On Sep 16, 2005, at 2:11 AM, j o a r wrote:
On 16 sep 2005, at 07.58, Markus Hitter wrote:
If it works, that's fine. It was some issue with Xcode's quick-parser (for menus and syntax coloring) or something along these lines. Possibly, if you have one quote only, like in:
#error Perhaps it's enlightening to do a few quick tests here.
I seem to remember that GCC used to barf on unmatched apostrophes (like in "can't") unless you quoted the whole warning string - at least on on some combinations of GCC version + OS platform that we had to support. I also think that there were some characters that were not allowed unless the string was quoted - but I'm not sure, and I can't remember which ones...
Using unmatched apostrophes in a unquoted warning string works fine when I try it now in GCC 4.x on Mac OS X. I'm still using the <#warning "some msg"> syntax though. Old habits die hard, and I don't have any problems at all, so I see little reason to change.
hmm, may be that's why I don't have any problem ever... I use double quote (#error "some text") and I have this habit to write one statement and not to use punctuation in between the double quote, such as:
#error "cannot find mymagic dot h"
can't remember why I started that way...
Pointers to official documentation / change notes on this topic would be appreciated.
yup, that would be great, too.