[libdispatch-dev] linux + libdispatch + clang + blocks

Jordan K. Hubbard jkh at apple.com
Tue Jun 8 11:40:40 PDT 2010

Or we could just come to the conclusion that the time is simply not yet right to add Linux to the supported OS list.

From what I can read between the lines on the discussion thread in that bug, there doesn't seem to be much interest in clang, or even in merging block support into whatever branch of gcc linux follows, and the ultimate goal of any porting work we do (or incorporate) is to see the technology adopted more along the lines of what FreeBSD is on schedule to do with their 8.1 release.  If there's already this much push-back on a simple header change then that tends to suggest that there will be even more insurmountable obstacles just around the corner as we move on to the stuff that's actually *hard*, like kernel support. :-)

My vote would be to focus on platforms who's user communities display an active interest in the GCD API.  We're not here to do a "hard sell" on it since that's just a good way to alienate folks who might someday, under different circumstances, be interested in what it has to offer.


- Jordan

On Jun 8, 2010, at 1:06 AM, Paolo Bonzini wrote:

> On 06/08/2010 04:16 AM, David Leimbach wrote:
>> Oh well time to use a different libc?  I hear FreeBSD has a nice one!
>> :-)
> No, time to fix clang.  See my answer to
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=11157
> Paolo
> _______________________________________________
> libdispatch-dev mailing list
> libdispatch-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev

More information about the libdispatch-dev mailing list