Thanks David, That makes total sense. Can you point me towards the part of the code where this is initialized? When I spoke with a co-worker about it we actually thought it may have been part of the code clang emits. We're planning to have a local modification to fit with our existing code base which requires OSX 10.7 or above.
Thanks again! -Doug On Wed, Jul 3, 2013 at 7:39 AM, David Chisnall <[email protected]> wrote: > This is something that won't work on most versions of OS X either. The > new type encoding format was introduced very recently and we haven't > adopted it yet because it breaks anything that parses Objective-C type > encodings. > > David > > On 3 Jul 2013, at 15:30, Doug Warren <[email protected]> wrote: > > > There's some code I need to port that was written for the Apple > Objective-C runtime which basically calls ivar_getTypeEncoding checks that > it matchs the format @"foo" and if so calls objc_getClass("foo"). With the > GnuStep runtime that is only returning @. Is there any way to get the > class of the ivar or how is the encoding determined if we wanted to modify > our copy to match Apple's implementation? > > > > > > _______________________________________________ > > Gnustep-dev mailing list > > [email protected] > > https://lists.gnu.org/mailman/listinfo/gnustep-dev > > > -- Sent from my IBM 1620 > >
_______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
