If this is the problem then Apple won’t be able to build their 64-bit CoreFoundation and Foundation as well, as Apple's 64-bit runtime is an non fragile one just like us. They make it work somehow, and I believe we can figure out a way to do this the Apple way.
Maybe not actually using the fields defined in @defs, but resolve ivars (other than isa) using Objective-C runtime functions? This won’t break, I think. > On Apr 9, 2015, at 16:02, David Chisnall <thera...@sucs.org> wrote: > > On 8 Apr 2015, at 20:53, 陈北宗 <xcvi...@gmail.com> wrote: >> >> When I said not compatible with ARC, I mean the resulting mix of CF and >> Foundation code will not be able to be built using ARC. However it will >> produce headers perfectly useable in ARC code, and the rest of Foundation >> can even be modernised into taking advantage of ARC as well. > > No, when you say 'not compatible with ARC', you mean 'intrinsically fragile > and not compatible with the non-fragile ABI', i.e. not compatible with the > default compilation mode for Clang, or with code that exists in the same > program as ARC code. > > Or, to put it in simpler terms 'completely useless'. > > David > > -- Sent from my brain >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
