KDevelop Go integration
Pavel Petrushkov
onehundredof at gmail.com
Mon Feb 1 15:54:00 UTC 2016
Hello Kevin,
I'm still here, I try to keep the plugin up to date with new go and
kdevelop changes, but I don't really have time to do any serious feature
development.
About parser package: last time I looked at it (summer 2014) using go code
in c didn't work very well and seemed more like a hack and there were no c
interface either. Another idea was to print the AST in go code and then
reparse it in C, but IIRC documentation said somewhere that format of
printed AST is not fixed. So I decided it would be too difficult to use.
Keep in mind that I'm by no means a go expert and things could have changed
drastically since then, especially now that whole go compiler is written in
go.
About gocode: again, in the summer 2014 it looked like gocode would be
relatively easy to integrate, but it was missing a lot of features, like
smart semantic completion and so on, that are on the other hand, easily
possible having the whole AST.
I have also heard that LLVM has some progress integrating Go. So it is
definitely worth to have a look at all this again, perhaps I could try
doing it in March, when I have some time. If anybody wants to work on it I
can help with understanding of my code or some go-specific features and
their integration in kdevelop. For the GSoC: I will most likely have no
time to do it, so I'm afraid I have to say no.
Regarding current state of the plugin: I believe it has been more or less
usable for some time, at least I was satisfied with it when I needed to
write some go. Other than that, I don't really know if it has any userbase
at all, if so, I wasn't contacted about any bugs or feature requests.
Regards,
Pavel.
On Feb 1, 2016 12:11 PM, "Kevin Funk" <kfunk at kde.org> wrote:
> Heya Pavel & Nicolai,
>
> How are you doing? :)
>
> Has there been any progress or communication going on with regards to the
> kdev-go plugin? I'd love to see it emerge a bit more, since Go appears to
> be
> getting more and more popular. You two seemed interested into driving the
> project further (cf. [3])
>
> Have you been able to look into the go parsing package [1] or gocode [2],
> and
> try out if it's feasible to use one of them instead of leveraging your Go
> custom parser?
>
> During my visit to FOSDEM I've seen some interest of people in driving the
> KDevelop Go integration further, so your input would be very welcome!
>
> If there's interest, we could also try packaging the efforts as a Google
> Summer of Code project during 2016, where one of you guys (if eligible)
> could
> work on it.
>
> Cheers,
> Kevin
>
> [1] https://golang.org/pkg/go/parser/
> [2] https://github.com/nsf/gocode
> [3] https://mail.kde.org/pipermail/kdevelop-devel/2014-August/048702.html
>
> --
> Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160201/e641f610/attachment-0001.html>
More information about the KDevelop-devel
mailing list