This bug is fixed in a 3.2.7Beta6 mac VM I've put into the update process.
a) Fixed issue with high ascii characters in path names b) Fixed bug with some aliased path constructs (no bug reported, but found it in testing)
This is a resend, this time with the promised attachment!
At 17:08 -0700 05/22/2002, John M McIntosh wrote:
having a repeatable test case would be nice.
Please try the attached SUnit tests. When I run them on Squeak 3.2.7Beta5 they fail, but on Squeak 3.0Alpha21MTCarbon they pass. This is using the same image in both cases.
Please let me know if you can reproduce this error.
What I think is going on is that once an attempt to open a file for reading has failed (e.g., because the file is not there), then all subsequent attempts to create new files for writing will fail.
The only slightly unusual thing about my setup is that the current directory has the Macintosh option-f (folder) character (asciiValue 196) as the final character of its name. However, this character has never caused a problem previously.
Andrew
Attachment converted: Lamie:StdFileS.cs (TEXT/R*ch) (000BDDA4)