>> ifTrue: [ >> line1 yo. >> line2 eh ] > > Horrible, horrible, horrible ;) Poor block. The block is an object...
Exactly what I was thinking; and how some of the new editor features since 3.9, that seem to reify "statements". For example, clicking inside parens or square-brackets selects that statement(s). I also really enjoyed the ability to "surround", thereby creating additional statement-levels. The whole interaction becomes much more liked working with tiled code rather than a text-editor. > I think the conclusion has to be (and I can confirm that the VisualWorks > team was equally divided) that no one formatting regime will make every one > happy and that all regimes will make a substantial minority unhappy. So > perhaps we should step up to having code formatted automatically according > to tailorable preferences. > My only concern is comment formatting but the way to deal with that is to > use automatic formatting and deal with comment problems as they arise. I > always used to be concerned about e.g. comments spanning multiple lines. > But without day to day exposure I don't think one can know how much of an > issue it is. As someone who's logged 5-digits of hours in Squeak these last few years, I think the best thing is to just not. Let 'em wrap! Use shout to turn them light gray, so they don't really intrude on the code, but are there if you want focus on the extra prose. Unfortunately, the real problem with comments within BlockNodes is how they duplicate themselves within the parse-tree.. ouch! I hope that is what you and Nicolas were talking about or that you'll have a fix for that.. > One upside will be less effort reformatting when indent levels change. Have > you noticed that Smalltalk tends to be more difficult to reformat than C > syntax languages, I guess because of keywords? Not having to worry about > this could be great. Very cool, I hope there'll be enough additional consensus to adopt these Beckian formats for Squeaks pretty-print refinement. > Of course, what format gets written to a source file could still be a source > of conflict ;) We may all want our syntax to be the format of record :) Absolutely. To not, would be the machine dictating to the user. Invoking automatic formatting is always the users choice. browseWithPrettyPrint allows readers to have it formatted dynamically if they wish.. Cheers.. > P.S. and don't get me started on the trailing period (putrid excressence), > or the space between ^ and the return expression (vomitous mass). _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
