On Wed, 11 Apr 2012 08:02:07 -0700 (PDT)
Darrell Anderson <humanreadable@...> wrote:

> > But here g++ developers *do* provide backwards
> > compatibility, it is called -fpermissive. And there is no "bleeding
> > edge" at all unless you consider C++98 to be a bleeding edge
> > standard. Anyway, old compilers still work. On my Slackware 13.1
> > system, I have g++-3.4 installed into /opt, and I can use it to
> > compile a working program against system Qt4 thanks to system g++
> > being backwards compatible with g++-3.4 in terms of ABI.
> 
> Okay, I sit corrected. :) Yet I believe the overall general attitude
> among many free/libre developers remains correct. The libpng project
> seems like a good example. Every dot-zero release requires everybody
> else to scramble to fix code.

Guns don't kill people, people kill people.
Concerning libpng it's the same thing: libpng doesn't break
compatibility, distributions break compatibility.
For example, libpng 1.0 was evicted from Slackware at version 9.0
(March 2003) but is still in Fedora 16 (the latest). And libpng 1.0 is
still maintained upstream BTW.
> 
> Darrell
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> trinity-devel-unsubscribe@... For additional
> commands, e-mail: trinity-devel-help@... Read
> list messages on the web archive:
> http://trinity-devel.pearsoncomputing.net/ Please remember not to
> top-post:
> http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>