Smalltalk › Amber Smalltalk

Possible issue with Announcer>>unsubscribe:

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

bowerandy-2

Possible issue with Announcer>>unsubscribe:

Folks,

It might be me but I can't seem to get Announcer>>unsubscribe: to work for subscriptions that have a block as their valuable. This is because the blocks have no #receiver and aren't therefore picked up by the #reject in #unsubscribe.

I'm not sure I can see how its possible to get this to work easily. Is there any other way to unsubscribe blocks; how does this side of things work in Pharo?

best regards

Andy Bower

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Nicolas Petton

Re: Possible issue with Announcer>>unsubscribe:

Hi!

Indeed, this is an issue in Amber's announcements. I usually use
#on:send:to: instead, exactly because of this issue.

Blocks have no #receiver, and probably will never have.

Cheers,
Nico

bowerandy writes:

> Folks,
>
> It might be me but I can't seem to get Announcer>>unsubscribe: to work for
> subscriptions that have a block as their valuable. This is because the
> blocks have no #receiver and aren't therefore picked up by the #reject in
> #unsubscribe.
>
> I'm not sure I can see how its possible to get this to work easily. Is
> there any other way to unsubscribe blocks; how does this side of things
> work in Pharo?
>
> best regards
>
> Andy Bower

--
Nicolas Petton
http://nicolas-petton.fr

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

bowerandy-2

Re: Possible issue with Announcer>>unsubscribe:

Nico,

Indeed, this is an issue in Amber's announcements. I usually use
#on:send:to: instead, exactly because of this issue.
Blocks have no #receiver, and probably will never have.

Thanks. Yes, that's what I ended up doing. Perhaps, the #on:do: form should be deprecated if its never likely to work correctly?

Best regards

Andy Bower

Ryan Simmons-2

Re: Possible issue with Announcer>>unsubscribe:

I know that in Gemstone they have Announcer>>on:do:for:.

Perhaps it could be added to Amber.

On 31 January 2014 09:19, bowerandy <[hidden email]> wrote:

Nico,

Indeed, this is an issue in Amber's announcements. I usually use
#on:send:to: instead, exactly because of this issue.
Blocks have no #receiver, and probably will never have.

Thanks. Yes, that's what I ended up doing. Perhaps, the #on:do: form should be deprecated if its never likely to work correctly?

Best regards

Andy Bower

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Nicolas Petton

Re: Possible issue with Announcer>>unsubscribe:

Hi!

Yes, #on:do:for: might be a good idea :)

2014-01-31 Ryan Simmons <[hidden email]>:

I know that in Gemstone they have Announcer>>on:do:for:.

Perhaps it could be added to Amber.

On 31 January 2014 09:19, bowerandy <[hidden email]> wrote:

Nico,

Indeed, this is an issue in Amber's announcements. I usually use
#on:send:to: instead, exactly because of this issue.
Blocks have no #receiver, and probably will never have.

Thanks. Yes, that's what I ended up doing. Perhaps, the #on:do: form should be deprecated if its never likely to work correctly?

Best regards

Andy Bower

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Nicolas Petton

Re: Possible issue with Announcer>>unsubscribe:

https://github.com/amber-smalltalk/amber/issues/881

2014-01-31 nicolas petton <[hidden email]>:

Hi!

Yes, #on:do:for: might be a good idea :)

2014-01-31 Ryan Simmons <[hidden email]>:

I know that in Gemstone they have Announcer>>on:do:for:.

Perhaps it could be added to Amber.

On 31 January 2014 09:19, bowerandy <[hidden email]> wrote:

Nico,

Indeed, this is an issue in Amber's announcements. I usually use
#on:send:to: instead, exactly because of this issue.
Blocks have no #receiver, and probably will never have.

Thanks. Yes, that's what I ended up doing. Perhaps, the #on:do: form should be deprecated if its never likely to work correctly?

Best regards

Andy Bower

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.