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] Fri Aug 19 10:37:40 -0700
2005 -------
IMHO a fix in the scope of a "strict" mode (I think you have in mind some
switch like the OptionCompatible mode) would not make much sense here.
I appreciate the extreme caution in order to preserve compatibility with
existing basic code, but here we are speaking of existing _incorrect_ code.
BTW I would let you know that I can remember at least two or three cases
where an enhancement or fix in the basic engine caused me (and maybe other) to
change my code to get it working in the new version. :-)
I mean perfectly correct basic code that in the switch from 1.0.x to 1.1.x has
been broken.
And, at least in one case, I'm not speaking of simply add a missing
parenthesis, but to rewrite a whole module, after a complicated debugging.
...I'm not joking, it's true :-)
So, it seems to me that not fixing a bug in order to preserve
compatibility with existing incorrect code is even too much caution.
I think that if one writes incorrect code, the problem is on his own side,
independently from the behavior of the interpreter.
Anyway, I don't want to bother furthermore on this matter, so I will
appreciate any decision you will take.
best regards
Paolo
---------------------------------------------------------------------
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]
