On Mon, Nov 26, 2007 at 11:01:56AM +0200, Allison Randal wrote:
> Patrick R. Michaud wrote:
> >
> >How about 'copy'?
> >
>
> I like 'copy', and the idea that it always consistently creates a copy
> of the object it's passed. We'll probably get some confusion about the
> distinction between 'copy
Klaas-Jan Stol wrote:
On Nov 26, 2007 10:01 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
I like 'copy', and the idea that it always consistently creates a copy
of the object it's passed. We'll probably get some confusion about the
distinction between 'copy' and 'clone'. Saying "clone creates a
On Nov 26, 2007 10:01 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Patrick R. Michaud wrote:
> >
> > How about 'copy'?
> >
> > Of the above suggestions, 'morph' seems most accurate, and 'new'
> > seems all wrong to me. Of course, if we do it as a variant of
> > 'clone' or 'morph' we might run i
Patrick R. Michaud wrote:
How about 'copy'?
Of the above suggestions, 'morph' seems most accurate, and 'new'
seems all wrong to me. Of course, if we do it as a variant of
'clone' or 'morph' we might run into trouble when the source
operand is itself a class (do we want to copy the class or do
On Sun, Nov 25, 2007 at 01:56:51PM +0200, Allison Randal wrote:
> Patrick R. Michaud wrote:
> >I just want to add a reminder here that the whole reason PCT,
> >PAST-pm, and Tcl use morph in the first place is because Parrot
> >doesn't provide a usable "replace pmc with clone" opcode, and
> >using m
Patrick R. Michaud wrote:
I just want to add a reminder here that the whole reason PCT,
PAST-pm, and Tcl use morph in the first place is because Parrot
doesn't provide a usable "replace pmc with clone" opcode, and
using morph+assign is a workaround.
In other words, if a "replace pmc" opcode exis
I just want to add a reminder here that the whole reason PCT,
PAST-pm, and Tcl use morph in the first place is because Parrot
doesn't provide a usable "replace pmc with clone" opcode, and
using morph+assign is a workaround.
In other words, if a "replace pmc" opcode exists, then morph
suddenly bec
A better fix is to update pmc_reuse in src/pmc.c so it correctly handles
morphing to object types. See pmc_new in the same file for an example of
instantiating an object from a type ID (by looking up the class object).
As Jonathan started to ponder in his message "Morphing to high level
classes