faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: "Kuanta" ...are you kidding or what?
by Eric Laffoon on Tuesday 26/Jul/2005, @19:56
|
I don't know of any plans to do a parser like you describe. Parsers are tedious and involved code that takes a lot of time and debugging. As far as providing better error messages I think your example shows how much more complex it really is. For a relevent changed method message you would need persistant memory of changes for both files which would be like incorporating a revision system into a parser. It's an interesting idea, but parsers have to process so much data optimization is a key factor and making them revision aware would likely be a nightmare and slow. A more ideal system would be to offer the option to find and change the relevent method calls in the project or put them in an edit queue. My preference in adding automation is that it actively seeks to reduce errors.
BTW I am not aware of everything going on with the KDevelop parser, just what we've been doing with Quanta so far. That's the perspective I'm looking at. It will be exciting to review using their parser in places or possible integration and modular parsing concepts. We will have inherent differences as well as similarities. |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
