Re: [cc65] scratch files on C64 or file spec and drive numbers

Hi,

> Might it be because it is a different programming language, with its own
> standard libraries? And the libraries (for any language) are the "emulation
> layers" adding features not present in the assembly interface? Take a simple
> printf() for example. If it wasn't an "emulation layer" with features (e.g.
> format string parsing and translating) not present in the assembly interface
> you would have to put things to stdout in a noticeably different manner.

Full ACK. With the right argumentation one could as well classify as
emulation the ASCII -> PETSCII translation for CBMs or the handling of
O_APPEND for Apple2s or ...

> P. S. I don't have a strong opinion on how the device numbers would be
> better passed for execution. It seems to me that it would be nice and more
> elegant from a programmer's POV to have a common syntax for passing all the
> file addressing components in one shot and parse it out of a single string
> but (at least for me) it is not critical and I am not fully aware of all
> possible clashes between different, common but non-standard-CBM extensions
> to the file addressing syntax like CMD, IDE64, etc.

Again full ACK. I simply wasn't aware at all that those extensions exist.

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