[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 66683] Implement Code refactoring
From:       Nick Frangiadakis <frangiadakis () gmail ! com>
Date:       2006-09-07 14:06:14
Message-ID: 20060907140614.29985.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=66683         




------- Additional Comments From frangiadakis gmail com  2006-09-07 16:06 -------
> > b) one should really not attempt to write a parser for something as complex
> > as C++, rather the key to success would be to have an open source compiler
> > such as gcc/openc++ provide its COMPLETE parse tree as some sort of
> > machine-readable (XML/RDF) output (there are already compilers (or patches
> > for gcc) to do exactly this (will post references later!))

> Nice theory, but in practice it does not work. gcc, as a compiler, can only \
> >process valid source files, and if you have some code segment "anything->" \
> > >without right side and semicolon, gcc based solutions just fail. IDEs want to \
> > > >work even when the code is not completely valid, so gcc is no option. Besides, \
> > > > >someone in fact has attempted to write a C++ parser, and has totally \
> > > > > succeeded, >which means better C++ support in KDevelop4 and a portable \
> > > > > parser that also can >be reused by other projects and makes refactoring \
> > > > > easier.

Yet, even providing refactoring ONLY when the project is in a valid state would be \
really neat. In fact, even eclipse (for the simpler Java) requires a valid state in \
many cases. 

Finaly another pointer might be http://www.cs.umd.edu/~jfoster/cqual/


[prev in list] [next in list] [prev in thread] [next in thread]