public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.edu>
To: "Dr. Volker Zell" <vzell@de.oracle.com>
Cc: e952508@anubis.ecci.ucr.ac.cr, Cygnus <gnu-win32@cygnus.com>
Subject: Re: I need help with telldir and seekdir
Date: Fri, 30 Oct 1998 00:03:00 -0000	[thread overview]
Message-ID: <9810292207.AA00625@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <8811-Wed28Oct1998162420+0100-vzell@de.oracle.com>

"Dr. Volker Zell" <vzell@de.oracle.com> writes:
> 
> Hi
> 
> >I'm trying to port code from unix to win32 with cygwin32.  Everything
> >worked right until a tried to compile a file wich included "dirent.h"
> >and tried to use seekdir and telldir.
> >    Can somebody tellme either  if  those functions are available in
> >other  header file, or  if i should implement them, and if that's the
> >case, how can i do it.

seekdir and telldir are not part of POSIX (and obviously not part of the
ANSI C library), and any code using these (presumably expecting a BSD 4.3 
environment) is inherently non-portable to POSIX systems.

More often than not, the combination of telldir and seekdir is simply used 
as a replacement for rewinddir, which *is* POSIX and is part of cygwin. 

Older versions of mc (eg,. 4.1.35) didn't use these, so must be recent
addition, and I would assume quite easy to work around.

Regards,
Mumit

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1998-10-30  0:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-28 11:32 Dr. Volker Zell
1998-10-30  0:03 ` Mumit Khan [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-10-30  5:08 Earnie Boyd
1998-10-30  0:03 N8TM
1998-10-28  4:06 Earnie Boyd
1998-10-27  6:15 ARNULFO RODRIGUEZ ZAMORA
1998-10-29 11:20 ` tjoen

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=9810292207.AA00625@modi.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --cc=e952508@anubis.ecci.ucr.ac.cr \
    --cc=gnu-win32@cygnus.com \
    --cc=vzell@de.oracle.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).