🚀 go-pugleaf

Tim Tyler wrote:
> In comp.lang.java.advocacy Dale King <KingD@tce.com> wrote:
> : "Roedy Green" <roedy@mindprod.com> wrote in message
> 
> :> I would hope most of the alignment would be automatic.  Programmers
> :> waste far too much time fiddling around with such minutiae an aligning
> :> Java text is some personal anally retentive way.
> 
> : Which was my point that intra-line alignment is not a good idea.
> 
> Intra-line alignment not a good idea?
> 
> You mean things like:
> 
> check("foo",    previous, current);
> check("wibble", current,  next);
> check("parf",   next,     previous);

I wouldn't be caught dead writing like that.  In any event, I think Dale 
meant something more like:

someReallLongeMethodNameWithManyArguments(aReallyLongArgument,
                                           anotherLongArgument,
                                           theLastArgument);
doOtherStuff();
...
...

Sometimes I do it as shown above, and other times I do it like this:

someReallLongeMethodNameWithAlotOfArguments(
         aReallyLongArgument, anotherLongArgument, theLastArgument);
doOtherStuff();
...
...

I haven't settled on a pattern for doing so, but the latter is becoming 
more prevalent in my code because it is immune to changes in the method 
name and parameter name lengths.

> 
> That sounds like one of Dale's more radical ones ;-)
> 
> Call me "anally retentive" - but isn't that useful in conjunction with
> block-editing?

I've yet to find a need for block editing (particularly in Java code), 
but I won't go so far as to say that others don't need it.

Jim S.