Re^3: How to detect I/O redirection on Win32

I definitely DON'T WANT the users to ignore errors or warnings.

And your users definitely do not want you dictating to them what they can and cannot ignore.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^3: How to detect I/O redirection on Win32

Replies are listed 'Best First'.
Re^4: How to detect I/O redirection on Win32 by Anonymous Monk on Sep 11, 2007 at 09:43 UTC
Hey, this is not a discussion on user psychology!! If a software release PRODUCES warnings and/or errors IT HAS to be logged. The users can decide to ignore the warnings, but the process won't let pass software with (MAKE/compile) errors. So the process has to take care to "see" as much as possible of the making, compiling, packaging ... To release a software to test department WITH build errors is just a waste of time!	[reply]

Replies are listed 'Best First'.

Re^4: How to detect I/O redirection on Win32
by Anonymous Monk on Sep 11, 2007 at 09:43 UTC

Hey, this is not a discussion on user psychology!!

If a software release PRODUCES warnings and/or errors IT HAS to be logged. The users can decide to ignore the warnings, but the process won't let pass software with (MAKE/compile) errors. So the process has to take care to "see" as much as possible of the making, compiling, packaging ...

To *release* a software to test department WITH build errors is just a waste of time!

[reply]