I know there was some talk about this extra "address" parameter recently, but i'm not sure what the upshot of it is. Right now, tcc is complaining loudly because the init functions for parrotsub and parrotcoroutine don't match the init_method_t type in the _vtable structure.
What's the deal here? --Josh array.c:void Parrot_Array_init (struct Parrot_Interp *interpreter, PMC* pmc) default.c:void Parrot_default_init (struct Parrot_Interp *interpreter, PMC* pmc) default.c:void Parrot_default_init_pmc (struct Parrot_Interp *interpreter, PMC* pmc, PMC* value) intqueue.c:void Parrot_IntQueue_init (struct Parrot_Interp *interpreter, PMC* pmc) parrotcoroutine.c:void Parrot_ParrotCoroutine_init (struct Parrot_Interp *interpreter, PMC* pmc, INTVAL address) parrotpointer.c:void Parrot_ParrotPointer_init (struct Parrot_Interp *interpreter, PMC* pmc) parrotsub.c:void Parrot_ParrotSub_init (struct Parrot_Interp *interpreter, PMC* pmc, INTVAL address) perlarray.c:void Parrot_PerlArray_init (struct Parrot_Interp *interpreter, PMC* pmc) perlhash.c:void Parrot_PerlHash_init (struct Parrot_Interp *interpreter, PMC* pmc) perlint.c:void Parrot_PerlInt_init (struct Parrot_Interp *interpreter, PMC* pmc) perlnum.c:void Parrot_PerlNum_init (struct Parrot_Interp *interpreter, PMC* pmc) perlstring.c:void Parrot_PerlString_init (struct Parrot_Interp *interpreter, PMC* pmc) perlundef.c:void Parrot_PerlUndef_init (struct Parrot_Interp *interpreter, PMC* pmc) -- Josh Wilmes ([EMAIL PROTECTED]) | http://www.hitchhiker.org
