A lint classic
From: tim (520010973502removethis_at_t-online.de)
Date: 05/29/04
- Next message: Bruce: "Re: A lint classic"
- Previous message: Guy Macon: "ECC memory under Windows"
- Next in thread: Bruce: "Re: A lint classic"
- Reply: Bruce: "Re: A lint classic"
- Reply: Dan Henry: "Re: A lint classic"
- Reply: Rick Merrill: "Re: A lint classic"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 29 May 2004 19:21:56 +0200
After months of nagging, one of me colleagues
eventually got around to looking at the 'lint' errors
in his 'c' code (which the rest of us are supposedly
relying upon as working).
As well as the expected problems such as:
if (byte_var < 0x200).....
and
if ( var && 0xf0 )...
was the incredible (I thought)
new_var = var << 16000; !!!
he looked at this line for a good 10 minutes before
declaring that he had no idea what it was really meant
to be doing. Personally I can't recall having seen such
a stupid line of code ever left in *working* code.
Disappointingly, having proved the worth of this tool,
he thinks this is job done and that he doesn't have to
use it again. He's in the wrong job (and perhaps, so
am I).
tim
- Next message: Bruce: "Re: A lint classic"
- Previous message: Guy Macon: "ECC memory under Windows"
- Next in thread: Bruce: "Re: A lint classic"
- Reply: Bruce: "Re: A lint classic"
- Reply: Dan Henry: "Re: A lint classic"
- Reply: Rick Merrill: "Re: A lint classic"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]