From owner-freebsd-current  Thu Jan 28 01:39:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA16667
          for freebsd-current-outgoing; Thu, 28 Jan 1999 01:39:13 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16662
          for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:39:10 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA30919;
	Thu, 28 Jan 1999 20:39:03 +1100
Date: Thu, 28 Jan 1999 20:39:03 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280939.UAA30919@godzilla.zeta.org.au>
To: bde@zeta.org.au, luigi@labinfo.iet.unipi.it
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
Cc: current@FreeBSD.ORG, grog@lemis.com, peter.jeremy@auss2.alcatel.com.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>not speaking about vinum, but to me, the indentation of 8 char and
>line length of 80 chars are almost mutually exclusive.
>
>See e.g. tcp_input.c ip_input.c and many network device drivers as
>an example -- basically all places where, for efficiency reasons,
>the code tries to expand in-line various block, the depth of
>indentation pushes everything to the right end leaving only 20-30
>useful chars per line.

See the Linux style guide (linux/Documentation/CodingStyle) for
strong opinions about this: "if you need more than 3 levels of
indentation, you're screwed anyway, and should fix your program".

I almost agree.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message