To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=56635 Issue #:|56635 Summary:|option explicit doesn't function correctly Component:|framework Version:|OOO 2.0 Beta2 Platform:|All URL:| OS/Version:|All Status:|NEW Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|scripting Assigned to:|ab Reported by:|npower
------- Additional comments from [EMAIL PROTECTED] Tue Oct 25 09:28:37 -0700 2005 ------- np->ab Maybe I'm off the mark here, the problem I'm seeing is as a result of this related issue http://qa.openoffice.org/issues/show_bug.cgi?id=56633 it seems that if option EXPLICIT is set, basic will erroneously not complain about a variable that has NO associated Dim statement (i.e. in the module its used ) but IS defined as private in another module. See the bug above for the complete description. but when compatability is turned on ( e.g. via CompatibilityMode( true ) ) it complains about the variable being undefined, this seems plain wrong, the test is in step2.cxx:FindElement(...) if( pElem->IsSet( SBX_PRIVATE ) ) { SbiInstance* pInst = pINST; if( pInst && pInst->IsCompatibility() && pObj != pElem->GetParent() ) pElem = NULL; // Found but in wrong module! wonder why this is only checked if IsCompatibiltiy is checked? surely should always do this check, but maybe I miss something --------------------------------------------------------------------- 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]
