Re: Type?
Re: Type?
- Subject: Re: Type?
- From: email@hidden
- Date: Thu, 8 Nov 2001 12:51:46 -0500
Sorry about that! One of the reasons I HATE being able to click on
something in a background window and have it take off. I much perfer
having to click once to bring the selected window to the front, then click
again to launch what you want. Guess this is one of the reasons not to
use a Powerbook to do several things at once!! Let me try again . . .
On Thursday, November 8, 2001, at 12:19 PM, Carlos Weber wrote:
The compiler is telling you that, in one of the lines of your source code,
it has found a name, "someClass", which (according to the compiler's
best guess and by virtue of its relationship to surrounding words and
names which the compiler believes it can understand) should be the name
of a _type_, i.e., one of the language's built-in types (like int or
float) or a class which has been defined by you or by one of the
frameworks. It might mean you are not #importing a necessary header file?
I created "someClass"; it's subclassed from NSObject. And all the #import
stuff is in place. I remember now that a missing #import WAS the problem
last time I got these errors. What really gets me is that the code that
is clogging up is a copy of some other code in the same project that works.
I have two data entry windows with related nibs and NSMutableArray(s),
one that stores two text fields and one that stores only one text field.
I coded the store-two-fields part first, which used a "firstClass:
NSObject" class as part of the code; then I merely copied everything over
to the new keep-track-of-only-one text field, changed the names using
find-and-replace, and deleted the code relating to the second text field
that was not needed. Indeed, I have gone over all of the .m & .h files
that are relative to the project and can find nothing wrong--not a missing
: or ; or anything else.
By turning on detailed logging in your project (open the Preferences...
item in the Project Builder menu, click the Building icon at the top of
the window, and then for Build Log Detail Level:, select Detailed Build
Logs), you may be able to see more precisely just where in your source
code the compiler is barfing, and go from there.
The detailed Logs still give no hint. Will now try the @someClass idea
that John Hornkvist recommended as a last resort.
| References: | |
| | >Re: Type? (From: Carlos Weber <email@hidden>) |