On Wed, 23 Feb 2011, Mark Mitchell wrote: >> Perhaps so; I'm not sure what the right answer is for the default ABI >> version. For now I've just made these changes ABI v6, and I'm checking >> in this patch. > That's good future-proofing. > > I know I'm being a bit pedantic, but I was just getting beat up about > GCC backwards-compatibility again today. It's possible to fix 100 bugs, > add 100 features, and still have an unhappy user if their code stops > working.
Well, we've just done it once again. Quoting from the GCC 4.6 release notes: Most libstdc++ standard headers have been changed to no longer include the <code>cstddef</code> header as an implementation detail. Code that relied on that header being included as side-effect of including other standard headers will need to include <code>cstddef</code> explicitly. Gerald
