On 02/11/2014 10:37 PM, Darrell Anderson wrote:
> This is a bug report against newer versions of libpng. I don't seen 
> any such errors with libpng 1.4.12.
> 
> I suspect a rite of initiation to become a libpng developer is to 
> introduce new code that breaks something for everybody downstream. 
> Cousins to the BOFH.

I cannot think of anything worse to break to cause unholy hell for all
developers alike other than breaking gcc or jpeg. Sheeze, I know it is for the
greater good of the future, and preventing exploits, blah, but those type of
FUBARs literally cost hundreds of thousands if not millions of manhours to
implements. In those cases every piece of software being built that contains a
png will have to be modified. I'm sure the png devs were not on any Christmas
lists (or other holiday lists) for the past few years...

-- 
David C. Rankin, J.D.,P.E.