To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=96834
------- Additional comments from m...@openoffice.org Thu Apr 30 09:58:34 +0000 2009 ------- Yes, that's the problem. For now we don't need a case where the current code is responsible for a bug. OTOH if we just change it because it looks odd, there is a chance that we break something without even knowing about it. So before changing the code I would like to see a test case that shows that the current code is wrong and the proposed change makes it better. Unfortunately this may be some effort as this would require to construct a suitable set of input files that is able to trigger this code. So in case we agree that this is necessary, I would like to move that to a different CWS as mba32issues01 is hopefully done now and it contains some fixes that will get more complicated to integrate the longer we hold them back. OTOH removing the patch from the CWS doesn't make sense also as it doesn't break anything that isn't broken anyway and it fixes the compiler problem. @cloph: as you raised the doubt, are you fine with my proposal? --------------------------------------------------------------------- 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...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
