9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ronald G Minnich <rminnich@lanl.gov>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] EROS, Vapour
Date: Mon,  3 Sep 2001 11:17:24 -0600	[thread overview]
Message-ID: <Pine.LNX.4.33.0109031116170.25593-100000@snaresland.acl.lanl.gov> (raw)
In-Reply-To: <3B8FF174.B3795343@null.net>

On Mon, 3 Sep 2001, Douglas A. Gwyn wrote:

> Eyal Lotem wrote:
> > The whole *point* behind Vapour is that it uses a safe language, rather
> > than damage-prevention hardware protection, ...
> > A serious advantage of Vapour for example, is since it doesn't reuqire
> > hardware protection, ...
>
> ? How on Earth can Vapour tell whether or not an access to e.g. serial
> port #0 is "safe"?
>

And why doesn't anybody ever seem to know that Burroughs plowed this
furrow for 25 years with no real good effect.

It's always fun when a user program brings down a mainframe due to a
compiler bug ...

ron



  reply	other threads:[~2001-09-03 17:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29  9:04 Eyal Lotem
2001-08-29 13:40 ` Rick Hohensee
2001-08-29 14:42   ` Ronald G Minnich
2001-08-29 15:48     ` Boyd Roberts
2001-08-31  8:45       ` Eyal Lotem
2001-09-03  8:39         ` Douglas A. Gwyn
2001-09-03 17:17           ` Ronald G Minnich [this message]
2001-08-29 14:37 ` Ronald G Minnich
2001-08-29 15:46   ` Boyd Roberts
2001-08-29 15:52 ` Boyd Roberts
2001-08-30 15:58   ` Douglas A. Gwyn
2001-08-30 15:57 ` [9fans] " Douglas A. Gwyn
2001-08-30 18:19 [9fans] " David Gordon Hogan
2001-08-31  8:53 forsyth
2001-08-31 18:13 David Gordon Hogan

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=Pine.LNX.4.33.0109031116170.25593-100000@snaresland.acl.lanl.gov \
    --to=rminnich@lanl.gov \
    --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).