> Is there any point in the #include_next, even?
I think so. If stdbool.h may provide extensions/additional definitions (ex
"#define _Bool"). I don't want
to manage these within libc++ and I don't want to prevent users from
getting them from the actual header.
Although upon further inspection "_B
On Fri, Feb 19, 2016 at 4:16 PM, Eric Fiselier via cfe-commits
wrote:
> Author: ericwf
> Date: Fri Feb 19 18:16:41 2016
> New Revision: 261381
>
> URL: http://llvm.org/viewvc/llvm-project?rev=261381&view=rev
> Log:
> Add stdbool.h wrapper for libc++
>
> Summary:
> According to the C++ standard is
Author: ericwf
Date: Fri Feb 19 18:16:41 2016
New Revision: 261381
URL: http://llvm.org/viewvc/llvm-project?rev=261381&view=rev
Log:
Add stdbool.h wrapper for libc++
Summary:
According to the C++ standard isn't allowed to define `true`
`false` or `bool`. However these macros are sometimes defin
