Anonymous user
Talk:Comments: Difference between revisions
→[[C]]: #if 0 and syntax errors
(→[[C]]: #if 0 and syntax errors: Please read what you delete) |
|||
Line 36:
: Did you actually ''read'' the text you removed? The ''Compiler'' does not see the unterminated character constant, but the '''Preprocessor''' does. See e.g. http://c-faq.com/ansi/ifdefsyntax.html
: Unfortunately I don't have the C standard, so I cannot quote directly from there, but I double-checked with C++ that both CD2 (latest public draft of the 1998 version) and n2009 (a draft for the next section) contain wording identically in both (i.e. with exrtemely high probability also in the real standard) that this is true in C++ as well. More exactly, character literals are preprocessing tokens, and translation to preprocessing tokens happens in translation phase 3, while processing of preprocessing directives (this includes #ifdef) doesn't happen until translation phase 4. --[[User:Ce|Ce]] 05:17, 30 September 2007 (MDT)
::Egads! The reason I disbelieved you is that I have never used a C compiler which actually obeyed this part of the standard. The snippet compiles fine in gcc 3.4 and 4.0.1. I even tried with '''-std=c99 -pedantic-errors''' options for all supported standards. I also tried with just the preprocessor '''cpp''' in isolation.
::I beilieve this section should be prefaced with "'''Standard:''' ANSI (obsolete)" or a list of compilers which exhibit this behavior. Which C/C++ compiler are you using which fails on the above snippet? --[[User:IanOsgood|IanOsgood]] 09:57, 30 September 2007 (MDT)
| |||