Created attachment 127568 [details]
Demo mentioned in the OP
A function programmed in BASIC for use in Calc may have parameters declared optional. Positions of optional parameter may occur anywhere in the formal parameter list.
Calls to the function with omitted parameters from a BASIC Sub yield the expected results.
Calls from a formula evaluated for a Calc cell wrongly pass the numeric 0 for omitted optional parameters.
I only stumbled over the bug recently, but this in a case where I tried to get a function actually usable "in production". I could not find a promising workaround. The severity is therefore higher than normal from my point of view.
For trailing omitted optional parameters an error Err:511 is thrown by LibO V3.3 Calc if parameter separators are used. No separator, nothing passed. (This also is the behaviour of AOO up to 4.1.2.)
V3.5 and higher accept trailing omitted, even if there is a surplus in positions.
they then also pass a 0 for declared but omitted parameters and nothing for parameter positions in surplus.
See attached demo.
For clarification: The bug was found using V5.2.0. Only for the report here I also tried many old versions.
Ok I get this in the demo, so I guess it is not as expected:
Arch Linux 64-bit, KDE Plasma 5
Build ID: 65f2d6b1cc40b4b90f8987e8ea14d24b5f38f950
CPU Threads: 8; OS Version: Linux 4.7; UI Render: default;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on October 10th 2016
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Arch Linux 64-bit
Build ID: 37fc9f51a8de11d40632e8cda17ccf1fa4b1f503
CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: gtk3;
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Built on 6 August 2019