[squeak-dev] Error: Attempt to evaluate a block that is already being evaluated - what does it mean?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Error: Attempt to evaluate a block that is already being evaluated - what does it mean?

Sophie424
I am using a block as a parameter in a recursive function, and get this
error. Does this have to do with blocks as not-quite-full closures? If so,
any workarounds?

Thanks - Sophie




Reply | Threaded
Open this post in threaded view
|

RE: [squeak-dev] Error: Attempt to evaluate a block that is alreadybeing evaluated - what does it mean?

Gary Chambers-4
Yes. You can send #fixTemps to the block.

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]]On Behalf Of
> itsme213
> Sent: 08 April 2008 10:52 PM
> To: [hidden email]
> Subject: [squeak-dev] Error: Attempt to evaluate a block that is
> alreadybeing evaluated - what does it mean?
>
>
> I am using a block as a parameter in a recursive function, and get this
> error. Does this have to do with blocks as not-quite-full
> closures? If so,
> any workarounds?
>
> Thanks - Sophie
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Re: Error: Attempt to evaluate a block that isalreadybeing evaluated - what does it mean?

Sophie424
I already tried several combinations of fixTemps (brute force :) with no
luck. Oh well, this has bitten me before, any hope for closures in 3.10 (or
3.11, ...)?

Thanks - Sophie


"Gary Chambers" <[hidden email]> wrote in message
> Yes. You can send #fixTemps to the block.

>> Subject: [squeak-dev] Error: Attempt to evaluate a block that is
>> alreadybeing evaluated - what does it mean?
>>
>>
>> I am using a block as a parameter in a recursive function, and get this
>> error. Does this have to do with blocks as not-quite-full
>> closures? If so,
>> any workarounds?




Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Re: Error: Attempt to evaluate a block that isalreadybeing evaluated - what does it mean?

Vassili Bykov-2
The workaround is

  aBlock reentrant value

This non-reentrancy issue is orthogonal to what #fixTemps works around
(well, almost).

On Tue, Apr 8, 2008 at 3:18 PM, itsme213 <[hidden email]> wrote:

> I already tried several combinations of fixTemps (brute force :) with no
>  luck. Oh well, this has bitten me before, any hope for closures in 3.10 (or
>  3.11, ...)?
>
>  Thanks - Sophie
>
>
>  "Gary Chambers" <[hidden email]> wrote in message
>
> > Yes. You can send #fixTemps to the block.
>
>
>
> >> Subject: [squeak-dev] Error: Attempt to evaluate a block that is
>  >> alreadybeing evaluated - what does it mean?
>  >>
>  >>
>  >> I am using a block as a parameter in a recursive function, and get this
>  >> error. Does this have to do with blocks as not-quite-full
>  >> closures? If so,
>  >> any workarounds?
>
>
>
>
>