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
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
Chan,
On Wed, Apr 8, 2015 at 8:21 AM, ChanMaxthon xcvi...@me.com wrote:
Is making frameworks source compatible interoperability?
Source code compatibility can be achieved without copying a given
implementation.
GC
--
Gregory Casamento
GNUstep Lead Developer / OLC, Principal Consultant
On 04/08/2015 12:11 PM, ChanMaxthon wrote:
Apple did not make NSSet/CFBag and NS/CFRunLoop TFB but we can make that
happen without breaking Apple's interface contracts.
Based on the design, NSRunLoop is an upper level wrapper of CFRunLoop
adding extra operations. I wouldn't find adding TFB
Is making frameworks source compatible interoperability?
Sent from my iPhone
On Apr 8, 2015, at 18:16, Gregory Casamento greg.casame...@gmail.com wrote:
Chan,
In the interest of being cautious, please, in the future, I would
prefer that you do NOT post reverse engineered information to
Unless you are a lawyer and are prepared to offer legal advice, let's not
discuss such semantics.
Let me also voice uneasiness at reading content resulting directly from
reverse engineering on GNUstep's mailing list. There are some topics that
may be best discussed off-list. Results of
I am thinking about a new TFB semantics actually. (not compatible with ARC, but
not really an issue as CF is not ARC anyway)
Because of this, leveraging Objective-C’s @defs():
@interface NSPlayground : NSObject
{
id object;
// …
}
@end
typedef struct CFPlayground
{
@defs(NSPlayground);
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.
Other than the
