On 08 Jan 2011, at 23:07, Nicolas Cellier wrote:
You mean something like:
| collec |
collec := #('foo' 'bar').
shallowCopy := collec copy.
self assert: collec first == shallowCopy first
Well, yes those copies are shallow, but what's the difference between
copy, copyFrom:to: first,
+ 1
does anybody want to implement this hovering excellent idea.
On Jan 9, 2011, at 10:02 AM, Johan Brichau wrote:
And yes, the rule of thumb is that one reads the comments (or implementation)
of a method to understand it, rather than (only) trying to guess it's
semantics from its
Andy agreed to pair program it with me, starting next week. Unless someone
beats us to it ;-)
On 09 Jan 2011, at 10:12, Stéphane Ducasse wrote:
+ 1
does anybody want to implement this hovering excellent idea.
On Jan 9, 2011, at 10:02 AM, Johan Brichau wrote:
And yes, the rule of
Excellent
You know what I'm dreaming of (may be this is already in)
you get the list of methods in the method list and you start to type and
automatically all the methods not matching are greyed out
or we only see the methods matching the beginning.
Stef
On Jan 9, 2011, at 10:26 AM, Johan
Nicolas wrote:
Then group the selectors (first, first: etc..), explain that they are
extensions, and don't need a copy prefix, because anyway most messages
will do a copy.
You are aware first doesn't copy, do you? The explanation should be
that you always have to take a look at the implementation
2011/1/8 Stephan Eggermont step...@stack.nl:
Nicolas wrote:
Then group the selectors (first, first: etc..), explain that they are
extensions, and don't need a copy prefix, because anyway most messages
will do a copy.
You are aware first doesn't copy, do you? The explanation should be
that you
