[Pharo-project] End of startup script behavior
bschwab at anest.ufl.edu
Tue Jan 31 11:10:23 CET 2012
Reminds me of one of early Dolphin hacks. OA being who they are, eventually fixed the snag. The problem was that event loop needed to be running for some late startup tasks to run properly. In this case, the image would do nothing vs. quit, but I suspect it's the same lesion under a different name.
My fix was to queue a deferred action and then fork a thread to wait until after OA's startup, and then did the offending work. It worked, and they added more or less the same thing to Dolphin. Interestingly, I never had to remove my hack<g>,
Please note (nobody wants to hear this) that Dolphin has thread synchronization objects, weak collections, and other nice things that make us look bad by comparison, even ignoring the calendar differences.
From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] on behalf of Sven Van Caekenberghe [sven at beta9.be]
Sent: Tuesday, January 31, 2012 4:57 AM
To: Pharo-project at lists.gforge.inria.fr Development
Subject: [Pharo-project] End of startup script behavior
Maybe I missed this, but did something change with the behavior at the end of a startup script between 1.3 and 1.4 ?
It used to be that the image kept on running unless you asked it to quit explicitly, now it seems that the image automatically quits unless you keep it busy. Can someone confirm this ? Was this intentional ?
What would be the recommended way to keep the image open ?
Somehow something like
[ (Delay forDuration: 1 hour) wait ] repeat.
seems so silly, but it works.
More information about the Pharo-project