[Pharo-project] Opening image multiple times - bug or feature?

Douglas Brebner squeaklists at fang.demon.co.uk
Sat Sep 26 01:17:39 EDT 2009

Igor Stasenko wrote:
> 2009/9/25 Douglas Brebner <squeaklists at fang.demon.co.uk>:
>> John M McIntosh wrote:
>>> Actually the WIndows VM use to lie, might still, if you opened a file
>>> READ/WRITE but it was read only, like on a CD, then the windows VM would
>>> say SURE no problem.  This caused grief for macintosh users using one-
>>> click apps on a CD because we would cause a walkback saying we
>>> couldn't open the file READ/WRITE.
>> The problem I had was code that was written on unix that opened the same
>> file twice in write mode in the initialization methods. Broke nastily on
>> windows with confusing exceptions and leaking file handles iirc.
>> BTW, opening an image twice at the same time on windows give the
>> "changes file not accessible" popup at startup of the second image.
> Right, because on windows you can obtain an exclusive write-lock on a
> file for a process and disallow others
> to open it for writing.
> AFAIK, POSIX systems also allowing locking the file handle through
> using ioctl().

Yep, and windows isn't the only one that does this by default, it's
merely the most common :)

More information about the Pharo-dev mailing list