ObjC and the dual runtime issue(s)

Subject: ObjC and the dual runtime issue(s)
From: Alex Perez <email@hidden>
Date: Mon, 29 Dec 2003 14:23:35 -0800 (PST)

Folks,

Now that we've got a real forum for this discussion, I guess it's time to
bring this issue up. Many folks who use the GNU ObjC runtime were less
than pleased with the fact that Apple shoe-horned @try/@catch & friends
into the *official* FSF GCC tree without making it work under the GNU
ObjC runtime. Frankly, I'm a bit miffed as this faux pas on Apple's part
as well, and as such I'd like to suggest/propose that some sort of policy
which explicitly states that ObjC language changes like @try and such not
be accepted into the FSF GCC tree until they work with both runtimes.
Apple is free to do as it wishes with their GCC tree, but Apple should not
have total control over the FSF's ObjC GCC stuff. This is the sort of
situation where corporate agendas and rushed deadlines can come into
conflict with the more loosey-goosey development model/timeline which is
used in GCC and other open source projects.

Anyways, I know there's also a faction of people using the GNU ObjC
runtime who think that @try and friends are braindead by design, but I do
not share that sentiment. What I'm somewhat concerned with are what I see
as strong-arm tactics from Apple WRT cramming things into the *FSF* ObjC
runtime in an apple-only way, with no regard for the GNU ObjC runtime.
ObjC language factionalization would be an absolutely horrible situation,
and I'd like to see that it's avoided at all costs.

Discuss.
_______________________________________________
objc-language mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/objc-language
Do not post admin requests to the list. They will be ignored.

Prev by Date: Re: Objective-C/C++ Rules
Next by Date: Re: ObjC and the dual runtime issue(s)
Previous by thread: Re: Class variables in Objective-C
Next by thread: Re: ObjC and the dual runtime issue(s)
Index(es):
- Date
- Thread

Home