Re: {CVS ci] alternate object initializer calling scheme

2004-04-16 Thread Leopold Toetsch
Chromatic <[EMAIL PROTECTED]> wrote: > What needs to be done before making it the default? I'm anxious to > remove CALL__BUILD=1 from my parrot alias. Waiting for famous final words by our big cheese... leo

Re: {CVS ci] alternate object initializer calling scheme

2004-04-15 Thread chromatic
On Sat, 2004-04-10 at 01:49, Leopold Toetsch wrote: > >> This initializer is available as first param in the init method. > > I'm happy with this. > Good. What needs to be done before making it the default? I'm anxious to remove CALL__BUILD=1 from my parrot alias. > We don't have it yet. We cou

Re: {CVS ci] alternate object initializer calling scheme

2004-04-10 Thread Leopold Toetsch
Chromatic <[EMAIL PROTECTED]> wrote: > On Fri, 2004-04-09 at 04:56, Leopold Toetsch wrote: >> >> new Pobj, Iclass, PInit >> >> This initializer is available as first param in the init method. > I'm happy with this. Good. > ... A similar scheme will work nicely for > deconstructors. > (I loo

Re: {CVS ci] alternate object initializer calling scheme

2004-04-09 Thread chromatic
On Fri, 2004-04-09 at 04:56, Leopold Toetsch wrote: > I've put in the new scheme for initializer calls. > To test it, set the environment variable "CALL__BUILD" to some value. > > Sample code to set an initializer to "_new" > > new P10, .PerlString > set P10, "_new" > newclass P1,

{CVS ci] alternate object initializer calling scheme

2004-04-09 Thread Leopold Toetsch
I've put in the new scheme for initializer calls. To test it, set the environment variable "CALL__BUILD" to some value. Sample code to set an initializer to "_new" new P10, .PerlString set P10, "_new" newclass P1, "Foo" setprop P1, "BUILD", P10 The BUILD initializer is called for a