Re: #pragma message in GCC
Re: #pragma message in GCC
- Subject: Re: #pragma message in GCC
- From: j o a r <email@hidden>
- Date: Fri, 16 Sep 2005 08:11:01 +0200
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.
Pointers to official documentation / change notes on this topic would
be appreciated.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden