Problem description: csng and cdbl return Error 13 if the number has negative exponent. Tested on Ukrainian and USA standards/interface Steps to reproduce: 1. Open LibreOffice Calc and it's IDE 2. Paste the following example. The following comments shows current answers: Sub Example Print val("-3.14e2") '-314 Print val("-3.14e-2") '-3,14E-02 Print cdbl("-3,14e2") '-314 Print cdbl("-3,14E-2") 'Inadmissible value or data type. 'Data type mismatch End Sub 3. Replace all commas by Your local decimal separator. It is very important! 4. Run it Current behavior: The answers are shown in comments: -314 -3,14E-02 -314 Inadmissible value or data type. Data type mismatch Expected behavior: -314 -3,14E-02 -314 -3,14E-02 The LibreOffice forum contains thread: en.libreofficeforum.org/node/5702 The proposed workaround is to use val. It works only on point separated numbers so it cannot be used on localized numbers. With best regards. Viktor. Operating System: Ubuntu Version: 4.1.0.4 release
Hello I reproduce on windows 7/64 with Version: 4.2.0.2 Build ID: cd65d6220c5694ee7012d7863bcde3455c9e3c30 Regards Pierre-Yves
** 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 on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Hi Still reproduced on windows 7/64 & Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16 Locale: fr_FR Regards Pierre-Yves
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
On pc Debian x86-64 with master sources updated today, I don't reproduce and have the right values. Idem with LO Debian package 6.1.5.2. Could someone give a new try with a recent LO version?
Caolán, I guess you have a good knowledge on this matter, considering your fix in tdf#98778
I imagine this is a duplicate of bug 98778 given the versions is reported in and the similar effect and that its not currently reproducible. *** This bug has been marked as a duplicate of bug 98778 ***