Re: PMC assignment stuff

2002-08-27 Thread Sean O'Rourke
On Tue, 27 Aug 2002, Jason Gloudon wrote: > Dan Sugalski wrote: > > This includes all forms of assignment, not just the ASSIGN op kind. > > When we do an ADD Px, Py, Pz, we're calling Px's set_pmc vtable entry > > with a PMC that represents the addition of Y and Z. Whether X changes > > its type i

Re: PMC assignment stuff

2002-08-27 Thread Jason Gloudon
Dan Sugalski wrote: > First, for simple X = Y cases, we need a new assignment opcode. We > have SET to copy pointers, CLONE to make full clones, but we don't > have a method to stuff a value from one PMC to another. > So, what we need to do is add ASSIGN Px, Py, which takes Px and calls > se

Re: PMC assignment stuff

2002-08-08 Thread Dan Sugalski
At 10:13 AM +0100 8/8/02, Nicholas Clark wrote: >On Thu, Aug 08, 2002 at 10:21:54AM +0200, Peter Gibbs wrote: > > Should a PerlScalar have its own vtable which acts as appropriate >> depending on current content, or should it switch vtables as the >> content changes? If the latter, do we have s