(v3.8.0 beta 1 in Windows 10)
I was playing around with #ifdef recently; just experimenting.
I put a nonsense string expression into it-- not actually defined anywhere-- to
see what would happen:
Instead of issuing an error message or even a fatal error as I half-way
expected, it actually fell through to the *first* clause successfully. Without
the double quotes, it works as expected and falls through to the #else.
Should #ifdef behave this way? Is the first double-quote causing some kind of
unforeseen problem for the parser?
Post a reply to this message