Probably yes. However, in that case the issue is at least internal to the implementation as nobody will actually use that class directly.
Cheers, Doru On Sat, Sep 5, 2015 at 11:56 PM, Bernardo Ezequiel Contreras < [email protected]> wrote: > Excuse me, but what about the following messages > > MessageBrowser browse: > ({WeakSubscriptionBuilder>>#on:do:. > WeakSubscriptionBuilder>>#on:send:to:}) > > should be deprecated, or not? > > > > On Sat, Sep 5, 2015 at 5:24 PM, stepharo <[email protected]> wrote: > >> Hi >> >> in announcer we have >> >> when: anAnnouncementClass send: aSelector to: anObject >> "Declare that when anAnnouncementClass is raised, anObject should >> receive the message aSelector. >> When the message expects one argument (eg #fooAnnouncement:) the >> announcement is passed as argument. >> When the message expects two arguments (eg >> #fooAnnouncement:announcer:) both the announcement and the announcer >> are passed as argument" >> >> ^ self subscribe: anAnnouncementClass send: aSelector to: anObject >> >> >> could we reduce the cognitive load and make sure that the API is only one >> protocol for example when: send: to:? >> I found it confusing and I have to check that this is indeed the same. >> I think that having one way is far enough. >> >> What do you think? >> Stef >> >> > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. > -- www.tudorgirba.com "Every thing has its own flow"
