A little MC patch

Jason Johnson jason.johnson.081 at gmail.com
Sat Feb 16 13:58:59 UTC 2008


Sorry, I didn't parse that (too many "no"'s I think :).  The GUI
doesn't actually lock does it?  It shows a status bar while it's
working doesn't it?  But if the MC system works by (a) looking at the
current state of the system and then (b) applying what is missing to
bring the system up to date then it is important that no modifications
to any methods are allowed until the whole operation is complete.

On Feb 16, 2008 2:33 PM, Igor Stasenko <siguctua at gmail.com> wrote:
> On 15/02/2008, Jason Johnson <jason.johnson.081 at gmail.com> wrote:
> > Do you block people changing methods in their image with a separate
> > browser?  It is my understanding that this was the purpose for letting
> > the GUI just block: to make sure no one could edit methods while in an
> > odd state.
> >
> No, all these no-locks only in places where no code modification
> performed, and therefore no need to lock UI.
>
> --
>
> Best regards,
> Igor Stasenko AKA sig.
>
>



More information about the Squeak-dev mailing list