Re: syntax highlighting bug?
Re: syntax highlighting bug?
- Subject: Re: syntax highlighting bug?
- From: David Ewing <email@hidden>
- Date: Fri, 16 Jul 2004 09:40:37 -0600
On Jul 14, 2004, at 3:43 PM, Markian Hlynka wrote:
I'm porting some code (loosely) that has a lot of lines like this:
#define verbose0 0 /* low-level output (off) */
#define verbose1 0 /* recent details */
#define verbose2 0 /* search or eval details */
#define verbose3 1 /* normal output (on) */
now, in "old" c, the symbol verbose0 might actually be replaced with "0
/* low-level output (off) */"
But, I'm under the impression that todays preprocessors are a little
smarter than that.
Thus, as long as I'm using a current gcc, should I be worried?
I don't think you need to be worried. Even in "old" C, this shouldn't
have caused any problems.
Second, Xcode highlights this example as I've shown above. Shouldn't it
be like this?:
#define verbose0 0 /* low-level output (off) */
#define verbose1 0 /* recent details */
#define verbose2 0 /* search or eval details */
#define verbose3 1 /* normal output (on) */
your comment colour may vary, but you get the idea? is this a bug?
Well, no colors came through, but this is still a known bug. No need to
file a new one.
Dave
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.