At 1:29 PM -0500 12/31/02, David Robins wrote:
If the op defines the destination as getting a brand-new PMC, then just stuff the pointer to it in the destination and let the GC pick up the original if necessary.Maybe I missed it in the original thread, but what was the resolution on how to create and return a new PMC in PMC ops that take a "PMC* dest" param? Should I submit my pmc_placement_new() (also in that thread) as a patch? (morph isn't sufficient because I don't want to coerce the destination into anything, I want to clobber it, so cycles are wasted if e.g. dest is presently (say) a number, and I morph it into a string, which does some sort of sprintf call, and then I set the string to an arbitrary new value).
If the op defines that it will assign a value in the destination, then call the set_value vtable method and let the destination PMC deal with the incoming value as it needs to.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
