9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A new language for Plan 9
Date: Wed,  7 May 2008 22:22:56 -0400	[thread overview]
Message-ID: <F5E4127F-AE9E-4ED0-A6D9-3BB71161D1D5@mac.com> (raw)
In-Reply-To: <fvnj0q$5kc$3@news.acm.uiuc.edu>

On May 7, 2008, at 5:24 AM, Matt Erickson wrote:

> On 2008-05-02, erik quanstrom <quanstro@quanstro.net> pondered onto
> the tubes:
>>> one does
>>>
>>> 	if key = 'c' then
>>> 			scanline
>>> 			runcommand
>>> 		else
>>> 			generate(key)
>>> 			assemble(key)
>>>
>>> This is similar to Python, and prevents the nesting ambiguity of C,
>>> Pascal, and some other languages that use block delimiters.
>>
>> don't forget fortran.
>
> I try to, oh God how I try to.  Then I come back to work in the
> morning, and have to remember it all over again.
>
> --
> Matt Erickson           <peawee@peawee.net>
> Political correctness is not insane. You want to call it
> "alternatively
> reality-based". - Richard Bos, Usenet
>

Good luck. My next compiler will do Fortran 77, and hopefully 90. It
will be #f, where # is the prefix (so 8f for 386).

A new Bentley is up, in the usual place. This adds full procedures and
functions with arguments, expression statements (like in C), and
demotes assignment from a statement to an operator. The next version
will have it right-associative (a := b := c := 0). I also plan to have
scope.

I'm surprised at how quickly I'm getting through this. I expected some
2 year project getting as much as the Sieve of Erastosthenes to work.




  reply	other threads:[~2008-05-08  2:22 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 [this message]
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
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=F5E4127F-AE9E-4ED0-A6D9-3BB71161D1D5@mac.com \
    --to=pietro10@mac.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).