c++ code completion status report
Victor_Roeder at GMX.de
Tue Jan 8 20:39:02 UTC 2002
> 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.
> 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 :-).
More information about the KDevelop-devel