Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Hi Alex,

On Friday, 2016-09-02 09:03:29 +0100, Alex McMurchy wrote:

I've replicated the problem on -

Lubuntu 1404LTS (up to date as off a few days ago) - gcc (Ubuntu
4.8.4-2ubuntu1~14.04.3) 4.8.4

Slackware-Current (1402) hasn't been updated for a few months - gcc (GCC)
4.9.3

Good.

Yesterday once I understood what the actual problem was I raised two bug
reports

 * Bug 101837 - EDITING: Calculation error for CHIINV function
 * Bug 101838 - Editing: Calculation error for MINVERSE function

Thanks, though a heads-up here on the list would had been enough.
Usually we don't track build problems in the bug tracker.

In minverse.ods there was another issue, which I've not raised a bug, which
was to do with a rounding error in Row 27 the actual result was
169841859430433 whereas the expected result is 169841859430434. Should I
raise a bug report for this as well - so it can be tracked?

Just add that to
https://bugs.documentfoundation.org/show_bug.cgi?id=101838

Thanks again

  Eike

-- 
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key "ID" 0x65632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/
Care about Free Software, support the FSFE https://fsfe.org/support/?erack

Attachment: signature.asc
Description: PGP signature


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.