On Nov 22, 2009, at 7:31 PM, Lukas Renggli wrote:
IMHO, the real problem has been a sort of XP snobbery: it appears that those building or integrating what would otherwise be a wonderful tool, have zero interest in preserving comments, and even some contempt for those of who write them.
This has nothing to do with snobbery, it is a technical issue.
I will spare you second-hand comments about what has been done in other languages and editors, as I have never encountered an RB anywhere but Smalltalk.
I know the refactoring engine of Eclipse. It must be 20 years ahead of Smalltalk.
Not sure because it is full of bugs because Java is complex. Now if you give me one engineering for 6 months I guess we can catch up and what you are doing is cool. At Smalltalk diego "gneffer" show a realy extension to RB (and really simple to implement) where you could select a couple of methods and it would check duplicated code and extract the methods automatically.
When saying that one must keep in mind that printing Java code so that it preserves the formatting is easier than to do the same with Smalltalk. Even if they have to handle 100+ AST node types individually, they all have a very strict structure and are rarely nested in unpredictable ways. Furthermore since the editor expands, completes, indents and formats a lot of code automatically anyway, people don't even notice when their code gets reformatted.
I know that we discuss the placement of comment with gwenael too. I think that some heuristics may help. And probably with the simple pretty printer of damien. Stef
Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project