FROM : William Squires
DATE : Sun Apr 27 17:29:53 2008
I just had a light bulb moment (oops, I should have said "a super-
bright white LED moment") - what if Apple were to include a "macro-
expansion" tool in XCode (4, anybody?)? The idea would be that - if
you have a problem in which you are having trouble with hard-to-find
compilation errors, you could run this tool (through a menu item
selection), and it would show you the total expansion for a ".m",
".c", or ".cpp" file as the compiler sees it, including all "#include/
#import"s and all #define macro expansions, all color-coded. You
would then recompile, and the error messages would then refer to that
listing, allowing you to pinpoint what the compiler is really seeing
that line as saying, rather than what you THINK the compiler is seeing!
Just my $0.02 here.
DATE : Sun Apr 27 17:29:53 2008
I just had a light bulb moment (oops, I should have said "a super-
bright white LED moment") - what if Apple were to include a "macro-
expansion" tool in XCode (4, anybody?)? The idea would be that - if
you have a problem in which you are having trouble with hard-to-find
compilation errors, you could run this tool (through a menu item
selection), and it would show you the total expansion for a ".m",
".c", or ".cpp" file as the compiler sees it, including all "#include/
#import"s and all #define macro expansions, all color-coded. You
would then recompile, and the error messages would then refer to that
listing, allowing you to pinpoint what the compiler is really seeing
that line as saying, rather than what you THINK the compiler is seeing!
Just my $0.02 here.
| Related mails | Author | Date |
|---|---|---|
| William Squires | Apr 27, 17:29 | |
| Michael Ash | Apr 27, 17:44 |






Cocoa mail archive

