The concept of "a warning" is broken by Alan Crowe (4.00 / 1) #4 Sat Mar 15, 2008 at 07:05:00 PM EST
The traditional concept is that the compiler tells you: three errors, five warnings.

You fix the errors, change the code to eliminate three of the warnings and decide to live with the other two. Now you have: no errors, two warnings.

This sucks; once you have attended to things you should get a clean compile. There should be declarations that you can wrap around dodgy code, muffling specific warnings and documenting why you don't care. So you start with: three errors, five warnings, no notes. You end up with: no errors, no warnings, two notes.

From time to time you should look in notes.log to see what the notes were about and review the reasons you gave for not pursuing the matter. Current practise implicitly schedules such a review for every compile, which is obviously too often.



Login
Make a new account
Username:
Password: