On 06.12.2012 17:15, Guillermo Polito wrote:


On Thu, Dec 6, 2012 at 5:02 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 6 December 2012 16:44, Guillermo Polito <guillermopolito@gmail.com> wrote:
>
>
> On Thu, Dec 6, 2012 at 4:35 PM, Igor Stasenko <siguctua@gmail.com> wrote:
>>
>> On 6 December 2012 16:28, Guillermo Polito <guillermopolito@gmail.com>
>> wrote:
>> > Wait, all delays are signaled when the image is saved? So, if I have a
>> > five
>> > minute delay in a process and I save the image 2 seconds later...
>> >
>> > [ d := 5 minutes asDelay.
>> > d wait.
>> > Transcript logCr: 'asd' ] fork.
>> >
>> > Smalltalk snapshot: true andQuit: false.
>> >
>> > That is a limitation but is also a bug :/...
>> >
>> no.. they are not.. sorry my first comment was not correct.. i
>> corrected myself in followup :)
>
>
> I understand the 1 delay<->1 semaphore. But I am not creating several ones.
> What if a second process saves the image while another one is waiting?
>
> This piece of code shows that problem.
>
> [ d := 5 minutes asDelay.
> d wait.
> Transcript logCr: 'asd' ] fork.
> Smalltalk snapshot: true andQuit: false.
>
> It will not honor the delay :/
>
ah.. ok. then that's indeed a problem.
about not honors: is it signal it prematurely or not signaling it at all?


prematurely :)

Hmmm, Delay >> startUp was modified recently, to restart the timer event loop.
The same doesn't happen in a 1.4 where that is absent.
Dunno whatever it was supposed to fix, but since the change initials indicate one Guillermo Polito was involved, he might be around to answer what might break if it is reverted :)

Cheers,
Henry