[Pharo-project] Announcer methods are bloated
stephane.ducasse at inria.fr
Tue Apr 19 21:40:51 CEST 2011
in addition I do not like to use on:do: since I prefer to keep it for exception.
Now did you check senders of each of these methods?
What would be a path to go to your solution. In fact subscribe:do: is not a really good name too.
I prefer on: do: (even if I do not like the overload) and on:send:do:
I think that we could deprecate when:do: first.
Then may be deprecate subscribe:do:
On Apr 19, 2011, at 8:07 PM, DougEdmunds wrote:
> If Announcements are newly added to core (discussion at
> why not start with a trimmed down set of methods? Why start with bloat?
> Announcer has these two core methods:
> 1) subscribe:do
> 2) subscribe:send:to:
> are fine.
> There is no need for
> 3) on:do (just calls 1)
> 4) on:send:to: (just calls 2)
> 5) when:do (also justs calls 1)
> View this message in context: http://forum.world.st/Announcer-methods-are-bloated-tp3461131p3461131.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
More information about the Pharo-project