On Sunday 06 April 2008 17:15:15 DavidW wrote:
> The 80char/line rule made sense when variable names couldn' t be over
> a few chars and OOP didn't allow
> aVeryLongBaseName.anEvenLongerMethodName('a string which is even
> longer and is hard to break.')
> type practice. Anyway I'm not interested in banging on about that
> (I'll leave the banging in MAX users)
> Readability is very important and lack of it causes bugs.
> I do not think it coincidental, for eg. that the very section with the
> error in it is where 'tab' had gotten down to 2 chars.
>
> Attached is an (almost) 80char/line clean version. I've left a ruler
> in where there's an overrun of more than a couple of chars.

You seem to have used another version? This file still uses util.getPlatform 
instead of util.platform.

> I hope it's of some use. Two ways to reduce the number of these would be
> 1. factor often used char strings, such as "CONFIGURATION DECISION: "
> to something smaller and add, as appropriate

There's already some of this, although it's not implemented everywhere: see 
util.confDecision and util.fatal.

> 2. Abbreviate some of the Method names (Eg use Environ or Ement for
> Environment)

3. Break lines at function arguments and other places, eg
someClass.someFunction(oneArgument,
	otherArgument)


-- 
Felipe Sateler