[Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

pharo at googlecode.com pharo at googlecode.com
Mon Jan 3 06:38:03 EST 2011


Comment #9 on issue 3436 by step... at stack.nl: #copyFrom: is broken
http://code.google.com/p/pharo/issues/detail?id=3436

Then the real question  is: why do we have copyFrom:to:?
To be in collection protocol style, that could be from:to:.
It is not reliably derivable from the protocol name if you get a copy or  
mutate the original.





More information about the Pharo-dev mailing list