> On Nov 28, 2016, at 3:35 PM, Jonathan Schleifer <[email protected]> 
> wrote:
> I read through both links, but is not clear to me what this provides over the 
> combination of, say, ObjFW + Clang or GNUstep + Clang.
> 
> It seems to want to achieve several goals, but does not state how. For 
> example, it says "Run everywhere C runs" and "based on a new compiler" at the 
> same time. That compiler seems to be a Clang fork. Which totally does not 
> match "Run everywhere C runs": Clang *by far* does not support as many 
> platforms as GCC. And GCC in turn by far does not support "everywhere C 
> runs". It also says
> 
>> The compiler is a fork of clang. One of the main goals of a community would 
>> be to integrate the compiler changes back into the mainline of clang. For 
>> that "Evidence of a significant user community" is one of the requirements.
> 
> which sounds a little bit weird. In order to upstream patches to Clang, 
> "Evidence of a significant user community" is not a hard requirement. I would 
> know. I added support for the ObjFW runtime and upstreamed it in time for the 
> Clang 3.2. There was no big user community back then. What it depends on is 
> that the patches are clean code and that you step up as a maintainer. Which 
> makes me a little bit unconfident, to be honest, because that means you 
> either didn't try or didn't meet the quality requirements.

I have not seen any proposals to upstream this, but maybe people merely failed 
to ping me directly; I'm afraid I don't keep up with as many mailing lists as 
I'd like to.

The number of new commits on the fork seems unexpectedly high for just a new 
ObjC runtime.  Apparently it also includes a major new language proposal as a 
simplifying alternative to ARC.

John.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Objc-language mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/objc-language/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to