John Denker wrote:
> 2) It seems vacuous to compare writing via a const char* to
> writing via a non-const char*, because AFAIK there is no such
> thing as writing via a const char*. No compiler AFAIK will
> generate any CPU instructions for it.
Oh, good grief:
$ echo 'void foo(const char* p){*(char*)p=0;}' > tmp.c
$ gcc -S -c -o - tmp.c
Look! Instructions! I await your further pedantry about this
not "really" being a const pointer because of the cast, to which
I will reply that casts like this are precicely the subject of
discussion (hint: see olaf's patch)...
If it really concerns you, take it to plib-devel. It's not our
code. The question was whether the constness issues in the
released plib code are blocking bugs for a new FlightGear
release. As far as I can see, they are not. Plib's behavior in
the lines touched by this patch is platform independent.
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
