Hi,
On Thu, Dec 15, 2016 at 01:02:05PM +0100, Jan Iversen wrote:
since you have already made the ball rolling by making gbuildtojson in C++
the logical consequence would be to port the script to C++.
My fear with that was it (using C++ instead of Python) would discourage people
to contribute for other IDEs. But now that we have at least a wireframe
implementation for most popular IDEs going straight to C++ might indeed be our
best option[1] bootstrapping-wise. Although parsing JSON in C++ is rather ...
meh, but we certainly dont want an external dependency for that.
Probably needs an iterative approach: first parse the JSON stuff in some C++
objects and create output for the first IDE. Other IDEs move over from Python
to C++ one by one later.
Best,
Bjoern
[1] tsss, the irony of that.
Context
- Re: make gbuildtojson and make xx-ide-integration problems. (continued)
Re: make gbuildtojson and make xx-ide-integration problems. · Alexander Thurgood
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.