On Sat, Jul 15, 2017 at 11:15 AM, Edward K. Ream <edream...@gmail.com> wrote: > > > On Sat, Jul 15, 2017 at 10:48 AM, Offray Vladimir Luna Cárdenas < > off...@riseup.net> wrote: > >> The thread about how Pharo instant update works, started to move. Here >> are the answers of a seasoned Smalltalker, with links to deepen the >> explanations: >> > I've taken a brief look at this. At one time, decades ago now, I did take a look at the SmallTalk internals. I think its fair to say the following: 1. The SmallTalk VM is a bit more dynamic than Python's. 2. It's not going to be possible to simulate, for example, "becomes" in Python. 3. More detailed study of SmallTalk/Pharo is not likely to help us for *our* purposes. I've been meaning to point of for a few days that developing with @button or @test *already simulates instant reload pretty well*. On re-reading the FAQ entry for the "stupendous Aha <http://leoeditor.com/FAQ.html#what-is-the-stupendous-aha-and-why-does-it-matter>", I see that it's not explained well enough. There are also hints about this topic here <http://leoeditor.com/unitTesting.html#test-driven-development-in-leo>. We've also discussed imp.reload on leo-editor recently. Instant reloading techniques are not as widely known as they should be. All these ideas must be brought together so that everyone can see the big picture. I'll do this in a new thread, which will likely become pre-writing for an important new chapter. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
