Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hi again,
> I just found another problem related to bytecode switching:
> *** switching to BYTECODE_library/Data/Dumper/Base.imc
> PC=-4501; OP=
Thanks, fixed.
> jens
leo
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Well done, looks really better!
Actually while digging hours through traces of EBNF, I wasn't really
happy with the output, so I changed it ;)
> I noticed that DOD runs are disturbing the output:
>495 null S31 -
>497 set P5, P6 - P5=#
Jens Rieks <[EMAIL PROTECTED]> wrote:
> I noticed that DOD runs are disturbing the output:
I haven't removed it, now it looks like:
2193 setprop P16, ".name", P17- P16=Sub= ...
DOD
2197 branch 14
Here the C did cause a DOD run.
leo
Hi again,
I just found another problem related to bytecode switching:
*** switching to BYTECODE_library/Data/Dumper/Base.imc
PC=-4501; OP=
The first shown OP after a switch is always wrong.
jens
Hi,
On Tuesday 09 March 2004 15:55, Leopold Toetsch wrote:
> I've rearranged the output of parrot -t a bit. It should be more
> readable now e.g.:
>
> 0 set P16, P1 - P16=NULL, P1=NULL
> 3 set P17, P5 - P17=SArray=PMC(0x40304908),
> P5=SArray=PMC(0x40304908)
> 6 set I16
I've rearranged the output of parrot -t a bit. It should be more
readable now e.g.:
0 set P16, P1 - P16=NULL, P1=NULL
3 set P17, P5 - P17=SArray=PMC(0x40304908),
P5=SArray=PMC(0x40304908)
6 set I16, P17 - , P17=SArray=PMC(0x40304908)
9 newsub P16, 46, 5715 -
