Remove clone_pmc VTABLE slot

[cotto]

The clone_pmc VTABLE function is implemented only in the Class PMC and used only in the p_p_px variant of the clone op. The extent of its purpose is to create a clone of the Class, then initialize it with the contents of a PMC, which is assumed to be hash-like. Given this VTABLE slot's limited use, I'd like to deprecate it.

[bacek]

+1

[jkeenan]

cotto,

Are we actually going to deprecate it? If so, what is its replacement? Can we file a deprecation notice?

Thank you very much.

kid51

[pmichaud]

-2. Removing the clone_pmc vtable would seem to assume that all (HLL) PMCs types would have identical clone functionality, which I think to be unlikely in the long run.

(Just because Parrot's PMC types don't make much use of this vtable doesn't mean it won't be needed for more complex HLL types.)

Pm

[jkeenan]

Replying to pmichaud:

-2. Removing the clone_pmc vtable would seem to assume that all (HLL) PMCs types would have identical clone functionality, which I think to be unlikely in the long run.

cotto:

Do you accept pmichaud's reason for opposing this change?

If so, we can close this ticket.

Thank you very much.

kid51

[cotto]

Replying to jkeenan:

Replying to pmichaud:

-2. Removing the clone_pmc vtable would seem to assume that all (HLL) PMCs types would have identical clone functionality, which I think to be unlikely in the long run.

cotto: Do you accept pmichaud's reason for opposing this change? If so, we can close this ticket. Thank you very much. kid51

Yup. I'll close this.