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

Hi,

> I don't think so. We talk about programmers here, not the end users, right?

[...]

> If my 0.02$ are of any value, I would prefer to steer this in the direction of cross-target source level compatibility. #8 anc Co. is definitely CBM specific...
>
> For CBM changing /0 to device 8 is 24 bits of code ;-) for other targets it might be a bit more complex but I think we'd win big if the code across targets would be source level compatible.

Okay, now we're from my perspective reaching a crossroads - and should
be clear about it:

Idea one: We strive for cross-target filenames. This would (at least
potentially) allow for non-trivial filename string constants in source
code to be valid across targets. However the syntax of those strings
would be so strange to users that it would potentially necessary to
provide target-specific UIs in order to create them from user input.

Idea two: We strive for "fully functional" filenames while admitting
that they are target-specific (beyond the trvial case of
"filename-only"). They would allow only to share trivial filename
strings in source code but would be (at least potentially) meaningful
enough to users of a certain target to be entered directly.

I personally strongly believe that we should head for 'idea two':

- Filesystem are just to different to really allow for a common
filename syntax. I.e. with Apple ProDOS files aren't accessed by drive
names/numbers at all but rather by volume names. So any "0:..." or
"A:..." wouldn't work.
- Such a common syntax would end up with the lowest common
denominator: 8.3 files without subdirectories.
- Such a common syntax would look much like an "emulation layer" in
the sense of Cygwin - which I believe isn't loved much.
- Such an approach would be quite heavyweight - at least on some targets.

To summarize: Id like to stay clear from "the big solution".

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