olaf flebbe wrote: > As a side note: The gcc does not enforce const-correctness very > much.
Sigh, and the flames continue... Your basis for that statement is what, exactly? Of course gcc enforces const correctness. I suspect what's happening here is that plib, which is using <string.h> and not <string>, is getting the C implementation declared. I'm not sure where the C++ standard requires here. Arbitrary libc headers obviously need to pass through compatibly, but maybe there are special requirements for the ANSI headers. > Unfortunatly they still miss MSVC8. Is the problem simply that VC8 has trouble? Isn't the obvious solution then to build with VC7 instead? If my memory serves, VC8 shipped with a new runtime that won't work on XP without an update, right? We probably want to build with the compatible compiler anyway. Regardless, you need to fix that patch if you want to see it used. 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
