Re: [anjuta-devel] Code assistance plugin
- From: Ignacio Casal Quinteiro <nacho resa gmail com>
- To: Sébastien Granjoux <seb sfo free fr>
- Cc: anjuta-devel-list <anjuta-devel-list gnome org>
- Subject: Re: [anjuta-devel] Code assistance plugin
- Date: Fri, 13 Apr 2012 23:20:35 +0200
Hey hey,
for libgee you need the 0.6 branch version which is the one
included in all distributions, for some reason the api is 1.0
in the 0.6 branch while in master is 0.8.
Regards.
2012/4/13 Sébastien Granjoux
<seb sfo free fr>
Hi Massimo,
Le 13/04/2012 22:13, Massimo Cora' a écrit :
I have never used it. Trying to compile brings to an error as
make[2]: Entering directory
`/home/pescio/gitroot/gedit-code-assistance/src'
make[2]: *** No rule to make target `gcp.vapi', needed by `all'. Stop.
even if the configure process ends fine.
I have just tried here and get the same error. In addition the configure script is looking for gee-1.0 while after compiling the latest version of libgee from GNOME git I get only gee-0.8.
please forgive me if I'm wrong, but from what I see, and from what I
already wrote here https://bugzilla.gnome.org/show_bug.cgi?id=660025#c5
clang doesn't support a symbol parsing as it's ctags.
So giving a list of symbols or autocompletion seems difficult to me.
Checking the clang manual it doesn't mention anything about the symbols,
but it's a static code analyzer, which instead ctags isn't.
I have looked a bit at clang manual and it looks very thin or I haven't found it. It looks like you get information rather in tutorials or by reading the code directly.
even if ctags is a dead project, it could detect symbols and their
types, which isn't that bad. Some more info would be really appreciated
on the scanned symbols, but, again, to me ctags seems the only
opensource choice, with its pros and cons.
I think you can get a syntax tree after parsing a file, I imagine that you can search for symbols too. It will be a bit different from ctags though because I think at least preprocessor macros are expanded. But I'm not sure neither.
Anyway to me it seems that they can be used both, they could be
complementary but not exclusive.
I think we can use both. But I think it would be useful to separate the parsing part (using ctags currently) from the symbol-db plugin. So we could have for C, a parser plugin which is using clang instead/and ctags and for the other languages ctags or something else. It's quite different from the architecture of the gedit-code-assistance plugin though.
Regards,
Sébastien
--
Ignacio Casal Quinteiro
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]