On Sat, 17 Jan 1998, Orlando Llanes wrote:
That's what they want us to think.. It's a trap!!! Just kidding =B) Iread in either Dr Dobbs Journal or C/C++ User's Journal that a standard has finally been set for C++, so 2.8.0 *might* be in response to that (just a guess, don't take for a fact that it's the reason 2.8.0 is mentioned).
This C++ standard was released in november or december last year; it takes slightly more time to develop a new compiler release. In fact, it took ~2 years since the last major release (2.7.0)
As for whether or not GPC will work without modifications (if 2.8.0 is in response to the C++ standardization), as long as GPC doesn't use C++ it should be backwards compatible with 2.7.x
Things are slightly more complicated. GPC hooks into GCC internals, and this interface *did* change. Then, a number of GPC files (gpc-*.c) are modified versions of their GCC counterparts (c-*.c), they have to be upgraded too. Finally, after such a severe modification of a large source base such as GCC+GPC, it takes some time before things stabilize.
But we must upgrade sooner or later, so we might just as well do it now.
JanJaap
--- With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC1925.