To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84979 Issue #|84979 Summary|Logic flaw in Create Names range checking Component|Spreadsheet Version|OOo 2.3.1 Platform|All URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|spreadsheet Reported by|terrye
------- Additional comments from [EMAIL PROTECTED] Fri Jan 4 04:41:03 +0000 2008 ------- http://user.services.openoffice.org/en/forum/viewtopic.php?f=33&t=1343 refers Insert->Names->Create calls ScAddress::Parse in sc/source/core/tool/address.cxx to parse and validate the range address against for three variants CONV_OOO, CONV_XL_A1, CONV_XL_R1C1. The intent here is to capture any range names which have a valid A1 or RC notation syntax and prefix such with an underscore to prevent a possible conflict of the form: Named range IF99 refers to D23. If cell A1 contains the formula =IF99 does this equal cell IF99 or cell D23? However the implementation is not based on matching the entire string but on certain valid prefix strings. Hence underscore prefix occurs if the name matches: ^(\a+)(\d+).* and $1 <= IV 0 < $2 <= 63356 ^[RrCc] ^[RrCc][^0-9].* ^[RrCc]([0-9].*) and 0 < $1 <= 63556 Hence Cot, Row, If1stop, In9v9999xx, R65536xx, R6553x7zz generate _ prefixes. Boat, Saw, IX2, A0, In99999xx, R65537zz do not. OK including RC notation is sensible future proofing but * There is nothing to be gained by enabling prefix matching. The rule should be at the prefix only occurs if the name in its *entirety* would also be a valid cell reference in A1 or RC notation. * You need to decide a policy on maximum bounds. This should either be the current worksheet dimensions (256x65536) for *both* A1 and RC notation or we adopt a clearly defined growth factor (e.g. 2Gb x 2Gb). * Help should clearly state the rules for prefixing Incidentally Excel postfixes *only* if the entire reference would generate an address conflict (excepting patterns of the form R99C999 which it rejects). Again this one should be easy to fix IF we do an entire match and use current bounds. Let me know if you want me to propose a patch. --------------------------------------------------------------------- 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]
