On 08/29/2012 10:00 AM, John W. Eaton wrote: > Why define true, false, and bool to anything when using C++?
Maybe it's for '#ifdef bool' but to be honest I'm just doing what GCC does. Perhaps you can ask the GCC developers why they do did it that way.... Anyway, I'd be surprised if Octave cares whether true, false, and bool are macros. If it does, then it's broken on GNUish hosts anyway, right? And if it doesn't, the gnulib patch should work as-is.
