olaf flebbe wrote: > Please do not mix the terms "compiles o.k. and works for me" with > "the code is correct".
I did no such thing. The issue here is whether or not the code is the *same* as the one we are shipping on other platforms. Yours is not, and therefore really shouldn't be packaged up into a release. But you're absolutely right: this looks like a plib bug to me too. You should re-submit that fix to the plib folks, not us. (And not as a MSVC8 "build patch" -- I wasn't looking for bugs in it, for example, and missed this one entirely). We can't fix plib bugs here, and if this isn't a showstopper for the release (it's not) posting it to a thread titled "The Release" and demanding that it be applied is probably going to confuse things more than help. And I still think that flightgear-devel is an inappropriate forum for discussion plib problems. Our goal here should be to get it building for the release, only. Note that all of this code has *already* been obsoleted in the CVS trunk anyway. After this release, it simply isn't possible for us to hit this bug, or any other problem with ssg, ever again. Andy ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
