On Saturday 02 February 2008 22:41:03 chromatic wrote:
> Second, we need a way to know the proper initialization order of PMC
> vtables such that we handle all parents before all children. Making this
> work for core PMCs is fairly easy. Making it work for dynpmcs is a little
> more difficult, b
libparrot exports over 16,000 symbols. Half of those are the vtable functions
in our PMCs.
For now, they get exported because of the way we build the vtables when we
initialize PMCs. Look in src/pmc/class.c in a built Parrot source tree for
now. Parrot_Class_class_init() creates the Class PM