From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] v8 shell
Date: Mon, 17 Nov 2003 12:13:29 +0000 [thread overview]
Message-ID: <a480d54509744ad8744679ac79a8fa91@caldo.demon.co.uk> (raw)
In-Reply-To: <qOudnaPaG6Ox4yiiRVn-hg@comcast.com>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
perhaps but it's not clear cut.
the bourne shell was quite tidy, but as with many hand-written
recursive descent implementations, it did cheat a few times.
i did do a yacc grammar for its language for a clone, based originally
on the BSTJ paper without sight of the code, but that grammar had to
be weakened in several places, with help from the scanner as i recall,
in order to handle `real' bourne shell scripts when i finally
had access to the bourne implementation and enough real shell scripts.
i'd be more precise but it must be a good 25 years or so
later, and i can't remember the details; not least because
i've moved on and i've got plenty of non-70's things to remember.
(that isn't to suggest that earlier things weren't much better
than some current `inventions', but that's perhaps not so
much a commendation of the old as
a condemnation of the self-styled `new'.
[-- Attachment #2: Type: message/rfc822, Size: 2406 bytes --]
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] v8 shell
Date: Mon, 17 Nov 2003 10:26:06 GMT
Message-ID: <qOudnaPaG6Ox4yiiRVn-hg@comcast.com>
boyd, rounin wrote:
> big feature of rc is that it has a yacc grammar.
> bourne's shell and it's derivitives had no such thing.
It wasn't implemented using YACC, but it certainly had
a grammar.
next prev parent reply other threads:[~2003-11-17 12:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.21.0311131606190.27715-100000@zenon.ceid.upatras.gr>
2003-11-13 16:06 ` Taj Khattra
2003-11-13 17:41 ` rob pike, esq.
2003-11-13 23:44 ` George Michaelson
2003-11-14 0:43 ` rog
2003-11-14 6:59 ` boyd, rounin
2003-11-17 10:26 ` Douglas A. Gwyn
2003-11-17 12:13 ` Charles Forsyth [this message]
2003-11-18 9:48 ` Douglas A. Gwyn
2003-11-14 12:04 ` John Murdie
2003-11-14 18:01 ` rog
2003-11-14 19:04 ` boyd, rounin
2003-11-14 19:18 ` rog
2003-11-14 19:31 ` boyd, rounin
2003-11-14 22:25 ` Roman Shaposhnick
2003-11-16 11:45 ` Richard Miller
2003-11-16 12:01 ` Geoff Collyer
2003-11-16 12:21 ` Richard Miller
2003-11-17 20:31 ` rog
2003-11-16 14:23 ` Russ Cox
2003-11-16 14:35 ` Richard Miller
2003-11-15 15:03 ` a
[not found] ` <oprykztjlztsux9g@smtp.borf.com>
2003-11-14 0:41 ` boyd, rounin
2003-11-14 17:51 ` rog
2003-11-14 18:51 ` boyd, rounin
2003-11-17 10:26 ` Douglas A. Gwyn
2003-11-14 7:05 ` boyd, rounin
2003-11-14 8:13 boyd, rounin
2003-11-14 18:12 Richard C Bilson
2003-11-14 19:09 ` rog
2003-11-14 19:12 ` boyd, rounin
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=a480d54509744ad8744679ac79a8fa91@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).