On Sat, 21 Aug 2004 19:36:43 -0400 Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 6:44 PM +0200 8/21/04, Mattia Barbon wrote: > > Hello, > >I think extenders should have access to at least some of the > >flags in PObj_enum. Should we have a different function for > >each flag (say: Parrot_PObj_set_custom_mark(INTERP, PMC, value), > >Parrot_PObj_set_is_class(INTERP, PMC, value) or a single > >Parrot_PObj_set_flag(INTERP, PMC, flag, value) where flag > >is an enumerated value declared in extend.h, NOT the values of > >PObj_enum. > > Nope. Flags are for internal PMC use or engine use, not for > extenders, at least not for now. > > > Extenders also need Parrot_PObj_mark(INTERP, PMC). > > Nope. That's for internal use, either by the DOD or the the PMC class > functions. > > We should get the APIs better delineated, though, with the reasons > for this stuff being where it is. I am writing Perl5PVAV PMC. I need to mark its contents. I need the custom mark flag (or a way to tell the GC to call my custom mark method) and I will need a custom destroy for other PMC types. How do I achieve this? Regards Mattia
