Eric Blake wrote: > Making the ABI change now (which > probably won't affect C apps, but will definitely affect any C++ code that > used uint32_t and friends in mangled names) > > But I'm with Dave that IF we decide > the ABI change is the right thing to do, then NOW is the only time worth > doing it.
Especially as the transition to gcc4/dw2-eh/shared-libgcc/shared-libstdc++/--enable-fully-dynamic-string is *definitely* an ABI break for C++, anyway. -- Chuck
