<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jul 5, 2011, at 9:41 PM, David Blaikie wrote:</div><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div>Objective-C++ exists and is important to a lot of our developers; any implementation of lambdas in Clang will eventually need to handle both.</div>
</div></blockquote><div><br></div><div>Ah, Ok then. Though I assume lambdas aren't a high priority for Apple at the moment, given the presence of Blocks. Is that the case? That's why I thought I'd start looking at it myself as it seems like a feature the wider community might have more interest/motivation to work on than the Apple folks.<br></div></div></blockquote><div><br></div>I don't think we'll openly weep if the first patches we see don't work in Objective-C++, but don't do anything that would it impossible.</div><div><br><blockquote type="cite"><div class="gmail_quote"><div>I suppose the question is whether "getLang().CPlusPlus0x" is true for Objective-C++, or only actual C++0x?</div></div></blockquote><div><br></div><div>Objective-C (and its revisions and supplements) is orthogonal to C++. We can and do support using the Objective-C extensions in code whose "base" standard is C++0x.</div><br><blockquote type="cite"><div class="gmail_quote"><div> Well for now the ObjC case for messages comes first - so it won't pollute the C++0x lambda case until someone wants to add in Obj-C++ lambdas.</div>
</div>
</blockquote></div><br><div>That seems like a reasonable approach.</div><div><br></div><div>John.</div></body></html>