Frank Condello wrote:
There are already a few requests for compiler warnings to point
out unused variables (mxahvbwa, aevsqtcd, andodvao) though I'm all
for more generalized compiler warnings (brlvldkv) especially now
that the language is getting more complicated.
I wouldn't mind if the compiler remained silent and this
functionality was an always-on part of the "Check for Errors"
feature however.
This is the beauty of the lint feature request "akkbdtkt" since it
is only invoked when the user decides to invoke it. It would not
be invoked when you compile the project. This keeps the compiles
focused on hard errors where the lint functionality would probably
be invoked once a week to keep your code clean. I think you want
to keep the "Check for Errors" functionality as it is and keep
lint checks as a separate functionality since the check for errors
feature is meant to speed up the edit-compile cycle so that it
won't drop you into the debugger thus slowing you down.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
