9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9's style(6) manual page
Date: Sat,  7 Apr 2018 22:38:20 +0200	[thread overview]
Message-ID: <20180407203820.GA29602@polynum.com> (raw)
In-Reply-To: <20180407131433.6819fa0c7eec6bac85da70c2@eigenstate.org>

On Sat, Apr 07, 2018 at 01:14:33PM -0700, Ori Bernstein wrote:
> On Sat, 07 Apr 2018 19:00:37 +0300, 8halfan@airmail.cc wrote:
> 
> > Just an amateur C programmer looking for answers. My main inspirations for
> > code style is K&R 2nd edition and I'm curious about the instructions in Plan
> > 9's style(6) manual page (for reference, 
> > http://man.cat-v.org/plan_9/6/style). I've
> > tried to think about the motivations, but not everything is as clear as 
> > it seems.
> 
> The manpage explains the reasoning:
> 
>     Ultimately, the goal is to write code that fits in with the
>     other code around it and the system as a whole.
> 
> So, most of the answers to your questions are simply that someone had a
> preference early on. They wrote the code. If you want your code to fit
> in with theirs, this is how to do it.

Indeed. When there are almost as many rational arguments for or
against some choice, this means that the subject is not essential
(there is no "truth"). In this case, for engineering reasons, the
goal shall be consistency: one person ("the chief") decides.
Furthermore, if the code is consistent (in the---french---army we
say: "paumés mais groupés" i.e.  "lost but together") you can apply
regular expressions processing to the whole because there _are_ rules,
if in whatever future the "chief" decides differently...

-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                       http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2018-04-07 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 16:00 8halfan
2018-04-07 17:47 ` Jules Merit
2018-04-07 17:59 ` Digby R.S. Tarvin
2018-04-07 19:11   ` hiro
2018-04-07 20:14 ` Ori Bernstein
2018-04-07 20:38   ` tlaronde [this message]
2018-04-07 20:42   ` Skip Tavakkolian
2018-04-08  4:38   ` Rob Ote

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180407203820.GA29602@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).