Re: #warning
Re: #warning
- Subject: Re: #warning
- From: Robert Dell <email@hidden>
- Date: Mon, 19 Dec 2005 19:09:43 -0500
Alastair Houghton wrote:
On 18 Dec 2005, at 23:14, Cameron Hayne wrote:
On 18-Dec-05, at 4:56 PM, Dirk Stegemann wrote:
Perhaps it's possible to create an "ordinary" warning, for example
something like an unused variable with an unique name to indicate the
line/function/whatever in the source code file, and which could be
removed by the linker...?
That's a good idea - it would serve Robert's purpose well I think.
Except I don't know how well it would really work… compilers (GCC
included) generally work in multiple passes, so putting in code that
generates warnings might not give a good indication of overall progress
either (that is, the warnings might all be generated in a single pass,
but the compiler could then spend 90% of its time working on other things).
Much better to split the file up into pieces. I wasn't a party to the
discussion alluded to earlier, but I assume since it's 29,000 lines long
that it must be auto-generated by something?
all hand typed.
i also tried (this weekend) pulling out one procedure and putting it in a file all by itself and then doing the following:
#include "initWithBundle.m"
it properly showed 4 files but it then complained when compiling that file saying it doesn't know anything about my globals.
I was forced to put it back in the main file and no more complaints.
_______________________________________________
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