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


User npower changed the following:

                What    |Old value                 |New value
================================================================================
             Assigned to|npower                    |ab
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Tue Jun 23 14:11:47 
+0000 2009 -------
->ab ( let the tennis begin ;-) )
finally I got a chance to look again at this. The main problem is that ( and
it's mentioned somewhere below ) is that there is some confusion regarding
scope. In 'ordinary' basic public module variables are actually defined at the
library level. If you have 2 module variables with the same name then only one
will really be used ( as one eclipses the other ). The patch addresses this by
really defining module variables at the module level. 

Note: the comment in the patch about 'SbUserform' ( which dosn't exist yet
upstream ) is equally valid for 'SbClassModuleObject'

hmm I didn't really address visibility with this patch, e.g. if you have 2
module variables of the same name, both are equally 'visible' say from a third
module. Which variable do you get by default? ( I don't know ) but certainly you
can qualify them with the Module ( Module2.var, Module2.var etc. ) One would
guess that both in VBA which variable you really get if you don't qualify the
variable with a module specifier is an implementation detail. Until I come
across some 'real' code to force me to obey whatever strange rule that VBA might
employ I suggest we ignore this part for now

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