To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112319
------- Additional comments from cl...@openoffice.org Mon Jun 14 20:40:24 +0000 2010 ------- > The code is commented-out and thats it. If you have a problem with that then > preprocess all files before you open them. No idea what you mean with preprocess before open. Please explain. > If I add a comment or remove a comment there is no need to give an > explaination for this action. Please stop involving me into silly discussions. It is not about comments. It is about commented-out code. And no, it is not your pet project. It is a question of overall code-quality in terms of contributor-friendliness, readability and maintainability. Error-aware code is good. commented-out-code where no one knows what it is meant to do is not. You cannot tell whether that is an ancient line of code that once was necessary, whether it is a leftover debug-statement or a completely unrelated copy and paste error. So I will continue bothering you when I stumble across those kind of things. That you cannot/don't want to give a reason why you added that commented-out code-statement is prove of my POV. --------------------------------------------------------------------- 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: issues-unsubscr...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
