| RE: [cdt-core-dev] Open C++ Parser |
This is very true, Chris. The last thing we would want is for a refactoring operation to mess up someone's code! That would be a quick way to get a bad reputation...
The parser and the parse information need to be complete and correct. To help address this, we are planning on writing a lot of Junit tests and make them an intrinsic part of our development process. And this not only applies to the parser. The CDT needs to be rock solid for it to reach the adoption level I think it's capable of.
Doug Schaefer
Senior Staff Software Engineer
Rational - the software development company
Ottawa (Kanata), Ontario, Canada
-----Original Message-----
From: Chris McKillop [mailto:cdm@xxxxxxx]
Sent: Friday, December 13, 2002 5:02 PM
To: cdt-core-dev@xxxxxxxxxxx
Subject: Re: [cdt-core-dev] Open C++ Parser
>
> However, to be sure I've sent some email to a couple of S-N folks with
> a bunch of questions. Perhaps we can get a more definitive answer on
> the scalability, performance, and correctness issues. I'll report
> back when I get an answer.
>
Just my thoughts. If we are going to provide any form of refactoring tools
we need to ensure that everything reported is correct. Perhaps not
everything can be reported, but false information could lead to a nightmare
for a developer trying to refactor and ending up with broken code.
chris
_______________________________________________
cdt-core-dev mailing list
cdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-core-dev