From: "Frank Ch. Eigler" <fche@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: <context> cleanup
Date: Sat, 05 Aug 2000 18:22:00 -0000 [thread overview]
Message-ID: <20000805212244.A12657@redhat.com> (raw)
In-Reply-To: <14732.19780.352341.736963@casey.transmeta.com>
dje wrote:
> While it's on my mind, one thing that needs cleanup
> is the use of <context>. It's passed down to control error message
> reporting. [...]
Sure ... and <estate> should be cleaned up to formalize the
interface to the run-time & language.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5jL3kVZbdDOm/ZT0RAZQyAJ9SX/Ax6HFG3HgcFt0UdMaWG1EsqgCeNYjx
gkVYMOYnOf/eHg2WkrLzFs8=
=gOiF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2000-08-05 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-05 10:22 Doug Evans
2000-08-05 18:22 ` Frank Ch. Eigler [this message]
2000-08-05 23:21 ` Ben Elliston
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=20000805212244.A12657@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).