I was looking at this an narrowed it down further. If you include
objc/objc-api.h, you get the error. I don't know if it's really
important, but perhaps we shouldn't include this file in a public header
(it's in NSObjCRuntime now). I don't know why it's causing a problem,
but in general, objc-api exposes a whole lot of runtime internals that
most people don't need to be messing with.
Wim Oudshoorn wrote:
>
> --
> I narrowed the problem down to the following simpler example:
>
> #include <Foundation/Foundation.h>
>
> @interface AClass
> + (id) aMethod;
> @end
>
> @interface BClass
> - (void) aMethod;
> @end
>
> int main (void)
> {
> AClass *anSet = [AClass aMethod];
>
> return 1;
> }
>
> This gives the same kind of error. NSSet and NSFont problem is caused
> by the existence of two methods set: + (id) set in NSSet and - (void) set in
> NSFont.
>
> The strange thing however is that:
>
> If you replace
> #include <Foundation/Foundation.h>
> by
> #include <objc/Object.h>
>
> The problem does NOT occur. (The program will not link of course)
>
> Some extra information:
> gcc version 2.91.66
> GNUstep objc 0.9.3
> base 0.9.3
>
> But I do not think that that is important.
>
> Wim Oudshoorn.
--
Adam Fedor, Digital Optics | Fudd's law of opposition: Push
[EMAIL PROTECTED] http://www.doc.com | something hard enough, and it
[EMAIL PROTECTED] http://www.gnustep.org | will fall over.
_______________________________________________
Bug-gnustep mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gnustep
