9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: pip@namaste.stricca.org
To: brucee@plan9.bell-labs.com
To: 9fans@cse.psu.edu, brucee@plan9.bell-labs.com
Subject: Re: [9fans] Mash
Date: Sun, 16 Jul 2000 20:57:43 -0400	[thread overview]
Message-ID: <200007162052.QAA05909@wellington.cnchost.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 485 bytes --]

<junk>
> [that's the C Reference Manual brainiac]
<junk>

Something interesting happened in December 1989. ANSI
adopted what was to become the ANSI C standard, which was
then adopted by ISO and is ISO/IEC standard 9899-1990.  If 
you require a copy, you can get it from ANSI or ISO:

	American National Standards Institute
	11 West 42nd Street
	New York, NY 10036
	Telephone (212) 642-4900

or

	ISO Sales
	Case postale 56
	CH-1211 Geneve 20
	Switzerland
-
pip


[-- Attachment #2: Type: message/rfc822, Size: 3411 bytes --]

From: brucee@plan9.bell-labs.com
To: 9fans@cse.psu.edu, brucee@plan9.bell-labs.com
Subject: [9fans] Mash
Date: Sun, 16 Jul 2000 13:50:19 -0400
Message-ID: <200007161750.NAA09238@cse.psu.edu>

> Does that mean you haven't ported "mash" yet?  :-)  :-)  :-)
>
> I only browsed the mash documentation, but it seemed very intriguing.

Hi, I'm Bruce Ellis - a friend of Mark Shaney's - and
I wrote mash.  There was a plan to replace mk either
by adding loadable module support to rc or by more or
less a mash port.  It's syntax is almost identical to rc
though I got rid of the "if not" wart by some deft but
perhaps not totally successful changes.

I actually did the dynamic loader (with much encouragement
from Russ - loadable vga drivers would be nice) but had
too many other things on my plate to do the rest.
(This involved really minor changes to 8l and a small
library file - 240 lines.  I didn't do the other loaders.)

I wrote a paper on mash for Usenix but it was rejected,
though there were some very fine papers on web servers
and perl that could fill its place.  (Sarcasm?)
Maybe I should tidy up the draft and put it somewhere.
You may not understand it though - some of the reviewers
seemed to have trouble with it because it wasn't ksh/nmake.

Let me be naughty and share some of their comments.
Yes, this is so unprofessional.

---
I find nothing interesting or novel or conceptually
appealing about the paper.

[ok - more fool you]

The author states that "a history mechanism probably
doesn't belong in a shell."  Make and Tk do?

[they aren't in the shell boofhead, that's the point]

Is a 1978 AT&T manual the best reference on the C language?

[that's the C Reference Manual brainiac]

What is a "trampoline function"?

[where did you go to school]

On the second last page, you write "mush" instead of "must"

[it's a draft - meant "tush" anyway]

We hope to see you in Monterey!

[eat my shorts]
---

But I digress.  Mash is fun, makes Inferno a better place.
The make loadable module is 723 lines of code.  nmake
is 723 pages of code.

Comments/suggestions welcome - though I don't read 9fans,
Russ forwarded me the mail.

Bruce Ellis
Computing Prototypes Research Group
Bell Laboratories

* Don't meddle in the mouth.

             reply	other threads:[~2000-07-17  0:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-17  0:57 pip [this message]
2000-07-16 21:49 ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2000-11-03 17:25 [9fans] mash rog
2000-11-02 13:20 rob pike
2000-11-02 15:54 ` Rick Hohensee
2000-11-03  9:27   ` Leo Caves
2000-07-18  7:42 [9fans] Mash forsyth
2000-07-18  8:18 ` Lucio De Re
2000-07-18  8:24   ` Lucio De Re
2000-07-17  2:01 pip
2000-07-16 22:21 ` Boyd Roberts
2000-07-16 22:20 brucee
2000-07-16 17:50 brucee
2000-07-17  9:12 ` Chris Locke
2000-07-18  6:27   ` Lucio De Re

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=200007162052.QAA05909@wellington.cnchost.com \
    --to=pip@namaste.stricca.org \
    --cc=brucee@plan9.bell-labs.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 NNTP newsgroup(s).