From: itz@very.loosely.org (Ian Zimmerman)
Subject: [TUHS] margins and indenting, and arbitrary c rules
Date: Fri, 10 Nov 2017 10:41:30 -0800 [thread overview]
Message-ID: <20171110184130.uuptimhldoudqvv3@matica.foolinux.mooo.com> (raw)
In-Reply-To: <20171109153151.3801118C0BC@mercury.lcs.mit.edu>
On 2017-11-09 10:31, Noel Chiappa wrote:
> Now that I think about it, I may have subconciously absorbed this from
> Ken's and Dennis' code in the V6 kernel. Go take a look at it: more
> than one level of indent is quite rare in anything there (including
> tty.c, which has some pretty complex stuff in it).
It has also been the preferred coding style in Perl, I think right from
the beginning. I'm sure it's written down somewhere, maybe even by
Larry Wall.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.
next prev parent reply other threads:[~2017-11-10 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 15:31 Noel Chiappa
2017-11-10 18:41 ` Ian Zimmerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-09 16:03 Noel Chiappa
2017-11-09 15:09 Noel Chiappa
2017-11-09 15:41 ` Don Hopkins
2017-11-09 19:13 ` Ron Natalie
2017-11-09 8:07 Steve Simon
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=20171110184130.uuptimhldoudqvv3@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
/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).