what about clangd?

[Daniel Mensinger]

On Mon, 26 Aug 2019 17:50:35 +0200
Tomaz Canabrava <tcanabrava at kde.org> wrote:

> On Mon, Aug 26, 2019 at 5:39 PM Daniel Mensinger <daniel at mensinger-ka.de>
> wrote:
> 
> > On Sat, 24 Aug 2019 11:38:22 +0200
> > René J. V.  Bertin <rjvbertin at gmail.com> wrote:
> >  
> > > René J.V. Bertin wrote:
> > >  
> > > > About that: at first sight a proper implementation would take the  
> > existing  
> > > > compile_commands.json project management code from the cmake plugin  
> > and move  
> > > > it to a parent class where it becomes available to other project  
> > manager  
> > > > plugins too?  
> > >
> > > And another JSON parser than the one from Qt, which fails on larger  
> > projects  
> > > like digiKam (with a compile_commands.json file that's 87Mb large).
> > >
> > > R.
> > >  
> >
> > Wait... seriously? I am using the QT JSON parser for for the meson plugin
> > (the
> > introspection format is also in JSON (but different from
> > compile_commands.json).
> >
> > In that case would switching to nlohmann::json be OK? If yes, were should
> > the
> > header be located in KDevelop?
> >
> >  
> It's not as easy to integrate Qt code to the Nlohmann::json as it has no
> knowledge of Qt (and uses the std::string instead), but it's so much easier
> to handle things, and it can handle gigantic json files.
> it also does not know about QVariants. so there's a little of boilerplate
> to write if you use it.
> but it's a really serious project and tried to be as fast and efficient as
> possible.
> 
> https://github.com/nlohmann/json
> 
> 
> Daniel
> >  

Since I am only using the parser to load the introspection data from meson,
the conversion should be fairly easy. I have only used the QT parser because
it was good enought (at least I thought that) and I didn't want to introduce
a new dependency (to increase the chances of getting the plugin merged).

I have already worked with nlohmann::json, so the conversion should be
trivial for me to do. I only need permission and to know where to put the
header :)

Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20190826/5e2dd0b7/attachment-0001.sig>