*NOT FOR REAL USE*
Just an example how Clang's code completion support may be added to the geany. Code is awful, Makefile.in edited by hand, etc. Usage as is not recommended. But prooves the concept and actualy works. I hope someone will fix it so it became usable.
On 27 March 2011 21:09, Alexander Tumin itakingiteasy@gmail.com wrote:
*NOT FOR REAL USE*
Just an example how Clang's code completion support may be added to the geany. Code is awful, Makefile.in edited by hand, etc. Usage as is not recommended. But prooves the concept and actualy works. I hope someone will fix it so it became usable.
Hi,
Nice idea, but I think that this needs to go in a plugin because I don't think we want Geany to have a dependency on clang. You might need to ask for a signal to be emitted from editor_start_autocomplete that you can connect to to call clang.
Cheers Lex
Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Sun, 27 Mar 2011 23:04:44 +1100 Lex Trotman elextr@gmail.com wrote:
On 27 March 2011 21:09, Alexander Tumin itakingiteasy@gmail.com wrote:
*NOT FOR REAL USE*
Just an example how Clang's code completion support may be added to the geany. Code is awful, Makefile.in edited by hand, etc. Usage as is not recommended. But prooves the concept and actualy works. I hope someone will fix it so it became usable.
Nice idea, but I think that this needs to go in a plugin because I don't think we want Geany to have a dependency on clang. You might need to ask for a signal to be emitted from editor_start_autocomplete that you can connect to to call clang.
Another possibility, but will introduce a huge amount of code which needs to be maintained, is to make it a build dependency in kind of switch (#ifdef ...) so it can be turned on by compile time and would not cause a hard, extra dependency.
Cheers, Frank
Another possibility, but will introduce a huge amount of code which needs to be maintained, is to make it a build dependency in kind of switch (#ifdef ...) so it can be turned on by compile time and would not cause a hard, extra dependency.
... huge amount of code that needs to be maintained...
I think you just provided your own answer :-)
Cheers Lex
Le 03/04/2011 14:37, Lex Trotman a écrit :
Another possibility, but will introduce a huge amount of code which needs to be maintained, is to make it a build dependency in kind of switch (#ifdef ...) so it can be turned on by compile time and would not cause a hard, extra dependency.
... huge amount of code that needs to be maintained...
I think you just provided your own answer :-)
+1
Moreover this would mean the feature is only available for those who build Geany themselves, or it'd become a hard dependency. So I think that Lex's suggestion is far better, may be implemented if somebody actually need it.
Cheers, Colomban
On Sun, 03 Apr 2011 14:45:13 +0200, Colomban wrote:
Le 03/04/2011 14:37, Lex Trotman a écrit :
Another possibility, but will introduce a huge amount of code which needs to be maintained, is to make it a build dependency in kind of switch (#ifdef ...) so it can be turned on by compile time and would not cause a hard, extra dependency.
... huge amount of code that needs to be maintained...
I think you just provided your own answer :-)
+1
Moreover this would mean the feature is only available for those who build Geany themselves, or it'd become a hard dependency. So I think that Lex's suggestion is far better, may be implemented if somebody actually need it.
Couldn't have said it better :).
Regards, Enrico
On Sun, 03 Apr 2011 14:45:13 +0200 Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 03/04/2011 14:37, Lex Trotman a écrit :
Another possibility, but will introduce a huge amount of code which needs to be maintained, is to make it a build dependency in kind of switch (#ifdef ...) so it can be turned on by compile time and would not cause a hard, extra dependency.
... huge amount of code that needs to be maintained...
I think you just provided your own answer :-)
+1
Moreover this would mean the feature is only available for those who build Geany themselves, or it'd become a hard dependency. So I think that Lex's suggestion is far better, may be implemented if somebody actually need it.
Just wanted to show another opportunity ;)
Cheers, Frank