<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 1, 2011, at 11:30 PM, Jean-Daniel Dupas wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><blockquote type="cite"><div><br>I agree. We should also have a __has_feature(has_extension) of course, and the new goodness should be documented in the language extensions guide.<br><br></div></blockquote><div><br></div><div>Is this really needed ? We can already test for has_extension availability using ifdef.</div><div><span class="Apple-style-span" style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif; line-height: 19px; font-size: small; "><pre>#ifndef __has_extension // Optional of course.
#define __has_extension(x) 0 // Compatibility with non-clang compilers.
#endif</pre></span></div></span></blockquote><br></div><div>Ah, great point. This is even better. Nope, not needed.</div><div><br></div><div>-Chris</div><div><br></div></body></html>