https://bugs.documentfoundation.org/show_bug.cgi?id=148466
--- Comment #1 from Mike Kaganski <[email protected]> --- I do not quite see, which is the *expected* result - hence, I fail to see what exactly is considered wrong. (In reply to Alain Romedenne from comment #0) > Expected Results: > Using VBA, results are different: Is the "Using VBA, results are different" the whole essence of the report? Then it looks NOTABUG to me: there's no definition in language or function *specification* what should be the error code in which situation. Even in VBA mode, we don't generally have the same errors (even compile-time vs runtime!). Additionally, the bug report does not mention if this is a request for a change for the sake of change, or if there is some existing code that fails working when importing from MSO. I suspect that this is only created as part of documentation effort, not motivated by a real user problem. However, *iif* there's not much effort is required to ensure that the errors *in VBA mode* (only!) follow VBA, then it's fine to implement this. However, note the "in VBA mode": the concern about the specific error numbers can only arise when a code is written with specific errors expectation and handling; and this very expectation is applicable to existing StarBasic code; so if we introduce *such* changes just to keep some (which?) existing VBA code working on migration, we definitely must protect our existing users from the same problem. -- You are receiving this mail because: You are the assignee for the bug.
