syntax highlighting bug?
syntax highlighting bug?
- Subject: syntax highlighting bug?
- From: Markian Hlynka <email@hidden>
- Date: Wed, 14 Jul 2004 15:43:24 -0600
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?
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? ie
is it worth filing? Am I doing something horribly wrong? I'll double
the size of my source file if I have to change it all to:
#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) */
Yes, I know I should use inline; but at this time it's not something I
can/will play with as it will break the legacy code I'm working with.
Markian
_______________________________________________
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.