To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69979


User fs changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|UNCONFIRMED               |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |INVALID
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Wed May  2 09:04:13 +0000 
2007 -------
> My personal opinion is that this is not a bug, as if the script
> programmer disposes of the context object then that is a bug in the
> script.

Seconded. Disposing an object which you're not the owner of is a no-go, and can
lead to a variety of undesired results (note that quietly doing nothing is one
of the more gently reactions).

The Basic runtime itself is unable to determine whether certain actions on
certain objects are allowed, that's conceptually pretty impossible. Doing the
right thing here is the task of the programmer.

Side note: If such a wrong API usage would result in OOo crashing, I would
accept this as a bug. A crashing OOo is unacceptable. However, a not-running
macro after doing something wrong is, well, only a not-running macro.

---------------------------------------------------------------------
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]

Reply via email to