Hi, Interesting. How do I do that? Doru
On May 22, 2016, at 9:49 AM, Max Leske <maxleske@gmail.com> wrote:
Another thing you can do (but be careful) is to close the changes file. Sources (and change operations) will then not be written to disk which saves a lot of I/O operations. I use this for some special imports. Iâm not sure however, how well that will work in Pharo 5 (Iâve been doing this in Pharo 1.3).
Cheers, Max
On 21 May 2016, at 23:51, Eliot Miranda <eliot.miranda@gmail.com> wrote:
Hi Doru,
On May 21, 2016, at 12:50 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
I am looking for ways to make loading of code from an st file faster. To this end, I would like to find in-image mechanisms that are not mandatory for obtaining a functional image.
For example, one place I look at is SystemAnnouncer uniqueInstance, and I know that I should have no Nautilus open and that I can disable Renraku and GTExample:
ReRuleManager uniqueInstance unsubscribe. GTExampleOrganizer instance stopSystemAnnouncements.
What else do you see around?
Strikes me that parsing, not compiling and either holding onto the source String or simply keeping a pointer into the source file makes sense. Compilation to methods can wait until installation. With that approach you need no notifications at all. HTH
_,,,^..^,,,_ (phone)
Cheers, Doru
-- www.tudorgirba.com www.feenk.com
"Don't give to get. Just give."
-- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."