gnustep-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PATCH: suppress deprecation warnings on OS X Leopard


From: Tim McIntosh
Subject: Re: PATCH: suppress deprecation warnings on OS X Leopard
Date: Sun, 30 Mar 2008 18:09:34 -0500

On Mar 30, 2008, at 5:31 PM, David Ayers wrote:

Tim McIntosh schrieb:

GNUstep seems to do a lot of mucking with the runtime structures that
are no longer visible with Obj-C 2.0, so I think the changes I made were just barely scratching the surface in view of what is actually needed. Not being familiar enough with the GNUstep code base, I have to wonder
if all of the direct use of the runtime APIs is really needed;  I can
see where it would be necessary on occasion within -base, but I was
surprised by the number of times I saw it being used in higher-level
frameworks.

Indeed we heavily rely on that mucking in GDL2.

But let me state this clearly... we are not mucking in the runtime for
performance reasons... we are just trying to get WO45 compatibility. So
if anyone has better ideas on how we can solve these issues with the
public API of Foundation, I'm up for it!

Thanks for the info and clarification. I didn't mean to pick on GDL2 here; I had just gotten the impression from experimenting with various things that the runtime API is used in a number of places outside of -base, and sometimes it was not clear why. I think part of this impression may have come from GSObjCRuntime.h getting pulled in by GSCategories.h in cases where it is not necessarily needed. This is why I was attempting to eliminate that #include.

In any case, it looked to me like there may be a lot of work to do wrt supporting the GSObjCRuntime.h interface on the Apple's Obj-C 2.0 runtime (which is probably really only needed to support 64-bit; I can't see them removing the old APIs in the 32-bit version any time soon).

Regards,
Tim





reply via email to

[Prev in Thread] Current Thread [Next in Thread]