RE: Tasks for the interested

2002-07-10 Thread John Porter
Dan Sugalski wrote: > These 'add-on' bytecode interpreters don't get any special > consideration in the core. That means they *can* have: > > *) A custom bytecode loader to translate their bytecode format >to ours, or something we can use > *) As many custom PMC classes as they want > *) D

RE: Tasks for the interested

2002-07-10 Thread Dan Sugalski
At 2:30 PM -0700 7/9/02, John Porter wrote: >Garrett Goebel wrote: >> John Porter wrote: >> > Not to beat on Dan (or anyone else), but for the sake of those >> [...] >> >> Please don't beat on Dan... ;) > >I'm not! Nope, he isn't. Warnings and concerns based on technical merits and past expe

RE: Tasks for the interested

2002-07-09 Thread John Porter
Garrett Goebel wrote: > John Porter wrote: > > Not to beat on Dan (or anyone else), but for the sake of those > [...] > > Please don't beat on Dan... ;) I'm not! > Parrot isn't Perl. I.e., your Perl-vision blinders are on a tad > tight. It's the first general purpose vm for dynamic languages.

RE: Tasks for the interested

2002-07-09 Thread Garrett Goebel
From: John Porter [mailto:[EMAIL PROTECTED]] > Dan Sugalski wrote: > > John Porter wrote: > > >I assume (but I'm open to correction) that it is *not* to simulate > > >the vm of other language environments, so as to execute faithfully > > >bytecode produced in those environments. (That is, taking

Re: Tasks for the interested

2002-07-09 Thread John Porter
Dan Sugalski wrote: > John Porter wrote: > >I assume (but I'm open to correction) that it is *not* to simulate > >the vm of other language environments, so as to execute faithfully > >bytecode produced in those environments. (That is, taking object > >code from a python compiler (e.g.) and execu

Re: Tasks for the interested

2002-07-09 Thread John Porter
Dan Sugalski wrote: > John Porter wrote: > > I assume (but I'm open to correction) that it is *not* to simulate > > the vm of other language environments, so as to execute faithfully > > bytecode produced in those environments. (That is, taking object > > code from a python compiler (e.g.) and e

Re: Tasks for the interested

2002-07-09 Thread Dan Sugalski
At 9:45 PM -0700 7/8/02, John Porter wrote: > > Dan wrote: >> > 1) Dig through the perl source and find out all the opcodes. >> > (pp.c and friends) Document the opcodes and what they do. >> > >> > 2) The same as #1, only for Python >> > . . . >> > >> > Once we get these, the next task is

Re: Tasks for the interested

2002-07-08 Thread John Porter
> Dan wrote: > > 1) Dig through the perl source and find out all the opcodes. > > (pp.c and friends) Document the opcodes and what they do. > > > > 2) The same as #1, only for Python > > . . . > > > > Once we get these, the next task is to write an opcode library > > for them... I want to unde

The Tcl VM (was: Re: Tasks for the interested)

2002-07-05 Thread John Porter
Dan wrote: > Okay, here are some tasks for the interested. They're all related > (I expect you'll see the pattern), but independent anyway. > > 1) Dig through the perl source and find out all the opcodes. > (pp.c and friends) Document the opcodes and what they do. > > 2) The same as #1, only fo

Re: Tasks for the interested

2002-07-01 Thread John Porter
(I don't have the original msg in my mbox, so I'm jumping in here...) The following is from the Tcl bytecode compiler [1] FAQ: Why doesn't Tcl use the Java bytecodes? I [2] had originally hoped to use Java bytecodes because they have a mature design and because Java is widely available. I cho

Re: Tasks for the interested

2002-06-26 Thread Joe McMahon
There's a draft update of the Z-machine spec to 1.1: http://www.jczorkmid.net/~jpenney/ZSpec11-draft6.txt It's not final, but it does clarify some vague stuff in the 1.0 spec. --- Joe M.

Re: Tasks for the interested

2002-06-23 Thread Richard J Cox
On Tuesday, June 18, 2002, 9:33:55 PM, you (mailto:[EMAIL PROTECTED]) wrote: > Okay, here are some tasks for the interested. They're all related (I > expect you'll see the pattern), but independent anyway. [...] > 5) .NET (same as #4, a link to a good reference is fine) Couldn't find any specifi

Re: Tasks for the interested

2002-06-19 Thread Joe Avis
> 2) The same as #1, only for Python Python Byte Code Instructions http://www.python.org/doc/current/lib/bytecodes.html __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

Re: Fwd: Re: Tasks for the interested

2002-06-18 Thread Josh Wilmes
Oh man. Now i'm doomed. I guess i'll start playing tonight then ;-) --Josh At 17:20 on 06/18/2002 EDT, Dan Sugalski <[EMAIL PROTECTED]> wrote: > At 5:10 PM -0400 6/18/02, Josh Wilmes wrote: > >So now who's going to implement it? (must..contain..urge..) > > You think *you* have to contain t

Re: Fwd: Re: Tasks for the interested

2002-06-18 Thread Dan Sugalski
At 5:10 PM -0400 6/18/02, Josh Wilmes wrote: >So now who's going to implement it? (must..contain..urge..) You think *you* have to contain the urge... :) Seriously, this is a good thing to tackle. Not only does it involve custom opcode libraries, but it also requires packfile loading with tran

Re: Fwd: Re: Tasks for the interested

2002-06-18 Thread Josh Wilmes
So now who's going to implement it? (must..contain..urge..) --Josh At 17:03 on 06/18/2002 EDT, Dan Sugalski <[EMAIL PROTECTED]> wrote: > >> 6) Infocom's z-machine > > > >http://www.gnelson.demon.co.uk/zspec/sect14.html > > Well, that's one...

Fwd: Re: Tasks for the interested

2002-06-18 Thread Dan Sugalski
>Date: Tue, 18 Jun 2002 15:55:51 -0500 >From: Joe Mason >To: Dan Sugalski <[EMAIL PROTECTED]> >Subject: Re: Tasks for the interested > > >On Tue, Jun 18, 2002 at 04:33:55PM -0400, Dan Sugalski wrote: >> Okay, here are some tasks for the interested. They'r

Re: Tasks for the interested

2002-06-18 Thread Rafael Garcia-Suarez
Dan Sugalski wrote in perl.perl6.internals : > Okay, here are some tasks for the interested. They're all related (I > expect you'll see the pattern), but independent anyway. > > 1) Dig through the perl source and find out all the opcodes. (pp.c > and friends) Document the opcodes and what they