From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: Mark Bradshaw <bradshaw@staff.crosswalk.com>,
Mark Bradshaw <bradshaw@staff.crosswalk.com>,
"'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: Readdir
Date: Wed, 18 Jul 2001 10:36:00 -0000 [thread overview]
Message-ID: <4.3.1.2.20010718133446.02157940@pop.ma.ultranet.com> (raw)
In-Reply-To: <911C684A29ACD311921800508B7293BA010A8A33@cnmail>
Yes, that's the readdir() Cygwin uses/provides.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
At 12:52 PM 7/18/2001, Mark Bradshaw wrote:
>I've found code for readdir in winsup/cygwin/dir.cc. Can you confirm that
>this is the correct code?
>
>-----Original Message-----
>From: Mark Bradshaw
>Sent: Wednesday, July 18, 2001 12:25 PM
>To: 'cygwin@cygwin.com'
>Subject: RE: Readdir
>
>
>Ah. That would explain then, wouldn't it. <grin> Can you point out where
>the readdir code is in the cygwin source?
>
>Mark
>
>-----Original Message-----
>From: Christopher Faylor [ mailto:cgf@redhat.com ]
>Sent: Wednesday, July 18, 2001 12:10 PM
>To: cygwin@cygwin.com
>Subject: Re: Readdir
>
>
>On Wed, Jul 18, 2001 at 10:20:55AM +0200, Corinna Vinschen wrote:
> >On Tue, Jul 17, 2001 at 06:28:37PM -0400, Mark Bradshaw wrote:
> >> Here's my monthly "I must be an idiot" question.
> >>
> >> I'm looking at the code in the cygwin source for readdir
> >> (/usr/src/cgwin-1.3.2-1/newlib/libc/posix/readdir.c). It's referencing
> >> members of the DIR structure that I'll be darned if I can find in my
> >> dirent.h file (/usr/include/sys/dirent.h).
> >>
> >> The code is referencing dd_loc, dd_buf, dd_size, and dd_len (among
>others)
> >> which don't seem to be valid DIR members. Am I looking at the wrong
>source
> >> and/or the wrong header?
> >
> >It's in the mingw/dirent.h header.
>
>Actually, cygwin doesn't use the readdir.c in newlib. It has its
>own implementation. I don't think that the one in newlib is
>related to mingw.
>
>cgf
>
>--
>Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting: http://cygwin.com/bugs.html
>Documentation: http://cygwin.com/docs.html
>FAQ: http://cygwin.com/faq/
>
>--
>Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting: http://cygwin.com/bugs.html
>Documentation: http://cygwin.com/docs.html
>FAQ: http://cygwin.com/faq/
>
>--
>Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting: http://cygwin.com/bugs.html
>Documentation: http://cygwin.com/docs.html
>FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-07-18 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 9:52 Readdir Mark Bradshaw
2001-07-18 10:36 ` Larry Hall (RFK Partners, Inc) [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-18 9:24 Readdir Mark Bradshaw
2001-07-17 15:28 Readdir Mark Bradshaw
2001-07-18 1:22 ` Readdir Corinna Vinschen
2001-07-18 9:10 ` Readdir Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.3.1.2.20010718133446.02157940@pop.ma.ultranet.com \
--to=lhall@rfk.com \
--cc=bradshaw@staff.crosswalk.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).