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

Re,

On Thu, Aug 16, 2012 at 09:23:07AM +0200, Oliver Schmidt wrote:
> Hi,
> 
> > the library is however ment to support the least common denominator for a
> > generic portable program.
> 
> If "portable" refers to things like POSIX then this would mean to
> remove i.e. conio, tgi, emd, mou, dio, ser ...
> 
> If "portable" refers to cc65-cross-target then this would mean to
> remove i.e. POSIX i/o, stdio, dio, emd, ser, mou ...
> 
> > something like a filemanager would most certainly
> > use target specific code anyway.
> 
> While this may be true we're already into "file management" with
> rename(), remove() - and on hierarchical filesystems with mkdir() and
> rmdir().
> 
> What I however consider the most important point: If we support
> opendir() then this means we're going for scenarios beyond users
> typing in filenames or hardcoded filenames. In those scenarios it' s
> the next logical step to discover not only files in the "current
> location" but in "other locations" as well.

I have the feeling, that this whole topic is a bit "oversized" for a C
compiler targeting CBM machines. What I mean here: some aspects of
POSIX-like VFS assumes quite complex OS-side support for that, on a machine
like C64, the compiler should generated code to support this, since there is
no OS behind which can give you that. But it would create quite massive
sized programs if every compiled C program on C64 also includes the support
code for these ...  It would be better to write a minimalistic (mono tasking
is enough) OS to run these programs on top of it, or having some loadable
module, etc, as not every programs may need such features in detail on an
average CBM platform, I think. Most of them only want to read (or maybe
write) files on a disk drive, and that's all. If someone wants to implement
a file manager using cc65 targeting eg C64, it's another story.

Sorry if I wrote non-sense, I really don't know too much about the
implementation details on these in cc65/etc, but I think one aspect is quite
important: to be able to "leave out" more complex file handling stuffs if
someone does not need it. If it's already decided (or had?) this way, sorry
for the OT, I really use only very basic file I/O without any complex
question about it compared to the recent threads on the list on this topic
:)

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