<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">>Additionally, I suspect we'd welcome code to do more in this area into the tree. I <br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">>think clang would be a good place to do this.<br>>Also, because clang (and llvm) is built and designed as a set of <br>>useful libraries for solving all sorts of problem, if there is a rough <br>>area where the design could be improved to meet your specific needs, I <br>>think we are interested in have that flexibility in clang.<br> Refactoring is my goal as well. I was originally attracted to clang because its design yields a much more expressive tree structure with detailed source
locations, this makes refactoring easy in many situations. I had a brief list of refactorings that I had worked on, for example renaming functions and variables, moving sections of code to different files and listing #include's which are not required in a given translation unit. If there was some community interest in this, I would very much like to contribute my work. One area which I have not spent enough time thinking about is what an interface for refactoring should look like. If people had some suggestions regarding what they would like to see and how the respective pieces should interact I would appreciate it. <br>Patrick <br></div><br></div></div><br>__________________________________________________<br>Do You Yahoo!?<br>Tired of spam? Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com </body></html>