Re: Library loading and initialization sequence

2003-10-11 Thread Leopold Toetsch
Nicholas Clark <[EMAIL PROTECTED]> wrote: > On Fri, Oct 10, 2003 at 05:44:05PM +0200, Leopold Toetsch wrote: >> >> - the opcode numbers are assigned dynamically: > What happens if the opcode library is rebuilt with more ops after the > bytecode using it is compiled and frozen to disk? Its as inva

Re: Library loading and initialization sequence

2003-10-10 Thread Nicholas Clark
On Fri, Oct 10, 2003 at 05:44:05PM +0200, Leopold Toetsch wrote: > Dan Sugalski <[EMAIL PROTECTED]> wrote: > > On Fri, 10 Oct 2003, Leopold Toetsch wrote: > > >> - the opcode numbers are assigned dynamically: > >> When you load an oplib containing 100 ops, they get op numbers > >> e.g. 1206 ..

Re: Library loading and initialization sequence

2003-10-10 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > On Fri, 10 Oct 2003, Leopold Toetsch wrote: >> - the opcode numbers are assigned dynamically: >> When you load an oplib containing 100 ops, they get op numbers >> e.g. 1206 ... 1305. Next oplib starts at 1306 ... >> - on load all runcores are notified

Re: Library loading and initialization sequence

2003-10-10 Thread Dan Sugalski
On Fri, 10 Oct 2003, Leopold Toetsch wrote: > - the opcode numbers are assigned dynamically: > When you load an oplib containing 100 ops, they get op numbers > e.g. 1206 ... 1305. Next oplib starts at 1306 ... > - on load all runcores are notified to use the new oplib function > or address t

Re: Library loading and initialization sequence

2003-10-10 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > Right now there's a load_pmc op, which goes along with the load_opcode_lib > and loadlib ops. I'd like to unify that I'll start the opcode load thingy, based on my experimental code I has posted here mid-March. The basics are: - assembler and runtime mus

Re: Library loading and initialization sequence

2003-09-30 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > Next, the sequence of loading. > Right now there's a load_pmc op Gone. > and loadlib ops. I'd like to unify that Done. > When we load a library, the bytecode should probe for and, if it exists, > call Parrot_lib_load_%s, where %s is the library name.

Re: Library loading and initialization sequence

2003-09-29 Thread Dan Sugalski
On Mon, 29 Sep 2003, Dan Sugalski wrote: > Firstly, we're adding a new method INIT to the .pmc file. *If* it exists This, by the by, corresponds to the _init method in loading, and is called on each thread instantiation. We're also going to add a LOAD method, again optional, which will be called

Library loading and initialization sequence

2003-09-29 Thread Dan Sugalski
Since I'm working on this now, I figure I'd best give everyone a heads-up as to what I'm doing. Right now, I'm working on loading PMCs, both dynamic and static, and the initialization sequence they go through. I know we've got some of this down already, but adding in MMD and the need to initialize