(Walter Harms) wrote:
A simple solution to *that* kind of dirty tricks would
be to remove any A = B from if statements so somebody can
write a RE to track hidden initialisations in if statements.
Another solution might be to change (lvalue == const) comparisons to
(const == lvalue) ones, so that an accidental (malicious?) '=' in place
of '==' is caught by the compiler.
I've made it my coding style after the incident.
--gera.
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
|
