From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 VM for Windows/Linux?
Date: Tue, 26 Nov 2002 09:49:58 +0000 [thread overview]
Message-ID: <3DE31D74.8050905@null.net> (raw)
In-Reply-To: <8dabe8463035c3181ba033ac7d104e9f@collyer.net>
Geoff Collyer wrote:
> As for a C compiler generating Dis, I believe that Dis
> cannot express all the things that one can do in C.
It could be done, by mapping all C objects into a single
large Dis object and all code into a single module, for
example, also providing hooks to get at some of the non-C
features. But why?
next prev parent reply other threads:[~2002-11-26 9:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 6:19 Geoff Collyer
2002-11-26 9:49 ` Douglas A. Gwyn [this message]
2002-11-26 16:24 ` Jack Johnson
2002-11-27 16:45 ` Steven Taschuk
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 1:31 Joel Salomon
2002-11-26 20:47 Keith Nash
2002-11-26 21:01 ` Doc Shipley
2002-11-27 9:40 ` Robin KAY
2002-11-27 18:11 ` Dan Cross
2002-11-30 8:11 ` Doc Shipley
2002-11-30 14:51 ` Dan Cross
2002-12-02 9:58 ` Robin KAY
2002-11-27 10:45 ` Martin C.Atkins
2002-11-26 14:19 Skip Tavakkolian
2002-11-26 18:10 ` suspect
2002-11-26 2:34 Skip Tavakkolian
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=3DE31D74.8050905@null.net \
--to=dagwyn@null.net \
--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).