To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263
------- Additional comments from [EMAIL PROTECTED] Fri Dec 7 14:58:02 +0000 2007 ------- Hi guys, seems that there are only vague opinions regarding verbosity. So, let me say that I have a very _clear_ opinion on that. _Every_ kind of verbosity not related to showing progress looks _unprofessional_! It creates the impression, that the author did not really know what he was doing, so he created verbosity for the purpose of controlling the build process. That certainly does not mean, that errors or warnings should be hidden. Au contraire, errors and warnings should ideally report the full reason for happening. This also means, that errors _must_ not be ignored and must be handled properly. And yes, I know that this is not as easy as it may sound. Let me give a short example. Ideally the action of compiling a C++ file is only reported as progress, e.g.: compiling foo.cxx ... But, in case the action failed, it certainly needs to report the reason and its context, e.g.: COMPILE ERROR #123 for foo.cxx: g++ -I.. -I.... foo.cxx -o foo.o .... You get what I mean. IMHO, this verbosity thing is very important. This is what new developers see the first time they start hacking on OOo. One or the other may remember how Linux building looked like in the old days and how it got its verbosity under control. We need to do the same. Sorry for being so verbose ... ;-) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
