On Sun, Apr 27, 2008 at 11:29 AM, William Squires <[EMAIL PROTECTED]> wrote: > 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.
You mean like Build->Preprocess? It won't show you where the errors are in that mess, but you can either compile the result yourself or just do it by eye. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
