Re: Cocoa Newbie Question.

In article 
<fe79dd66-0263-429a-b443-a7a28ef083eb@[EMAIL PROTECTED]
>,
 piscesboy <oraclmaster@[EMAIL PROTECTED]
> wrote:

> On Jun 11, 1:51 pm, piscesboy <oraclmas...@[EMAIL PROTECTED]
> wrote:
> > This is my first time compiling objective C and C files together for
> > one program. All of my files are C files except the main file which is
> > in objective C called main.m
> >
> > Here is the code for my boilerplate main implementation file file:
> >
> > #im****t <Cocoa/Cocoa.h>
> > #include "defs.h"
> > #include "data.h"
> > #include "treenode.h"
> > #include "fileinout.h"
> >
> > int main(int argc, const char* argv[]){
> >
> >         return 0;
> >
> > }
> >
> > All the other .h files in my #includes are C files containing my
> > functions.
> >
> > Here is the error I get when I compile:
> >
> > gcc -Wno-im****t -ansi -pedantic -Wall -O2 -c treenode.c
> > gcc -Wno-im****t -ansi -pedantic -Wall -O2 -c main.m

This is not the cause of your error, but -Wno-im****t very, very likely 
is not something that you will want to compile .m files with. At the 
least, that would get rid of the warning

> > main.m:1:2: warning: #im****t is a GCC extension

I also guess that you are not using Xcode. Reason is that, on my system 
(10.5.3), Xcode compiles a simple main.m as

CompileC /[...]/main.o /[...]/main.m normal ppc objective-c 
com.apple.compilers.gcc.4_0

which eventually calls gcc passing a few zillion flags, including

    -fpascal-strings
    -x objective-c
    -arch i386

If you are not using Xcode, start doing that, if only to check what 
command lines it produces.

> > In file included from /System/Library/Frameworks/AppKit.framework/
> > Headers/AppKit.h:53,
> >                  from /System/Library/Frameworks/Cocoa.framework/
> > Headers/Cocoa.h:13,
> >                  from main.m:1:
> > /System/Library/Frameworks/AppKit.framework/Headers/NSEvent.h:72:
> > error: syntax error before 'unsigned'
> > make: *** [main.o] Error 1
> >
> > This is a fairly cryptic error for me but it appears to be associated
> > with the file #im****t 'ed from the Cocoa framework. What is going on
> > here?
> >
> > I am an absolute beginner in using Objective C and I just want to
> > learn to get this to compile for now.

I guess that you are not telling the compiler that it is compiling 
Objective-C code. Hence, it interprets Cocoa/Cocoa.h as a C header, 
which in turn leads to your error message because some line in that 
header is not legal C. Producing good error messages for C code, and 
even more so for C++ code, in incredibly hard, and often impossible. The 
actual reason for the error could be any earlier line.

> New development: I tracked down and looked at the file NSEvent.h and
> looked at line 72 and found this:
> 
> 
> static inline unsigned int NSEventMaskFromType(NSEventType type)
> { return (1 << type); }
> 
> gcc says there is a syntax error before "unsigned".

See my remark about producing good error messages for C/C++.

> This appears to be the offending line of code for when I include
> anything else it compiles fine. My worry now is that NSEvent.h is
> busted and as I am a newbie I don't want to touch the code. I just
> want to get it to work.
> 
> I never touched NSEvent.h in my life. What is going on here?

On my system (10.5.3, with XCode 3.0), that line reads:

NS_INLINE NSUInteger NSEventMaskFromType(NSEventType type) { return (1 
<< type); }

I guess your "tracking down" included preprocessing the code. If so, 
this is nothing to worry about. If not, can you check the actual file?

If this does not help, start compiling a main.m that only contains 
"im****t <Cocoa/Cocoa.h>". If that succeeds, the problem likely is with 
some of your own files or with the commands you issue to compile your 
code.

Reinder