Date: Fri, 13 Jul 2007 07:34:10 -0700 From: Sam Leffler <sam@errno.com> To: syrinx@freebsd.org Cc: Kostik Belousov <kostikbel@gmail.com>, "Constantine A. Murenin" <cnst@freebsd.org>, Perforce Change Reviews <perforce@freebsd.org>, Alexey Tarasov <glorgster@gmail.com>, Hans Petter Selasky <hselasky@c2i.net> Subject: Re: PERFORCE change 123376 for review Message-ID: <46978D62.8000100@errno.com> In-Reply-To: <61b573980707122359y43bb9ec4gf76892e619cc8599@mail.gmail.com> References: <200707121428.l6CESBSj045007@repoman.freebsd.org> <46965433.6050207@FreeBSD.org> <200707121831.22913.hselasky@c2i.net> <db2194de0707121840i2dc5de1fj614c7b4efad7b9d7@mail.gmail.com> <20070713034425.GH2200@deviant.kiev.zoral.com.ua> <61b573980707122359y43bb9ec4gf76892e619cc8599@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[picking a random reply] Shteryana Shopova wrote: > style(9) says: > <quote>Many of the style rules are implicit in the examples.</quote> ;) > > IMO it is a good idea to try to keep to the rules while coding. Also > all code lines should (must ;)) contain 80 characters max. Folks, before things get too out of hand, please remember there are only 2 ironclad rules about style: 1. style(9) is a guideline and not a contract 2. existing style trumps any rules in style(9) (i.e. when modifying existing code) The point being that one shouldn't get too hungup about the exact form of this person's code. The convention+practice codified in style(9) represents the agreed upon common style to use but failing to follow some rules doesn't justify getting bent out of shape. Given them advise, sure. Point out the man page, absolutely. If you program long enough you will find your personal coding style varies widely (often to suit the project environment). Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46978D62.8000100>