Date: Fri, 10 Oct 1997 08:49:12 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: Major number requested Message-ID: <19971010084912.ZA64319@uriah.heep.sax.de> In-Reply-To: <19971010155311.58360@lemis.com>; from Greg Lehey on Oct 10, 1997 15:53:11 %2B0930 References: <Pine.SGI.3.95.971008190216.13566A-100000@shellx.best.com> <Pine.SGI.3.95.971008234128.3136A-100000@shellx.best.com> <19971009203311.QE10395@uriah.heep.sax.de> <343D4AD9.794BDF32@whistle.com> <19971010072220.HE00812@uriah.heep.sax.de> <19971010155311.58360@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As Greg Lehey wrote:
> > ...or use Emacs with the appropriate style description. :-)
>
> That's a new one on me. Last time I looked, you didn't get much
> choice. Pointer?
My own Emacs is stone-aged. I'm using c++-mode.el (but i think this
has been renamed since), and i've added a submenu that allows me for a
number of choices for the C style. This is rather hacked, but i have
yet to find the time to make it right (probably after upgrading Emacs
to a current version, now that i've got enough disk space to do this).
(defconst bsd-c-style
'("FreeBSD"
(c-basic-offset . 8)
(c-tab-always-indent . t)
(c-hanging-braces-alist . ((substatement-open after)
(brace-list-open)))
(c-hanging-colons-alist . ((member-init-intro before)
(inher-intro)
(case-label after)
(label after)
(access-label after)))
(c-cleanup-list . (scope-operator
empty-defun-braces
defun-close-semi))
(c-offsets-alist . ((arglist-close . c-lineup-arglist)
(substatement-open . 0)
(case-label . 0)
(block-open . 0)
(knr-argdecl-intro . -)))
)
"FreeBSD C Programming Style")
Note that the above is not fully style(9)-compliant. I think other
people might have better pointers. I know that K&R function arguments
are not indented, and despite of style(9), i prefer expression
continuation lines being indented to the level the original expression
started (as opposed to 4 spaces as style(9) says).
> > Better repair indent(1) before using it. See the Unix Hater's
> > Handbook for a description of its flaws.
>
> I've hacked enough of them myself. They're too deep for anything
> short of a rewrite to fix.
I think so. I once tried, but eventually gave up. The worst thing is
that the entire file is copied, and then written over the original
file, instead of creating a new file with just the modified contents
(and rename everything in the end).
> What about a pointer to the UHH?
ISBN 1-56884-203-1
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971010084912.ZA64319>