From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] New language?
Date: Tue, 16 Jul 2002 13:09:13 -0400 [thread overview]
Message-ID: <Pine.LNX.4.30.0207161302390.14125-100000@athena> (raw)
In-Reply-To: <000501c22cee$2608e170$bf356887@bl.belllabs.com>
> be harder than it appears. And there comes a point
> where an extension changes the flavor of a language
> a little too much, and I think this one might be over
> that line.
Too true. What then, a new language based on C pulling the
yummy stuff out of limbo? One that's not interpreted, without
a garbage collector, and no atend >:), but that has tuples, array bounds
checking, etc? At this point should we just considering loosening up
Oberon a little and making a few additions?
I'd be willing to help so long as we fix the BCPL inherited '&'
precedence.
Sam
next prev parent reply other threads:[~2002-07-16 17:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 16:08 [9fans] useful language extension, or no? rob pike, esq.
2002-07-16 15:31 ` Sam
2002-07-16 17:24 ` [9fans] more extensions FJ Ballesteros
2002-07-16 16:26 ` Sam
2002-07-16 17:28 ` Howard Trickey
2002-07-16 17:09 ` Sam [this message]
2002-07-17 5:45 ` [9fans] New language? GBA
2002-07-17 6:23 ` Lucio De Re
2002-07-16 18:23 ` [9fans] more extensions Scott Schwartz
2002-07-16 18:47 ` Dan Cross
2002-07-16 19:05 ` Jon Snader
2002-07-17 8:58 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2002-07-17 7:33 [9fans] New language? Fco.J.Ballesteros
2002-07-17 8:21 ` Lucio De Re
[not found] <nemo@gsyc.escet.urjc.es>
2001-10-09 6:25 ` [9fans] rewriting paths [was: mv vs cp] Fco.J.Ballesteros
2001-10-09 6:41 ` George Michaelson
2001-10-10 9:05 ` Douglas A. Gwyn
2001-10-09 14:19 ` Richard
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.30.0207161302390.14125-100000@athena \
--to=sah@softcardsystems.com \
--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).