Re: PDB [Was: Re: Calling conventions, IMC]

2004-01-20 Thread Leopold Toetsch
Will Coleda <[EMAIL PROTECTED]> wrote: > bash-2.05a$ make exit > ../../../parrot ../tcl.pbc exit.tcl > branch_cs: illegal resume offsetmake: *** [exit] Error 1 This is very likely an undefined label. imcc tries to find that at runtime (it could have come out from eval) and fails. > So, I'm tryin

Re: Calling conventions, IMC

2004-01-19 Thread Melvin Smith
At 03:16 PM 1/19/2004 -0700, Luke Palmer wrote: Will Coleda writes: > I didn't expect the code to be very usable, merely compilable. =-) > > If I want to call myself from myself, how do I do that then? > > For anything else, I do: > > .local Sub foo_sub > newsub foo_sub, .Sub, __foo > > .pcc_

PDB [Was: Re: Calling conventions, IMC]

2004-01-19 Thread Will Coleda
Ok. I've converted my code over to do this[1]. I am now able to compile tcl.imc, but all my code fails to run, ala: bash-2.05a$ make exit ../../../parrot ../tcl.pbc exit.tcl branch_cs: illegal resume offsetmake: *** [exit] Error 1 So, I'm trying to track down where this badness is happening: bas

Re: Calling conventions, IMC

2004-01-19 Thread Luke Palmer
Will Coleda writes: > I didn't expect the code to be very usable, merely compilable. =-) > > If I want to call myself from myself, how do I do that then? > > For anything else, I do: > > .local Sub foo_sub > newsub foo_sub, .Sub, __foo > > .pcc_begin prototyped > .arg $S1 > .pcc_call

Re: Calling conventions, IMC

2004-01-19 Thread Will Coleda
I didn't expect the code to be very usable, merely compilable. =-) If I want to call myself from myself, how do I do that then? For anything else, I do: .local Sub foo_sub newsub foo_sub, .Sub, __foo .pcc_begin prototyped .arg $S1 .pcc_call foo_sub tellmeagainwhyineedthislabel: .re

Re: Calling conventions, IMC

2004-01-19 Thread Leopold Toetsch
Will Coleda <[EMAIL PROTECTED]> wrote: > (has a .end) Yup. > Managed to shrink it down to: > .pcc_sub __interpret prototyped >newsub P1, .Sub, __interpret >.pcc_begin_return >.return 0 >.pcc_end_return > .end Two problems: You are overriding the already existing Sub with that nam

Re: Calling conventions, IMC

2004-01-19 Thread Leopold Toetsch
Will Coleda <[EMAIL PROTECTED]> wrote: > 1 .pcc_sub __interpret prototyped > 2# An array of commands to interpret. > 3.param PerlArray orig_commands Please note that between .pcc_sub and .param nothing is allowed, not even a comment. leo

Re: Calling conventions, IMC

2004-01-19 Thread Will Coleda
(has a .end) Yup. Managed to shrink it down to: .pcc_sub __interpret prototyped newsub P1, .Sub, __interpret .pcc_begin_return .return 0 .pcc_end_return .end It appears that creating a Sub that refers to the sub you're currently in is the trigger. If I change the sub name to "foo", it co

Re: Calling conventions, IMC

2004-01-19 Thread Dan Sugalski
At 12:55 PM -0500 1/19/04, Will Coleda wrote: Though the file contains: 1 .pcc_sub __interpret prototyped 2# An array of commands to interpret. 3.param PerlArray orig_commands ... 392 DONE: 393.debug("final retval is '") 394.debug(retval) 395.debug(

Calling conventions, IMC

2004-01-19 Thread Will Coleda
(Thanks for the quick response on the last email) I have another problem. I have a 405-line file (containing a single .pcc_sub) that is being included from my main .imc. I get: error:imcc:pcc_return not inside pcc subroutine in file 'lib/interpret.imc' line 397 included from 'tcl.imc'