From: ara.t.howard@...
Date: 2006-10-06T01:17:36+09:00
Subject: Re: [OT] Re: dynamically changing superclass/mixins

On Fri, 6 Oct 2006, Jeremy Tregunna wrote:

one last comment, and then i'll move over to the io list, since this is really
ot (sorry everyone)...

> Sure. It's really simple actually. Every bit of Io code you see (excluding
> comments) are messages. Io is a message based language, there are no
> keywords, and infact, the only reason comments aren't messages is because I
> havn't completed my patch to Io's parser and lexer to transform #, // and /*
> */ into an actual message yet.
>
> Considering the parse tree for the above can be a little more verbose than it 
> needs to to demonstrate how Io is parsed, I'll draw out the parse tree as a 
> list of lists (try not to think of it as a tree because it's not really). The 
> code example is:
>
> method(a, a * a) call(5); otherStuff
>
> The above is transformed into several messages
>
> --- method --- call
>    | a          5
>    | a - *
>    |     a
>    |- otherStuff
>
>
> (Apologies if your mail client made that look funny.)

would the above be read something like

   m = method a, a * a

   m 5

   otherStuff

??

is the parse non-ambiguous as

   (method a, a * a) call 5 ; otherStuff

??

i'm skimming docs now.  it looks very interesting.  the only quirk
IsForNonNativeEnglishSpeakers ;-(

cheers.

-a
-- 
in order to be effective truth must penetrate like an arrow - and that is
likely to hurt. -- wei wu wei