|Subject:||Re: Discovery from class-dumping Yosemite system libraries.|
|Date:||Wed, 8 Apr 2015 14:48:52 +0100|
Is making frameworks source compatible interoperability?
Sent from my iPhone
> On Apr 8, 2015, at 18:16, Gregory Casamento <address@hidden> wrote:
> In the interest of being cautious, please, in the future, I would
> prefer that you do NOT post reverse engineered information to this
> list. In the US such information is okay to use for the purposes of
> interoperability, but it becomes of questionable legality given that
> there are people on this list who are not in the US and local laws in
> their countries may vary.
> Thanks, GC
>> On Wed, Apr 8, 2015 at 6:11 AM, ChanMaxthon <address@hidden> wrote:
>> I class-dumped Apple's system libraries and discovered this:
>> NSObject is implemented in libobjc.dylib, despite header appeared in Foundation.framework
>> NSArray and friends, Objective-C classes that is toll-free bridged to CoreFoundation types, are implemented in CoreFoundation.framework, despite header appeared in Foundation.framework
>> CF types does have a one-to-one mapping to internal Objective-C classes, being subclasses of respective public umbrella classes or _NSCFType class for non-TFB types. This suggests that the polymorphic CoreFoundation functions maps to Objective-C methods on NSObject.
>> Apple did not make NSSet/CFBag and NS/CFRunLoop TFB but we can make that happen without breaking Apple's interface contracts.
>> Sent from my iPhone
>> Gnustep-dev mailing list
> Gregory Casamento
> GNUstep Lead Developer / OLC, Principal Consultant
> http://www.gnustep.org - http://heronsperch.blogspot.com
Gnustep-dev mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|