Re: [cc65] Re: readdir bug

From: Spiro Trikaliotis <ml-cc651trikaliotis.net>
Date: 2012-09-17 20:08:01
Hello,

* On Mon, Sep 17, 2012 at 05:36:30PM +0200 Ullrich von Bassewitz wrote:
 
> Actually, I was waiting for comments. Maybe someone has another idea.

I still see the possibility to have a function _readdir_restart() to
call whenever there is file I/O after the readdir(). This way, the code
can tell the readdir() code "reload the directory" by using seekdir().

If the code does not need this, it just does not have to call
_readdir_restart(), and everything will work as it works now.

readdir() would be slowed down only by a test for a flag set in
_readdir_restart() in the normal case. Only if it is set, there will be
a penalty because seekdir() will be called internally.


Another option: Read in the directory blocks one after the other, and
process the directory entries on the cc65 side. This would work out easy
for 4040, 2031, 154x, 155x and 157x disks, even with GEOS (as I know the
format used by these drives very well). I do not know how many
modifications there are out there (CMD? Any others?), and I do not know
about the format of a SFD1001, 8050, 8250, 1581, FD-x000 and other
drives, IDEDOS, ...

This might be a big undertaking, but it would fix the issue.

Regards,
Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Mon Sep 17 20:08:24 2012

This archive was generated by hypermail 2.1.8 : 2012-09-17 20:08:27 CEST