Then you end up with, say:
< tab >int[] x = {
< tab >< tab >1, 2, 3, 4, 5,
< tab >< tab >6, 7, 8, 9, 10
};
which you can probably see promotes the structure of the code over its
actual content. I used to think the same, but spending a while in a locked
room with lisp cured me.
--
Skype: ricky_clarkson
UK phone (forwards to Skype): 0161 408 5260
On Wed, May 18, 2011 at 8:15 AM, Casper Bang <[email protected]> wrote:
> > It's easier to write a rule that detects and rejects tabs than it is to
> > detect a bad mixture of tabs and spaces. In the latter, what would
> happen
> > with:
> >
> > < tab >int[] x = {1, 2, 3, 4, 5,
> > < tab > 6, 7, 8, 9, 10};
>
> I would argue, that space characters has no place after a linebreak.
> They should only be used between tokens within a line. NetBeans 7.0
> *finally* got soft linebreaks, so the kind of artistic hard linebreaks
> as shown above, is no longer necessary. Let a person with a 27"
> monitor take full advantage of his screen.
>
> --
> You received this message because you are subscribed to the Google Groups
> "The Java Posse" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
