On 12/30/06, M. Edward (Ed) Borasky <znmeb / cesmail.net> wrote:
> Wilson Bilkovich wrote:
> > Exactly. I wasn't going to chime in until someone broke the ice.. but
> > the Parrot team basically can't explain the design rationale. It's
> > even featured in a solid book about virtual machines, along with a
> > narrative that amounts to: "Uhh.. umm.. this is certainly an
> > interesting way to go about it."
> What's the name of the book? The only book I've seen is the O'Reilly
> book on Perl 6 and Parrot. That pretty much ignores Python, PHP and
> Ruby, of course. :)

http://www.amazon.com/Virtual-Machines-Iain-D-Craig/dp/1852339691/
Badly needed an additional editor to fix typos and other mistakes, but
is a very interesting book none the less.

> > From Ruby's perspective, it also has the odd feature of having
> > separate registers for Strings and for Objects. *shudder*
> IIRC they also have separate integer and float registers, just like many
> real machines. *That* -- a separate floating point stack vs. a single
> "parameter stack" -- was a big debate point in the discussions leading
> up to the ANS Forth standard, and in the end, the standard had to be
> written so either could be implemented.

> > Anyone who wants to hack on a Ruby VM will receive a warm welcome in
> > the arms of Rubinius. :)
> Well ... to repeat myself:
> 1. Adding programmers to a late project makes it later.
> 2. I have my own languishing half-person projects to look after.
> 3. I really really suck at C programming -- I can just barely read C.

Well, I meant it as a general invite. :)

> P.P.S: What exactly *is* the status of Perl 6? :)

I will let this link stand on its own, with.. no.. further.. commentary:
http://dev.perl.org/perl6/doc/design/syn/S05.html