Thus spake Solar Designer (solaropenwall.com):
> A related topic -- has anyone audited the fts code in glibc? I am
> using it in the mtree port and it'd rather be safe.

I started implementing a "mini fts" for http://www.fefe.de/dietlibc/,
but I got disgusted and threw it away. I hope that it is just a
misunderstanding, but am I right that fts has to keep a data structure
to detect cycles?

Who designs APIs like this? Why not simply have a struct { char* name;
struct stat s; } and a callback that says if fts should traverse into
this subdir and one callback that gets called for each file? FTS can
not be implemented without malloc. IMHO that sucks big time.

Felix

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]