Dan Sugalski: # Details of strings, PMCs, and vtables shouldn't be exposed to people # writing extensions. Strings and PMCs should be opaque types, and # vtables shouldn't be exposed at all, to hide the details of the # implementation. Structure should be completely unexposed. # # Only the core and PMC class authors should see the vtables, and only # people actually writing them in C. (PMC classes written in # perl/python/ruby/whatever should see the interface their particular # HLL exposes) # # Probably a good first step for an extending and embedding PDD, if we # want just a single one, is to define what's visible where, and what's # black magic in other places, just so we can keep this stuff straight.
*Sigh*. Okay, then we'll need a different interface to call vtable methods on PMCs from outside. We can't just say "no, all you can do is toss these things around, you can't do anything with them". Any suggestions? --Brent Dax [EMAIL PROTECTED] Parrot Configure pumpking, regex hacker, embedding coder, and all-around good guy Check out the Parrot FAQ: http://www.panix.com/~ziggy/parrot.html (no, it's not mine) <obra> mmmm. hawt sysadmin chx0rs <lathos> This is sad. I know of *a* hawt sysamin chx0r. <obra> I know more than a few. <lathos> obra: There are two? Are you sure it's not the same one?
