Re: [cc65] Uniform mass storage device discovery and file locations

I do not state this frivolously, but getcwd() on the Commodore is a HUGE
effort, and for one of the most common scenarios (SD2IEC devices), it fails
if the user is inside a disk image. On the CBM targets, getcwd() would have
to calculate it's position on the disk by moving backwards and building a
stack of the strings of the directory names as it goes.  This will use a
lot of memory and is problematic if a user has changed a directory's header
name without also changing the filename in the parent directory, which is
entirely possible. It will fail completely if the user starts out in a disk
image as the getcwd() code will not be able to restore the drive to it's
original state after calculating the path.

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.