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. Regards, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Aug 16 09:23:24 2012
This archive was generated by hypermail 2.1.8 : 2012-08-16 09:23:29 CEST