Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Mar 2012 11:47:42 +1030
From:      "Daniel O'Connor" <doconnor@gsoft.com.au>
To:        Mark Linimon <linimon@lonesome.com>
Cc:        Doug Barton <dougb@freebsd.org>, John Baldwin <jhb@freebsd.org>, svn-src-all@freebsd.org, Dimitry Andric <dim@freebsd.org>, src-committers@freebsd.org, Bruce Evans <brde@optusnet.com.au>, svn-src-head@freebsd.org, Chris Rees <utisoft@gmail.com>
Subject:   Re: svn commit: r233052 - head/share/mk
Message-ID:  <373E5B77-704B-4E40-BBAB-10A54BA3A6E5@gsoft.com.au>
In-Reply-To: <20120321004836.GB30795@lonesome.com>
References:  <201203162319.q2GNJjx5039482@svn.freebsd.org> <201203201019.40486.jhb@freebsd.org> <CADLo839Ef3bu_14AdexOWapOacFLk3MM9HK-oNLmtA52Cc9C6w@mail.gmail.com> <201203201728.21049.jhb@freebsd.org> <20120321004836.GB30795@lonesome.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 21/03/2012, at 11:18, Mark Linimon wrote:
> Personally, I'd like to see us pick a "recommended way for new code",
> whether it's one or two spaces, whatever.  (8 spaces seems too much.)

2 space indents are fine IMO, but they are spaces.

A tab character should be viewed as 8 spaces wide, but that doesn't =
force you to have 8 space wide indents.

If you change tab width then you need to teach each editor and viewer =
that could possibly read your file what that width is, which is =
basically an impossible task.

Yes using just spaces, or coalescing 8 spaces into a tab uses more disk =
space than just tabs, but that amounts to sweet FA these days.

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C









Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?373E5B77-704B-4E40-BBAB-10A54BA3A6E5>