From: Roman Shaposhnick <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] kenc
Date: Wed, 2 May 2007 20:39:36 -0700 [thread overview]
Message-ID: <1178163576.16650.1787.camel@work.sfbay.sun.com> (raw)
In-Reply-To: <4637917B.19AC54E1@null.net>
On Wed, 2007-05-02 at 08:32 +0000, Douglas A. Gwyn wrote:
>
> I don't see any way to undo the situation..
C at least has a luxury of vectoring off all the eager beavers
to a C++ committee, where languages like Fortran don't have
a Fortress to protect them from mutilation yet (pun intended).
Thanks,
Roman.
prev parent reply other threads:[~2007-05-03 3:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 9:33 Saint Sexburga
2007-05-01 10:48 ` Russ Cox
2007-05-01 11:48 ` Uriel
2007-05-02 8:32 ` Douglas A. Gwyn
2007-05-03 3:39 ` Roman Shaposhnick [this message]
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=1178163576.16650.1787.camel@work.sfbay.sun.com \
--to=rvs@sun.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).