Hi Eike,
Actually the risk is quite low, as every release would introduce
a self-maintained state. To shorten things the final cut could be done
at every step if the sequence turned out to be unmaintainable.
You obviously have thought about it more than I have ;)
Fortunately we do have some time now for 4.3 to think things over. I'm
not clinging to my proposal but I think it's best for the users
who exchange documents.
I shall have a look at the code and see if your stepped approach is easy to
apply. Also, I shall have a look if and how this has effect on the Excel 2010 functions
CEILING.PRECISE, ISO.CEILING and FLOOR.PRECISE.
Where would be a good place to put the 'to Do list' (planned changes per release per function)?
In the code, in a wiki, which file/page?
Winfried
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.