On Aug 6 20:28, Corinna Vinschen wrote: > On Aug 6 13:31, Christopher Faylor wrote: > > On Fri, Aug 06, 2010 at 06:39:25PM +0200, Corinna Vinschen wrote: > > >On Aug 6 10:51, Chris Sutcliffe wrote: > > >> On 6 August 2010 10:11, Corinna Vinschen wrote: > > >> > On Aug ??6 09:40, Christopher Faylor wrote: > > >> >> On Fri, Aug 06, 2010 at 09:33:41AM -0400, Chris Sutcliffe wrote: > > >> >> >I assume d_fileno and d_reclen may be part of __d_unused1 or > > >> >> >__d_internal1? ??I'd appreciate some help here, since I'm not sure > > >> >> >what > > >> >> >to do at this point. > > >> >> > > >> >> No, they are not part of either of those fields. ??If they were > > >> >> they would be exposed. > > >> >> > > >> >> They simply are not implemented. > > >> > > > >> > And they don't have to. ??Per POSIX, only d_ino and d_name can be > > >> > expected by a portable application(*). > > >> > > >> Fair enough, thankfully they are don't seem to be used by the code, so > > >> I added an '#ifndef __CYGWIN__' around them and have managed to get by > > >> this. > > > > > >Btw., d_fileno is just another old name for d_ino. The Linux headers > > >defines it thus as `#define d_fileno d_ino'. We can do the same in > > >Cygwin. Maybe that minimizes some porting effort. > > > > Huh. I thought the d_fileno actually stood for the file handle of the > > opened directory. > > The Linux headers suggest that it was an old BSD name.
Actually it's not old at all. BSD still uses d_fileno for the name of this structure member in sys/dirent.h and d_ino is just a define in dirent.h. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
