C++ Parsers for KDevelop (kinda long)

John Zedlewski zedlwski at Princeton.EDU
Fri Feb 25 00:44:53 GMT 2000


 
>    RD> how easy it would be to add grammars for additional languages - such
>    RD> as Java or Perl. Is the OpenC++ parser code easy to adapt to parse
>    RD> other languages?

Hmm... hasn't it been pretty much decided that KDevelop will stick to
C++?  In any case, as long as you use a nice, clean interface, you could
always plug in a different parser pretty simply.  Managing automatic
makefiles, projects, class trees and such would be much harder to port
than this anyways.

> In fact, C++ parsers with error recovery of some kind, can be used to
> highlight errors as you type.
> 
> That's another reason speed becomes so important. If you can reparse every
> second at minimal cost, you can do very very cool things.

JBuilder Foundation does a little of this (it has an "errors" tree) and
it's very cool.  
I agree with most folks, though, that speed is probably priority #1 and
ease of use is #2.  Kind of a shame that OpenC++ wins on one and doesn't
do so great on the other.  
Thanks a lot for the info, Daniel.  Even if KDevelop doesn't use it, I
found the info helpful personally!
--JRZ




More information about the KDevelop mailing list