At 6:48 PM +0100 2/20/04, Leopold Toetsch wrote:
Dan Sugalski wrote:
At 9:42 AM +0100 2/20/04, Leopold Toetsch wrote:
Started that now:
The syntax (proposed and current) is for PASM:
.pcc_sub @MAIN _main:
and for PIR:
.sub _main prototyped, @MAIN, @IMMEDIATE, @LOAD, @POSTCOMP
Let's skip
Dan Sugalski wrote:
At 9:42 AM +0100 2/20/04, Leopold Toetsch wrote:
Started that now:
The syntax (proposed and current) is for PASM:
.pcc_sub @MAIN _main:
and for PIR:
.sub _main prototyped, @MAIN, @IMMEDIATE, @LOAD, @POSTCOMP
Let's skip the commas, mandate the properties come later, l
At 9:42 AM +0100 2/20/04, Leopold Toetsch wrote:
Started that now:
The syntax (proposed and current) is for PASM:
.pcc_sub @MAIN _main:
and for PIR:
.sub _main prototyped, @MAIN, @IMMEDIATE, @LOAD, @POSTCOMP
Let's skip the commas, mandate the properties come later, lower-case
'em, and toss
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> MAIN subs, of which there should be only one, is the sub that parrot
> executes when it's handed a bytecode file to run. If I do:
Done.
> IMMEDIATE subs are executed, with no parameters, as soon as they're
> done compiling. They're definitely compile-tim
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> We've got the need to have subs that get executed when a code segment
> is loaded,
That part is working now for loaded assembly and byte code.
.pcc_sub @LOAD _the_init_code: # PASM
.sub _the_init_code @LOAD, prototyped # PIR
s. t/pmc/sub.t for
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Okay, since folks are diving into IMCC (assuming we can keep a fight
> from breaking out) it's time to address bytecode loading.
> We've got the need to have subs that get executed when a code segment
> is loaded, a need to have a 'main' sub that gets exec
