olaf flebbe wrote: > You may be wrong. They are writing to const char *. I had to strdup().
A "const" char* is exactly the same thing as a regular pointer at the level of CPU instructions. Writing to it does exactly the same thing as writing to a non-const pointer. The difference exists at *compile* time only. If MSVC is complaining about it, just adjust the warning level. Are you maybe trying to say that plib is writing to a static string constant? That would be a pretty serious bug if true, but as far as I can see it's not. Your use of strdup() is just adding an extra (and needless) step. Have you tried just adding a typecast instead? Again, the point here isn't whether or not plib's code is clean and will compile without warnings on MSVC. The point is whether it works the same as it does on our other platforms. Build issues are plib's problem, not ours. 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
