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

Vassili Bykov smalltalkbigot at gmail.com
Tue Apr 8 22:46:36 UTC 2008


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 <itsme213 at hotmail.com> 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" <gazzaguru2 at btinternet.com> 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?
>
>
>
>
>



More information about the Squeak-dev mailing list