| ??? 06/02/09 21:21 Read: times |
#165768 - The argument is Responding to: ???'s previous message |
Neil Kurzman said:
LINT ... it can be picky. That is the whole point. I call it, "attention to detail" If you don't care about being certain that your code is correct, then just don't bother with Lint! It points out things that maybe wrong, but are not. It points out potential danger areas. Do you want (potential) danger areas in your code? Again, if you don't care, then just don't bother with Lint! But If you want code that not only appears to work when you try it a couple of times, but that you can guarantee is free from (potential) flaws that could manifest under unusual conditions, or could be broken by a careless modification in the future - that is the time to use Lint and to pay attention to its advice. It is also a good teacher. Only if you pay attention to its advice! Unfortunately, Sandeep Gupta seems to have been very quick to throw all these messages on all the forums he could find, but hasn't shown any interest in any of the replies. :-( |
| Topic | Author | Date |
| PC Lint - Error 64 | 01/01/70 00:00 | |
| signed/unsigned | 01/01/70 00:00 | |
| These are LINT Questions | 01/01/70 00:00 | |
| First time with LINT? | 01/01/70 00:00 | |
| Fair I think | 01/01/70 00:00 | |
| The argument is | 01/01/70 00:00 | |
| Some examples | 01/01/70 00:00 | |
| There is no such thing as a benign warning | 01/01/70 00:00 | |
| A question of dices | 01/01/70 00:00 | |
| LINT has to deal with C | 01/01/70 00:00 | |
| char != letter | 01/01/70 00:00 | |
| Signed/unsigned char | 01/01/70 00:00 | |
| signed/unsigned | 01/01/70 00:00 | |
Show it! | 01/01/70 00:00 | |
| How to post legible source code | 01/01/70 00:00 |