Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-02 Thread Stéphane Ducasse
...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Lukas Renggli [reng...@gmail.com] Sent: Saturday, January 01, 2011 2:06 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: Quite some software (Seaside, Mondrian

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-02 Thread Lukas Renggli
On 2 January 2011 10:37, Stéphane Ducasse stephane.duca...@inria.fr wrote: On Jan 2, 2011, at 1:33 AM, csra...@bol.com.br wrote: I would like to add to the tally. Changing ObjectcopyFrom: to ObjectcopyStateFrom: makes for me a lot more sense that changing (in fact by the creation of)

[Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Sebastian Sastre
('if this isn''t broken' copyFrom: 15) ~= 'broken' ifTrue:['this is screwed'] ifFalse:['this is intuitive'] Evaluate that in any Pharo workspace and it will show you. Reported here. Status? invalid Came on guys. Really? I ask because, if so, situation goes like this: A. we think again and

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Igor Stasenko
On 1 January 2011 18:15, Sebastian Sastre s...@sebastianconcept.com wrote: ('if this isn''t broken' copyFrom:  15) ~= 'broken' ifTrue:['this is screwed'] ifFalse:['this is intuitive'] my first thought about it was that it should answer own copy , starting from 15th element :) Evaluate that

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Stéphane Ducasse
HI sebastian If I remember correctly you are not the only one bitten by it :) so we should do something ObjectcopyFrom: anotherObject Copy to myself all instance variables I have in common with anotherObject. This is dangerous because it ignores an object's control over its own inst

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Adrian Lienhard
Yes, this method name is unfortunate... I think we should just rename the method and tag copyFrom: as deprecated. And some versions later we'll implement copyFrom: as we think is appropriate. Cheers, Adrian BTW Sebastian, I think your energy would be better invested into producing a changeset

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Schwab,Wilhelm K
...@inria.fr] Sent: Saturday, January 01, 2011 1:29 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: HI sebastian If I remember correctly you are not the only one bitten by it :) so we should do something ObjectcopyFrom: anotherObject Copy

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Lukas Renggli
[stephane.duca...@inria.fr] Sent: Saturday, January 01, 2011 1:29 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: HI sebastian If I remember correctly you are not the only one bitten by it :) so we should do something

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Peter Hugosson-Miller
Of Stéphane Ducasse [stephane.duca...@inria.fr] Sent: Saturday, January 01, 2011 1:29 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: HI sebastian If I remember correctly you are not the only one bitten by it :) so we should do something

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Schwab,Wilhelm K
...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Peter Hugosson-Miller [oldmanl...@gmail.com] Sent: Saturday, January 01, 2011 2:30 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: Hehehe. While I

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Schwab,Wilhelm K
[pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Lukas Renggli [reng...@gmail.com] Sent: Saturday, January 01, 2011 2:06 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: Quite some software (Seaside, Mondrian, Magritte, Pier

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Stéphane Ducasse
right please open a bug entry and provide cs :) Stef Yes, this method name is unfortunate... I think we should just rename the method and tag copyFrom: as deprecated. And some versions later we'll implement copyFrom: as we think is appropriate. Cheers, Adrian BTW Sebastian, I think

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Stéphane Ducasse
I like copyStateFrom: as a name lukas there is copyFrom:to: and copyFrom: make a lot of sense as copyFrom: index until the end. Stef

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Igor Stasenko
On 1 January 2011 20:59, Stéphane Ducasse stephane.duca...@inria.fr wrote: I like copyStateFrom: as a name lukas        there is copyFrom:to:        and copyFrom: make a lot of sense as copyFrom: index until the end. +1 in the presence of #copyFrom:to: the current implementation of

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread Schwab,Wilhelm K
: [Pharo-project] An intuitive (or screwed) #copyFrom: I like copyStateFrom: as a name lukas there is copyFrom:to: and copyFrom: make a lot of sense as copyFrom: index until the end. Stef

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

2011-01-01 Thread csrabak
@lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: Quite some software (Seaside, Mondrian, Magritte, Pier, ...) depends on the current implementation of #copyFrom:, as it is an extremely efficient way to remember and restore the state of an object: rememberReceiverDuring