At 10:29 AM 12/17/2001 -0500, Jason Gloudon wrote:
>On Mon, Dec 17, 2001 at 09:43:28AM -0500, Dan Sugalski wrote:
>
> > >Can you clarify what you mean by "deep copy" at least to the pointer
> level ?
> > >
> > >set P0, P1
> > >
> > >should invoke P0's "assignment" vtable function (does anyone know if it
> > >already
> > >exists under a different name ?). For the existing PMC's the appropriate
> > >assignment vtable calls P1's clone function with P0 as the destination.
> >
> > The entry's set_xxx, where xxx is integer, number, string, or value.
> > However, that's not appropriate here--set P0, P1 should just copy the
> > pointer from P1 to P0. Actually stuffing the value of the PMC pointed
> to by
> > P1 into the one pointed to in P0 should be done with a different op.
>
>Ok, so set creates an alias. The string set opcode should also create an
>alias for consistency, no ?
It does. Or it did last I checked...
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
