Re: Release check

[David Ayers]

Adam Fedor wrote:

> Is anyone planning on adding something to the GNUstep libraries that
> will make them binary incompatible (i.e. compared to the current CVS)?
> It would be nice to start working on getting the next release out.
> Adding binary compatible changes is still fine, of course.

I currently can't commit to doing this myself so don't hold up anything
because of this request, but I think it would be really great if someone
could find a way to have NSObject.h not #include <objc/Protocol.h> as
this pulls in <objc/Object.h> which in turn declares methods:

- (int)compare:anotherObject;
- shallowCopy;
- (const char *)name;

which often trigger warnings with new gcc's as the OpenStep API uses
different selector signatures when using untyped objects (i.e. id and
many cases of nested messages).  The legwork would be including those
headers in the necessary .m files.

Technically this really isn't a binary compatibility issue, but I
suspect that removing it could break enough code that currently assumes
certain declarations, that it would be worthwhile to bundle this with
binary compatibility breakage.

Cheers,
David