diff options
| author | DJ Delorie <dj@redhat.com> | 2001-10-15 22:50:13 -0400 |
|---|---|---|
| committer | DJ Delorie <dj@gcc.gnu.org> | 2001-10-15 22:50:13 -0400 |
| commit | aac04c15d761628889f138b16219bce27f25bbb2 (patch) | |
| tree | 58903ff3e4335306b7c9f5c24e8baf3b9a9922a8 /libiberty/fdmatch.c | |
| parent | 2d4368e6cd739fadc7e3cc1111f30f2941e8a8a3 (diff) | |
Makefile.in (TEXIFILES): Add fnmatch.txh.
* Makefile.in (TEXIFILES): Add fnmatch.txh.
(maint-undoc): New.
maint-tool: Add "undoc" tool.
* alloca.c, argv.c, asprintf.c, choose-temp.c, concat.c,
fdmatch.c, ffs.c, getruntime.c, insque.c, lbasename.c,
make-temp-file.c, mkstemps.c, pexecute.c, random.c, spaces.c,
strerror.s, strsignal.c, strtol.c, vasprintf.c: Add or update
documentation.
* fnmatch.txh: New.
* functions.texi: Regenerate.
From-SVN: r46274
Diffstat (limited to 'libiberty/fdmatch.c')
| -rw-r--r-- | libiberty/fdmatch.c | 32 |
1 files changed, 13 insertions, 19 deletions
diff --git a/libiberty/fdmatch.c b/libiberty/fdmatch.c index 7af039f5a2b..979c214d5d4 100644 --- a/libiberty/fdmatch.c +++ b/libiberty/fdmatch.c @@ -20,25 +20,19 @@ Boston, MA 02111-1307, USA. */ /* -NAME - - fdmatch -- see if two file descriptors refer to same file - -SYNOPSIS - - int fdmatch (int fd1, int fd2) - -DESCRIPTION - - Check to see if two open file descriptors refer to the same file. - This is useful, for example, when we have an open file descriptor - for an unnamed file, and the name of a file that we believe to - correspond to that fd. This can happen when we are exec'd with - an already open file (stdout for example) or from the SVR4 /proc - calls that return open file descriptors for mapped address spaces. - All we have to do is open the file by name and check the two file - descriptors for a match, which is done by comparing major&minor - device numbers and inode numbers. +@deftypefn Extension int fdmatch (int @var{fd1}, int @var{fd2}) + +Check to see if two open file descriptors refer to the same file. +This is useful, for example, when we have an open file descriptor for +an unnamed file, and the name of a file that we believe to correspond +to that fd. This can happen when we are exec'd with an already open +file (@code{stdout} for example) or from the SVR4 @file{/proc} calls +that return open file descriptors for mapped address spaces. All we +have to do is open the file by name and check the two file descriptors +for a match, which is done by comparing major and minor device numbers +and inode numbers. + +@end deftypefn BUGS |