From owner-freebsd-current Thu Jan 28 00:19:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06047 for freebsd-current-outgoing; Thu, 28 Jan 1999 00:19:19 -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 AAA06033 for ; Thu, 28 Jan 1999 00:19:16 -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 TAA23954; Thu, 28 Jan 1999 19:19:12 +1100 Date: Thu, 28 Jan 1999 19:19:12 +1100 From: Bruce Evans Message-Id: <199901280819.TAA23954@godzilla.zeta.org.au> To: bde@zeta.org.au, grog@lemis.com Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h) Cc: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> It would be nice if style(9) documented the options to give indent(1) >>> to match the `approved' layout convections. (This would reduce the >>> effort involved in importing large chunks of code). >> >> This is impossible, since indent(1) is buggy and out of date with both >> KNF and C. > >Well, you can do a certain amount. In fact, I use GNU indent and >achieve a reasonable approximation. I see no evidence of this. vinum sources don't seem to have a single line in KNF, except accidentally. They have an indentation of 4 instead of 8, lots of per-statement comments, lots of lines longer than 80 characters, lots of block comments without `/*' and `*/' on a line by themself, ... >It would be nice to import it, >but it doesn't comply with style(9) :-) style(9) only applies to non-contrib'ed sources. e.g., vinum :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message