How to decide the file type in Cygwin?

Randall R Schulz rrschulz@cris.com
Tue Mar 25 05:11:00 GMT 2003


Glenn,

At 20:04 2003-03-24, Glenn Fowler wrote:

>some unix systems { linux bsd uwin } support the
><dirent.h> struct dirent d_type field
>
>the dt_type values { DT_UNKNOWN DT_DIR DT_LNK } can be used to optimize
>directory traversals that otherwise would have to stat() directory
>entries to discover/count subdirectories

Thanks for the information.

"You snooze, you lose." I've been napping.

To the original poster: Portable coding will require that you either 
use the stat(2) method or feature your source code (use #if or #ifdef) 
to accommodate the variety of system capabilities.


>-- Glenn Fowler


Randall Schulz


>On Mon, 24 Mar 2003 15:38:17 -0800 Randall R Schulz wrote:
> > Yang,
>
> > Unix file systems don't store the the type of a file system entity in
> > the directory entry used to access that entity, they stored in the
> > so-called "inode." Once you have a name, use the stat(2) system call to
> > get its inode information. From there you'll be able to determine what
> > kind of an entity it is. If you have a file descriptor, then fstat(2)
> > will do the same.
>
> > Randall Schulz
>
> > At 15:27 2003-03-24, Yang, Huaichen wrote:
> > >I need to list all files in a folder (including sub-folder,
> > >recursively), and I tried some sample codes in GNU C manual, as
> > >follows:
> > >
> > >...
> > >
> > >The sample was working. Then I added some codes to check the
> > >ep->d_type (the type of the file). If it was a directory, the
> > >program would check the sub-folder recursively. However, I
> > >encountered a compiler error. The property d_type was not defined
> > >in the Cygwin header file dirent.h. It seems that we cannot
> > >distinguish the files from the directories. Is that true? Doesn't
> > >anybody have a good idea to do this?
> > >
> > >Thank you very much in adavance!


--
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/



More information about the Cygwin mailing list