James McKenzie wrote:
We are not 'wasting time.' This issue needs to be addressed by the development community so that errors, warnings and fixmes are properly reported.
This is semantics. FIXME/WARN/ERR - who cares? They are all just hints if something goes wrong where to look.
Each developer uses them differently. If you suggesting we all drop all we are doing and change all ERR(), that not really errors, but some messages that can happen even with broken windows programs, to WARN(), since FIXME() doesn't really qualify because this feature in most cases is implemented. Then we should just shut all the messages off by default and get rid of them. Or do s/ERR/WARN/g on the whole codebase.
Keep in mind lots and lots of windows programs trigger errors, because of bugs in their code. That happens on windows to. So because of some crappy program we want to limit ourself to what we can see? How does that help with troubleshooting valid errors? Or you want ask users for +all log every time something doesn't work?
Vitaliy.