The gcc-4.3 distribution removes backward compatible include files,
pre-iso header files that a large number of legacy C++ packages rely
on. I'm wondering why such a major disruption in backward
compatibility wasn't reserved for gcc-5.0. And I'm also wondering why
the gcc packagers at Debian can't simply re-introduce these include
files. Is there some technical reason, some conflict in moving
forward with C++ that rules out the kind of backward compatibility
offered for years by libstdc++?
As an upstream developer I've struggled for years to keep stable C++
frameworks compiling with each new release of gcc. But gcc-4.3 raises
the bar in terms of backward incompatibility. Can the Debian gcc
community be of some help here? Why do more than 300 packages have to
be altered and re-tested solely for the offense of originating in the
earlier days of C++? It seems an unwise conservation of community
resources.
Scott Johnston
http://www.ivtools.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
