Benjamin Kosnik writes: > I think it's important to insure that gcc-3.3 and gcc-3.2 are at the > same C++ ABI before gcc-3.2 is released. Yes, it's important to understand that there will be MASSIVE resistance to changing the C++ ABI very soon again after 3.2, so it will be really bad if 3.3-pre will already break it.