From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] A new language for Plan 9
Date: Mon, 5 May 2008 14:32:16 +1000 [thread overview]
Message-ID: <775b8d190805042132i7b2493c7n60d2f07e8d047423@mail.gmail.com> (raw)
In-Reply-To: <5F6CBD28-FC04-4D68-AA60-B36568DE7005@mac.com>
wow, sounds like a freshman assignment. don't steal ".b" from limbo, use limbo.
brucee
On Mon, May 5, 2008 at 11:45 AM, Pietro Gagliardi <pietro10@mac.com> wrote:
> I put up a new Bentley. This has support for, hopefully, all control
> structures:
>
> if e then if..then
> s
> if e then if..then..else
> s
> else
> s
> while e do while..do
> s
> loop loop (infinite loop)
> s
> repeat repeat..until (like
> do..while(!))
> s
> until e
> for i := e to e [by e] do like in pascal, but
> with steps
> s
> for i := e downto e [by e] do like in pascal, but with steps
> s
>
> The file asm.b is a simple demonstration of the last two.
>
> The Bentley compiler, when built, is named #b, so the 386 compiler (and the
> only one so far) is 8b. The name is changed on build. This is used exactly
> like the C compilers:
>
> 8b asm.b
> 8l -o asm asm.8
> asm
>
> The -S option produces an Assembly listing, but does not build (the C
> compilers do).
>
> My only regret so far is that for loops generate a medium sized piece of
> spaghetti (yum). See the comment in 8.c for details.
>
> Set for the next release: arguments in procedures, functions, a more
> sophisticated stack size algorithm, bit arrays.
>
>
>
next prev parent reply other threads:[~2008-05-05 4:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 1:23 Pietro Gagliardi
2008-05-02 1:26 ` erik quanstrom
2008-05-02 2:21 ` Pietro Gagliardi
2008-05-02 2:34 ` Pietro Gagliardi
2008-05-07 9:24 ` Matt Erickson
2008-05-08 2:22 ` Pietro Gagliardi
2008-05-11 23:04 ` Pietro Gagliardi
2008-05-02 1:52 ` Rob Pike
2008-05-02 1:12 ` Federico G. Benavento
2008-05-02 2:22 ` Pietro Gagliardi
2008-05-02 1:53 ` Rob Pike
2008-05-02 2:19 ` Pietro Gagliardi
2008-05-02 3:22 ` Robert William Fuller
2008-05-02 12:34 ` Chad Dougherty
2008-05-02 14:43 ` Robert William Fuller
2008-05-03 14:07 ` David Arnold
2008-05-03 15:47 ` lucio
2008-05-03 23:28 ` Skip Tavakkolian
2008-05-03 23:32 ` Bruce Ellis
2008-05-03 23:50 ` Pietro Gagliardi
2008-05-04 2:43 ` Eric Van Hensbergen
2008-05-04 5:16 ` Steve Simon
2008-05-04 5:42 ` Bruce Ellis
2008-05-04 7:42 ` John Stalker
2008-05-04 7:48 ` Steve Simon
2008-05-04 7:57 ` lucio
2008-05-04 12:18 ` Bruce Ellis
2008-05-04 13:48 ` Pietro Gagliardi
2008-05-04 15:03 ` Eric Van Hensbergen
2008-05-05 1:45 ` Pietro Gagliardi
2008-05-05 2:24 ` andrey mirtchovski
2008-05-05 3:58 ` erik quanstrom
2008-05-05 10:16 ` Pietro Gagliardi
2008-05-05 4:32 ` Bruce Ellis [this message]
2008-05-02 4:25 ` ron minnich
2008-05-02 4:41 ` John Barham
2008-05-02 4:54 ` ron minnich
2008-05-02 5:01 ` John Barham
2008-05-02 4:39 ` John Barham
2008-05-02 5:07 ` andrey mirtchovski
2008-05-02 12:12 ` erik quanstrom
2008-05-02 5:07 ` John Barham
2008-05-02 12:07 ` erik quanstrom
2008-05-02 7:49 ` John Stalker
2008-05-02 8:42 ` Bakul Shah
2008-05-02 9:24 ` Martin Neubauer
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=775b8d190805042132i7b2493c7n60d2f07e8d047423@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@9fans.net \
/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).