From: Peter Graf <p.graf@itknet.de>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] What happened to feof & ftell?
Date: Thu, 01 Feb 2001 00:48:00 -0000 [thread overview]
Message-ID: <3.0.5.32.20010201095058.00914730@mail.becomsys.de> (raw)
In-Reply-To: <20010201065751.63430.qmail@web11101.mail.yahoo.com>
Martin van Veen wrote:
>like ftell and feof there is more stuff missing (which I wrote some
>weeks ago, but nobody responded). Fortunately, these functions are
>implemented, but only not mentioned in the stdio.h file. I patched
>stdio.h so that fileno and fdopen can be used. Patch is attached...
Thank you very much. You are right, at least ftell() is available in the
latest CVS snapshot. I've been using an older sourcetree. Thanks for the hint.
All the best
Peter
next prev parent reply other threads:[~2001-02-01 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 20:25 [ECOS] 68302 (or 680x0) port ? Lee Nipper
2001-01-29 4:36 ` AW: " Joerg Rapka
2001-01-31 6:44 ` [ECOS] What happened to feof & ftell? Peter Graf
2001-01-31 9:21 ` Jonathan Larmour
2001-01-31 22:57 ` Martin van Veen
2001-01-31 23:17 ` Jonathan Larmour
2001-02-01 0:48 ` Peter Graf [this message]
2001-07-25 17:58 ` [ECOS] 68302 (or 680x0) port ? wangwei
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=3.0.5.32.20010201095058.00914730@mail.becomsys.de \
--to=p.graf@itknet.de \
--cc=ecos-discuss@sourceware.cygnus.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).