Allison Randal <[EMAIL PROTECTED]> wrote:
Klaas-Jan Stol wrote:
> In a way, when copying it, it does make sense all attributes are copied as
> well.... (it seems "clean")

Indeed. Let's categorize this bug as a feature.

Are you sure? It seems like this bug/feature will go away when pdd15
is implemented. At that point, setting a Sub in a namespace will no
longer modify the methods or vtable functions of a class.

As a feature, this could do a world of hurt. I'm not sure how much
sense it makes to copy a method from one class to another, but I'd
hate to see vtable functions trampled over. Imagine this: you copy a
method from one class to another. Unknown to you, that method was also
acting as the get_string vtable function. By copying the method, you
also replaced that vtable function in the destination class. Now when
your language tries to stringify an object using the get_string vtable
function, it gets something other than the string it should have
gotten.

--
Matt Diephouse
http://matt.diephouse.com

Reply via email to