"N.M. Maclaren" <n...@cam.ac.uk> writes: > That is another matter entirely. The code of gcc/gfortran is supposed > to be compilable with other compilers, and it is foolish to make > unnecessary assumptions by relying on undefined behaviour. > > The simple facts are that C++ does NOT define bool to be compatible with > _Bool, and there are enough differences in specification and semantics > to make it likely that they are not the same in at least some compilers. > This mess has caused and still causes no end of problems for Fortran > interoperability and in standards like MPI.
Er, maybe so, but is there actually an issue in _this_ case? >From original message, it sounds like these are internal compiler interfaces, so all that matters is that they be self-consistent, and there's no external ABI involved... So as long as all the code in question is compiled with C++ and uses C++ bool, or is compiled with C99 and uses _Bool, and doesn't use any functionality that isn't in the intersection of those two types, there shouldn't be any problem, right? -miles -- Congratulation, n. The civility of envy.