glibc headers and C++

[Ulrich Drepper]

Jakub Jelinek <jakub@redhat.com> writes:

> 4) hack C++ so that it accepts statement expressions in initializers (by
> either turning them into some internal functions or expanding them within
> __static_initializers_and_constructors or how is that function called).

I see not much of a difference between calling the function htonl()
and handling the statement expression.  In any case a synthetic
function has to be generated.  Therefore I strongly prefer #4 since
this is simply necessary to rectify the behavior.  The user should not
be exposed to such implementation details.

Alternatively we simply disable the optimizations for C++.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------