Am Dienstag, den 18.07.2006, 21:34 +0200 schrieb Marco van de Voort: > > Am Dienstag, den 18.07.2006, 15:42 +0200 schrieb Marco van de Voort: > > > > > > *dir functions are special. These are (3) functions and are done by an own > > > probably not 100% compat implementation in syscall ports. > > > > I'll go looking there, thanks. > > > > ... has this changed recently? I looked at almost any file having > > "syscall" in it's name but didn't find anything regarding "*dir". I > > forgot to mention that I'm using fpc 2.0.2 release sources atm. > > Did you grep?
Yes, but with a wrong pattern - found them now. > For linux they are in linux/ossysc.inc, > prefix by fp as per baseunix convention (fpreaddir,fpopendir) > > > > Why would you want > > > to do this? > > > > Because "readdir_r" gives proper error messages and "readdir" doesn't. > > Depends on implementation, but actually I meant: why are you not using > findfirst/findnext which is portable? Because that's my target. I'm trying to make an experimental new (sysutils.)FindFirst/-Next implementation with detailed error messages. But first I have to review the *dir function implementations, up to now I assumed the libc functions would be used ... and my first finding is: there are the aliases defined that get resolved in the function and procedure declarations in bunxh.inc. Thank you, Marc _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
