c++ code completion status report

Christoph Cullmann cullmann at babylon2k.de
Tue Jan 8 21:25:04 UTC 2002

Am Tuesday 08 January 2002 20:41 schrieben Sie:
> Hi!
> > I'd even go further: Why parsing the files over and over to do code
> > completion instead of doing an incremental parse, that is to say: look
> > what changed and change the internal representation of the c code
> > accordingly. That way code completion code be sped up from maybe 30
> > seconds to about one. I reckon, however, that this is much more complex.
> I think that there's another 'problem': The editor has to *tell* the parser
> where the code has changed. And for this we would need an additional
> interface within the KTextEditor interface.
Than make a sample interface and send it too me, will include it in kdelibs if 
it is generic enough ;)


> > Maybe we'd be able to use the internal representation of gcc, or access
> > it through a well defined interface to avoid having to struggle with
> > bison, flex and the c preprocessor at all. If we adopted that approach,
> > the incremental parsing would become a feature of gcc and other IDE's
> > would be able to use it as well.
> Hmmm, I don't think that GCC is the right way to go. What will people do,
> who want to use other compilers then those in the GNU Compiler Collection?
> Okay, we could insert a *compiler code completion interface* or something
> like that.
> Just some thoughts :-).
> Bye,
> 	Victor
> _______________________________________________
> Kdevelop-devel mailing list
> Kdevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
| Christoph Cullmann
| KDE developer
| cullmann at kde.org
| http://www.kde.org

More information about the KDevelop-devel mailing list