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 *fix* in etoys was to alter the file open (read/write) and silently fall back to saying oops try again (read-only) if it fails. Versus fixing all the places where you opened a file for reading, but as read/write (by default). On 2009-09-24, at 4:44 PM, Douglas Brebner wrote: > Schwab,Wilhelm K wrote: >> Hello all, >> >> I'm getting Ubuntu configured on my new $400 laptop, and just >> noticed that I can load one Pharo image at least twice w/o any >> error messages. Is that good or bad? I'm inclined to say it is >> bad, with caveats below. >> > > It's because unix allows you to open a file for write multiple times. > This also applies to in-image code which can make for interesting > platform dependant bugs when running on platforms that don't allow > this, > like windows. > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- = = = ======================================================================== John M. McIntosh <[email protected]> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
