[prev] [thread] [next] [lurker] [Date index for 2006/06/24]
* Peter da Silva <peter@xxxxxxx.xxx> [2006-06-24 00:10]: > > in which case all attempts to fit it into 80 column lines are > > contortions that serve no other purpose than to distract > > while reading but particularly while writing. > > You're confusing lines and statements. Not at all. > a = function(a fairly complex expression, another expression); > > That fits on one line, but I'm inclined to write it as: > > a = function( > a fairly complex expression, > another expression > ); Yes, so do I. Btw, kudos for *not* writing it as a = function(a fairly complex expression, another expression); as many C people do. Ugh. > Simply because it's easier to read and provides redundancy and > documentation. I was with you up to "easier to read", but uh, where's the redundancy and documentation in that example? > > Any code formatting rule that cannot be formalised so that > > software can do it is a bad formatting rule; > > That's fine, documentation isn't "a formatting rule". You might > as well say the same thing about comment and function name > rules. Not at all the same thing. Code layout and identifier names play in completely different leagues. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>There's stuff above here
Generated at 20:01 on 27 Jun 2006 by mariachi 0.52