Re: [cc65] Re: readdir bug

From: Spiro Trikaliotis <>
Date: 2012-09-17 20:35:07

* On Mon, Sep 17, 2012 at 08:17:35PM +0200 Ullrich von Bassewitz wrote:
> Hi!
> On Mon, Sep 17, 2012 at 08:08:01PM +0200, Spiro Trikaliotis wrote:
> > 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().
> Yes, good idea.
> This would be a one-liner calling "seekdir (DIR, telldir (DIR))".

Oh... I did not even see that everything I need is already there, so,
there is no need to spill everything into the library.

> I'm not sure
> if the library should really supply such a function.

Then, why not:

#define _readdir_restart(DIR) seekdir((DIR), telldir(DIR))


On platforms that do not need this, this macro could be defined as an
empty one.

> But that would mean that a program using readdir will always get telldir and
> seekdir linked in.

You're absolutely right, I totally missed this.

> > Another option: Read in the directory blocks one after the other, and
> > process the directory entries on the cc65 side.
> I'm really trying to avoid solutions like this. They create lots of code and
> incompatibilities with several kind of hardware.

I can understand this. This would have been only a "last resort"
solution, anyway.


Spiro R. Trikaliotis
To unsubscribe from the list send mail to with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Mon Sep 17 20:35:29 2012

This archive was generated by hypermail 2.1.8 : 2012-09-17 20:35:33 CEST