at one point gwenael changed the parser to handle comments but apparently the code could not be loaded and it was never integrated. I imagine that now it is too divergent.
Stef On Nov 22, 2009, at 2:44 PM, Schwab,Wilhelm K wrote: > Lukas, > > What about the handling of comments? The RB or its parser, etc. made *no* > attempt to get them in the correct position as presented to the formatter, > making the effort of creating a formatter fairly pointless. If that has > improved, I will take another look, but my instinct is to ask for the RB to > make a list what it would need to reformat so I can take care of it myself - > it was that bad. > > Bill > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Lukas > Renggli > Sent: Sunday, November 22, 2009 7:33 AM > To: [email protected] > Subject: Re: [Pharo-project] (no subject) > >> I still have issues with not preserving code formatting in the latest >> pharo-dev. Particularly, method renaming cause code to be reformatted. > > The formatting cannot be preserved in all cases. For example, if the renamed > method has many arguments or is sent with complex arguments (block, nested > message sends, ...) the code is still reformatted. For the cases where an > automatic formatting is not avoidable, the class RBConfigurableFormatter can > be configured to produce something that is more to your likings. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
