On Thu, Jun 14, 2012 at 07:18:08PM +0200, Noel Grandin wrote:
On Thu, Jun 14, 2012 at 6:38 PM, Bjoern Michaelsen
<bjoern.michaelsen@canonical.com> wrote:
Im getting fits thinking about the long term maintainability though.
In what sense?
It's an extra compile step and an extra dependency.
You can even choose from ExcelsiorJET / GCC-for-java / vmkit-clang :-)
... and a completely unsupported scenario for upstream HSQLDB -- so any
interesting bug in this compiler/product combinations will be ours. The
compiler becoming unsupported will be ours. In effect we would have our own
branch of some very complex technology (compilers/translators).
Best,
Bjoern
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.