[cfe-dev] __has_include and __has_include_next
Chris Lattner
clattner at apple.com
Mon Nov 2 13:17:45 PST 2009
On Oct 30, 2009, at 1:43 PM, John Thompson wrote:
> Here's another go at __has_include and __has_include_next for your
> review.
>
> -John
In the documentation, please add an explicit "to test for this
feature, use #if defined(__has_include)" at the bottom of the section.
Minor style suggestion, instead of :
+ // Get the result value. true means the file exists.
+ Result = (File ? true : false);
How about:
+ // Get the result value. Result = true means the file exists.
+ Result = File != 0;
Otherwise, looks great! Please apply, thanks John!
-Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20091102/31d283f7/attachment.html>
More information about the cfe-dev
mailing list