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

Hi,

> For me, the conclusion is simple: We do not have many chars that are not
> valid commonly for all cases. Thus, the only option that comes to
> mind for me is to say: The device number *must* be specified in front of
> the file name. Thus, the format would be to have "8:name", "10:name" or
> ":name", anything else is invalid.

If we follow that argumentation then we're back at square one - as Uz
predicted :-(

I'm pretty sure nobody wants a program with fopen("abc.txt", ...) fail
with an invalid filename.

If allowing filenames with all kinds of weird chars and supporting
tape drives and <you name it> through the POSIX functions is
considered more important that being able to select between device 8
and 9 then probably the current solution is appropriate.

However by now nobody will be surprised to read that I personally
don't think so. Programs working tape drives and whatever are mot
likely no cross-target and can therefore easily use the cbm_k_...()
family of functions, which are presumably better suited for the task
at hand anyway.

I'm still asking for a reasonable solution for the usual case of
handling files on floppy (or hard disk) drives.

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