From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [even more off topic] 'The Practice of Programming' &
Date: Thu, 31 Jul 2003 09:27:20 -0700 [thread overview]
Message-ID: <3F294368.4020809@nas.com> (raw)
In-Reply-To: <d34707bf724ad58495e4a1d8444bce8e@caldo.demon.co.uk>
Charles Forsyth wrote:
> it does produce quite attractive output (pm obviously, not cfront).
> i simply use the old binary on current Plan 9.
Is there any particular reason why pm was written in C++ and not C?
Intern project? Easier? Heritage from Some Other Unix?
I'm not familiar with it at all. Where does/did it fit in the troff
chain? Is there anything that replaces it now?
-Jack
next prev parent reply other threads:[~2003-07-31 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 17:11 rob pike, esq.
2003-07-30 17:21 ` andrey mirtchovski
2003-07-31 8:52 ` Ralph Corderoy
2003-07-31 15:25 ` rob pike, esq.
2003-07-31 16:03 ` Charles Forsyth
2003-07-31 16:07 ` Fco.J.Ballesteros
2003-08-01 4:33 ` Lucio De Re
2003-08-01 4:48 ` rob pike, esq.
2003-08-01 5:08 ` Lucio De Re
2003-08-01 5:35 ` Lucio De Re
2003-08-01 5:37 ` Skip Tavakkolian
2003-07-31 16:27 ` Jack Johnson [this message]
2003-07-31 16:31 ` rob pike, esq.
2003-07-31 17:20 ` Scott Schwartz
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=3F294368.4020809@nas.com \
--to=fragment@nas.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).