Re: [cc65] Filenames for POSIX functins on CBM targets

Hi,

> The point is: I can have the same code to access floppy drives on all
> (?) platforms CC65 supports, on all devices that it supports. The small
> setup that is platform-specific does not count for me here.
>
> BTW, the setup could be hidden in a chdir() function, making it
> cross-platform again.

I see this from a somewhat different perspective. It's about
declarative vs. programmatic.

The string I'm asking for declares the location of a file. Independent
from some point in the runtime of a program and independent from other
files and other aspects of the environment like current <whatever>.

The _curunit is something I need to set before opening a file and need
to keep track of when opening another file. It's basically like having
only relative paths in a modern OS. Non-trivial file i/o programs
typically come to the point of converting all relative paths into
absolute paths and use only those.

This is not just a question of some setup - at least to me.

>> Again - Im _NOT_ looking for a single path syntax for all targets! I'm
>> only looking for _SOME_ path syntax on every target. But the CBMs have
>> none at all. Therefore there's no need at all to find such a char.
>
> No? I thought you proposed the colon?

Only for the CBMs and only because the drive specifier already uses
them. I don't care at all what char it is. It would be great if it
could be entered from the keyboard with reasonable effort.

I don't even ask for a specific char. I only ask for the equivalent of
an absolute pathname on CBM for the POSIX functions. A single string
that when interpreted contains all information necessary to know the
location and name of a file. For CBMs only!

The other targets are already fine the way they are.

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