#fixCallbackTemps from Grease package (included with SeaSide)

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

#fixCallbackTemps from Grease package (included with SeaSide)

timrowledge
A note for anyone working on Grease & Seaside -
After installing Seaside I note that there are a couple of potentially problematic Undeclared items. They both appear to be related to Grease methods and in particular block context temps.

The offending items are #home and #startpc, both referenced in BlockContext>>#fixCallbackTemps. This is possibly related to the changes in closures etc we've recently added for the next release. There are four implementors and perhaps 20 senders that will need some attention. It might well be making for interesting odd effects in SeaSide.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: D: Detonate



Reply | Threaded
Open this post in threaded view
|

Re: #fixCallbackTemps from Grease package (included with SeaSide)

Levente Uzonyi
On Mon, 5 Aug 2019, tim Rowledge wrote:

> A note for anyone working on Grease & Seaside -
> After installing Seaside I note that there are a couple of potentially problematic Undeclared items. They both appear to be related to Grease methods and in particular block context temps.
>
> The offending items are #home and #startpc, both referenced in BlockContext>>#fixCallbackTemps. This is possibly related to the changes in closures etc we've recently added for the next release. There are four implementors and perhaps 20 senders that will need some attention. It might well be making for interesting odd effects in SeaSide.

BlockContext has become obsolete since Cog, which uses BlockClosure.
All the #fix*Temps magic is unnecessary with closures.

Levente

>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Strange OpCodes: D: Detonate