From: "Noah Evans" <noah.evans@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9 function names
Date: Thu, 8 Mar 2007 10:17:28 +0900 [thread overview]
Message-ID: <56a297000703071717p428ef9b9j58d671f51f28d142@mail.gmail.com> (raw)
In-Reply-To: <87tzwwvr2t.fsf@wmipf.in-berlin.de>
http://www.lysator.liu.se/c/pikestyle.html
On 3/8/07, Michael Teichgräber <mt@wmipf.in-berlin.de> wrote:
> Hi,
>
> is there a reason why underscores are avoided in most function and
> variable names on Plan 9? I have used this style for a while now, and
> it seems to me that it increases the over-all code readability, as
> names or function calls can be more easily recognized. Without
> underscores one has to look for shorter or more to the point
> function/variable names. But sometimes an ambiguity might remain, since
> words are not separated from each other.
>
> Or, is it just a habit without a specific reason?
>
> Michael
>
next prev parent reply other threads:[~2007-03-08 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 18:36 Michael Teichgräber
2007-03-08 1:17 ` Noah Evans [this message]
2007-03-08 9:38 ` Douglas A. Gwyn
2007-03-08 12:22 erik quanstrom
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=56a297000703071717p428ef9b9j58d671f51f28d142@mail.gmail.com \
--to=noah.evans@gmail.com \
--cc=9fans@cse.psu.edu \
/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).