From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: Richard Henderson <rth@redhat.com>
Cc: "Vincent R." <forumer@smartmobili.com>, gcc@gcc.gnu.org
Subject: Re: apple blocks extension
Date: Tue, 15 Sep 2009 16:21:00 -0000 [thread overview]
Message-ID: <4AAFBEE5.4080303@verizon.net> (raw)
In-Reply-To: <4AAFBAF2.3050209@redhat.com>
Richard Henderson wrote:
> On 09/15/2009 08:28 AM, Vincent R. wrote:
>> I just was curious to know if closures in apple gcc(called blocks from
>> what I read) is
>> also in mainline.
>> What is the status about this extension ?
>
> It is unlikely that this will ever be brought into GCC, since
> it appears to be largely identical to the C++0x Lambda feature.
>
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1968.pdf
>
>
> r~
>
I agree that it is superfluous for C++ at this stage but it might be
nice for Objective-C (regular C) although Objective-C++ will then have
to be taught how to deal with it somehow anyway.
OTOH, with lambdas it might be more easy to put this in.* It is
probably just a special case of lambdas. We'd have to find out which
one of course. I think syntactically it shouldn't be too bad.**
In general, and this has come up before, there are other things in
Objective-C 2.0 that we don't have. IIRC the Apple trees left behind
are a little old and not in good shape. What are the licensing issues
for borrowing from LLVM leaving aside the technical issues?
ed
* Or not. I think C++ lambdas are implemented as a little class of some
type which might make C mad.
** I was noticing that C++ lambdas and Obj-C message passing syntax
collides a little.
next prev parent reply other threads:[~2009-09-15 16:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 13:28 Vincent R.
2009-09-15 13:46 ` Steven Bosscher
2009-09-15 13:59 ` Dave Korn
2009-09-15 14:03 ` Tristan Gingold
2009-09-15 14:21 ` Vincent R.
2009-09-15 17:03 ` Michael Meissner
2009-09-15 16:04 ` Richard Henderson
2009-09-15 16:21 ` Ed Smith-Rowland [this message]
2009-09-15 16:50 ` Ian Lance Taylor
2009-09-16 15:50 ` Mark Mitchell
2009-09-16 16:21 ` Ian Lance Taylor
2009-09-16 18:12 ` Vincent R.
2009-09-16 18:40 ` Chris Lattner
2009-09-16 19:05 ` Dave Korn
2009-09-16 23:57 ` Linda A. Walsh
2009-09-15 16:35 ` Chris Lattner
2009-09-17 0:05 ` Linda A. Walsh
2009-09-24 14:57 ` Jason Merrill
2009-09-24 15:23 ` Chris Lattner
2009-09-24 16:53 ` Jason Merrill
2009-09-24 20:41 ` Jason Merrill
2009-09-25 16:55 ` Vincent R.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AAFBEE5.4080303@verizon.net \
--to=3dw4rd@verizon.net \
--cc=forumer@smartmobili.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).