|parrotcode: Parrot Object|
|Contents | PMCs|
src/pmc/parrotobject.pmc - Parrot Object
A Parrot Object is reasonably simple. Its data pointer points to an array with the attributes of the object in it. The int cache value holds the attribute count of this instance.
The object is actually constructed by the instantiation code in src/objects.c, at least for right now.
newon the registered class PMC and not the ParrotObject itself.
init()method gets replaced by
destroymethod is of course wrong. The finalization code could resurrect the object, by e.g. storing it into some structure. But as destruction is also done in this step, the stored object is unusable (in best case) or even recycled to a new PMC. All access to such a zombie would be really interesting.
- create a tobe_finalized list in the GC - don't destroy these objects immediately - create a dedicated finalize vtable - run the finalization code after GC has finished - run all finalizers in MRO order - postpone destruction to the next GC cycle
PMC *find_method(STRING *name)
PMC *get_attr(INTVAL idx)
PMC *get_attr_str(STRING *name)
void set_attr(INTVAL idx, PMC *val)
void set_attr_str(STRING *name, PMC *val)
INTVAL get_integer_keyed_int(INTVAL key)
FLOATVAL get_number_keyed_int(INTVAL key)
STRING *get_string_keyed_int(INTVAL key)
PMC *get_pmc_keyed_int(INTVAL key)
void set_integer_keyed_int(INTVAL key, INTVAL value)
void set_number_keyed_int(INTVAL key, FLOATVAL value)
void set_string_keyed_int(INTVAL key, STRING *value)
void set_pmc_keyed_int(INTVAL key, PMC *value)
void delete_keyed_int(INTVAL key)
INTVAL defined_keyed_int(INTVAL key)
INTVAL exists_keyed_int(INTVAL key)
deleg_pmcmethod, else it's just SUPER aka the default implementation.
void visit(visit_info *info)
*infois the visit info, (see include/parrot/pmc_freeze.h).
void freeze(visit_info *info)
void thaw(visit_info *info)
void thawfinish(visit_info *info)