To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=17781
------- Additional comments from [EMAIL PROTECTED] Mon Aug 22 00:25:01 -0700 2005 ------- I'm sorry to hear that you had to rewrite a module. That's what I always want to avoid but obviously that hasn't been successfull in all cases. BTW: If you had to change correct code to make it run in 1.1 it means that 1.1 contained a re- gression bug. Do you know if this problem is still there? If Basic does not run correct code, it's simply a bug. In any case this of course happened accidentally and I don't think this mistake is appropriate to justify breaking existing code in general. Of course, you're right that breaking incorrect code is not as bad as breaking correct code but I think there are different levels of incorrect code. If I take advantage of an ob- vious bug in my program I can't complain when the bug is fixed. But forgetting a parentheses can be done accidentally, in particular if the compiler does not complain about it... ;-) Ok, now we're going round in circles, but that's why I would prefer a "strict" mode. But this should be a general option that you only have to set once, not in every module. --------------------------------------------------------------------- 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]
