Re: Debian coding style?
In article <E10fwkE-0003P2firstname.lastname@example.org>,
Steve Lamb <email@example.com> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>On 7 May 1999 21:35:46 -0400, Amy Fong wrote:
>>I've been interpreting it as actual lines. Now, with the requirements to
>>put all curly braces on its own line _plus_ the need to put curly braces
>>around all if/while/for (including single liners), functionality
> Exactly. And in a language like perl where syntax can be quite
>interesting, the line blurs even more. I mean, is the following...
> ...4 lines...
> ...3 lines...
>die "Ack!\n" unless $blah;
> ...or 1 line? :)
> I'm sure C has similar examples. Point being that I could take that one
>line and make it 4 and, in essence, reduce my allowed "space" by a factor of
>4. Or, conversely, reduce 4 lines into 1 and increase my space.
> I agree with them that excessive function length is bad. Conversely,
>however, is an excessive number of functions. :)
> For reference, my prefered method of the above, in perl, would be:
Hmmmmm... I'd probably end up having to obfuscate the code with lots of
#define's to keep the function within 40-50 lines.
As for perl... well we could probably easily squash it up but it'll
probably fail alot of readability tests. *shiver*
"We Suzaku Seishi aren't smart enough to give up!!!" Tasuki (Fushigi Yuugi)
I don't speak for anyone but myself.