comment on

It's a good bet that there's never been anything like Parrot before.

I'd take that bet.

Back in the eighties I did a lot of work with Poplog, a programming environment that had Lisp, Prolog, ML, Pop-11 and a few other languages all compiling down to a single virtual machine, which was in turn incrementally compiled down to raw machine code. Ran on VMS and most Unix platforms.

The VM was stack based, rather than register based as Parrot is, but there certainly isn't anything new about a cross-platform VM that was built to be the target for many different languages.

Parrot's just following in the grand Perl tradition of stealing the best ideas and implementing them well :-)

(If anybody is interested Poplog is still around. It's open source, runs on VMS, Windows9X/NT and a variety of versions of the Unix operating system (including Linux, AIX, Ultrix, SunOS, HP-UX and Dynix), on a variety of processors including VAX, M680x0, SPARC, 80x86, and MIPS. See poplog.org for info.)

In reply to Re^2: Analysis, Design effort of Perl 6 by adrianh
in thread Analysis, Design effort of Perl 6 by pbeckingham

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks