Hello, * On Sun, Aug 12, 2012 at 09:14:50PM +0200 Oliver Schmidt wrote: > Hi, > > > Looking at the whole discussion, I am getting more and more to the > > conclusion that open() should probably just pass that name directly to the > > os. Exactly. That's where at least I started from, after reading about groepaz' comment about chdir()/getcwd(). > Taking that seriously the current code that adds "0:" if it doesn't > recognize a drive specification would need to be removed. Yes. > Otherwise > i.e. instead of "abc.txt" the file "0:abc.txt" would be written to the > tape drive... Even worse, for dual disk drives, it changes the behaviour: If I last accessed a file on drive 1, then writing "abc.txt" will write to drive 1, but "0:abc.txt" will write to drive 0. I already stated elsewhere hat I consider the adding of "0:" as an error. At least, it would surprise anyone who already worked on the platform and knows about that "last accessed drive" behaviour. It's like on Windows: If I write a file "abc.txt", I would not expect it to appear on "c:\abc.txt" if the current working directory is not "c:\" by accident. Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sun Aug 12 21:40:19 2012
This archive was generated by hypermail 2.1.8 : 2012-08-12 21:40:23 CEST