Deferring code update calls ...

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

Deferring code update calls ...

marcel.taeumel
Hi, there.

What do you think about triggering code updates not directly but deferred via a project's deferred UI messages?

Here is a change set that does that:
thin-update-process.cs

Since we do not update the compiled methods in existing process call stacks, update code would be more robust if the respective call stack would be small. For example, this affects code that uses direct inst var accesses like HandMorph >> #handleEvent:.

Drawback: If you want to update the system programmatically such as in a deployment scenario, you would have to account for that. Fabio? :D

Best,
Marcel
Reply | Threaded
Open this post in threaded view
|

Re: Deferring code update calls ...

Bert Freudenberg
On Wed, Jun 29, 2016 at 3:10 PM, marcel.taeumel <[hidden email]> wrote:
Hi, there.

What do you think about triggering code updates not directly but deferred
via a project's deferred UI messages?

Yes.
 
Drawback: If you want to update the system programmatically such as in a
deployment scenario, you would have to account for that. Fabio? :D

No. Don't put it in the updater code, but into the menu item handler.

- Bert -