Re: Future evolution of c++config.h and _GLIBCXX_USE_LONG_LONG

[Paolo Carlini <pcarlini at suse dot de>]

Matt Austern wrote:

> The danger is really on the Libc side.  According to the C++ standard, 
> the following program is valid:
> #define lldiv_t 0
> #include <iostream>
> int main() { return lldiv_t; }
>
> No sane person would do this (other than a test suite writer), but it 
> is valid.

Thanks. Now I begin to really understand what you mean: your message is
actually about the *possible* behavior of a _GLIBCXX_USE_LONG_LONG
macro (etc., as explained by Gaby and Jason), not about the *current* 
usage of
it...

Paolo.