From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: programming style under Plan9??
Date: Fri, 1 Apr 2005 22:54:36 -0500 [thread overview]
Message-ID: <ee9e417a05040119546b16d4d1@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0504012026300.14759@cps211.cps.cmich.edu>
> I have observed that that the Plan9 C-code generally
> consists fo ALL modules of a program are in the same file.
I don't think this is true at all.
Sure it's true of /sys/src/cmd/*.c, but that's
the directory that contains all the one-file programs,
and most of them are tiny enough that splitting them
up would just be annoying (there are exceptions).
But there are plenty of programs that are split into
separately compiled pieces, both in the sense of
libraries and just multiple files for different pieces
(look in /sys/src/cmd/acme for example).
I split my programs into pieces that make it easier
for me to think about. If that happens to coincide
with what some people call modules, great, and
if it doesn't, well too bad for them.
Russ
next prev parent reply other threads:[~2005-04-02 3:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 1:34 I RATTAN
2005-04-02 2:40 ` Ronald G. Minnich
2005-04-02 3:34 ` Brantley Coile
2005-04-02 4:06 ` Russ Cox
2005-04-04 9:56 ` Gorka Guardiola
2005-04-04 13:24 ` jmk
2005-04-04 14:20 ` Charles Forsyth
2005-04-02 9:31 ` Charles Forsyth
2005-04-02 9:56 ` noselasd
2005-04-02 19:31 ` jmk
2005-04-02 20:57 ` Devon H. O'Dell
2005-04-02 22:08 ` jmk
2005-04-02 12:36 ` Brantley Coile
2005-04-02 3:54 ` Russ Cox [this message]
2005-04-02 13:11 ` I RATTAN
2005-04-02 15:50 ` Ronald G. Minnich
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=ee9e417a05040119546b16d4d1@mail.gmail.com \
--to=russcox@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).