Generate Parrot::OpcodeTable?

2001-09-18 Thread Gregor N. Purdy

All --

It seems to me that we should have a Parrot::OpcodeTable module that
is auto-generated rather than having the assembler and disassembler
read in the opcode_table file itself. We can install OpcodeTable.pm
just like any other module when folks install the assembler and
disassembler.

We still need the current Opcode.pm, but I wonder if it should be
in Parrot::Private::OpcodeTable or Parrot::BuildUtil::OpcodeTable
or something...


Regards,

-- Gregor
 _ 
/ perl -e 'srand(-2091643526); print chr rand 90 for (0..4)'  \

   Gregor N. Purdy  [EMAIL PROTECTED]
   Focus Research, Inc.http://www.focusresearch.com/
   8080 Beckett Center Drive #203   513-860-3570 vox
   West Chester, OH 45069   513-860-3579 fax
\_/




Re: Generate Parrot::OpcodeTable?

2001-09-18 Thread Simon Cozens

On Tue, Sep 18, 2001 at 04:15:45PM -0400, Gregor N. Purdy wrote:
 It seems to me that we should have a Parrot::OpcodeTable module that
 is auto-generated rather than having the assembler and disassembler
 read in the opcode_table file itself.

Yes; I can't remember why I thought this was a good idea, but it is.

Oh yes, it can be found in @INC, whereas assemble and disassemble
currently look for opcode_table in the current directory; this makes
it hard for people to write Parrot code outside of parrot/.

Simon
-- 
`And when you've been *plonk*ed by Simon C., you've been *plonked*
by someone who knows when, and why, and how.' - Mike Andrews, asr