"Malte S. Stretz" <[EMAIL PROTECTED]> writes:
> Uh, no, please not. That's one thing I always "fix" when I see it (I never
> had the idea this might be intentional -- to me it was just some annoying
> behaviour of some editors, incuding vim). Either always use tabs or always
> use two spaces, but don't mix-and-match.
Mix-and-match, yes!
*Some* editors? It's *both* emacs and vim and it's done as a default in
those because it makes navigation easier. Representing 32 consecutive
columns as spaces is annoying. To turn around Kenneth's argument, in
this day and age when every editor can handle tabs very well, is there
any reason to use spaces slavishly for columns?
> You mean a newline before the curly brace? I think the rule of thumb is to
> do so for subs and big blocks, short blocks may have the curly on the same
> line.
No, just after the first set of declarations.
sub foo {
my ($self, $bar) = @_;
code_here;
}
> Please not 4. Either two or tabs, everything else is a pain in the thumb to
> code with when you don't have a good editor around.
What, are you using edlin or something?
> All the three above should be the same, either 1 or 2, I'd prefer 1.
Why the same? They are separate options for a reason. 1,2,2 I think.
> -sbl :)
Yeah, you lose this one. :-)
Daniel
--
Daniel Quinlan anti-spam (SpamAssassin), Linux,
http://www.pathname.com/~quinlan/ and open source consulting
