From: Eli Zaretskii <eliz@gnu.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [TUI] correctly display windows source files
Date: Tue, 10 Oct 2006 21:24:00 -0000 [thread overview]
Message-ID: <ufydvkgoa.fsf@gnu.org> (raw)
In-Reply-To: <452B9EB9.4040709@st.com> (message from Denis PILAT on Tue, 10 Oct 2006 15:23:05 +0200)
> Date: Tue, 10 Oct 2006 15:23:05 +0200
> From: Denis PILAT <denis.pilat@st.com>
> Cc: gdb-patches@sourceware.org
>
> About your remark,
> I've tried to ungetc(EOF) and I did not get any problem, after
> ungetc(EOF) the next call to fgetc is still EOF.
That could be so, but I'd prefer that our code didn't do anything that
could fail, even theoretically. We shouldn't call functions with
arguments that invoke undefined or uncertain behavior.
It should be a simple matter of adding a test for EOF.
next prev parent reply other threads:[~2006-10-10 21:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 15:25 Denis PILAT
2006-10-09 18:01 ` Mark Kettenis
2006-10-09 19:28 ` Eli Zaretskii
2006-10-10 13:23 ` Denis PILAT
2006-10-10 15:08 ` '\r' only end-of-line Denis PILAT
2006-10-10 21:34 ` Eli Zaretskii
2006-10-11 10:08 ` Denis PILAT
2006-10-11 13:33 ` Daniel Jacobowitz
2006-10-11 13:57 ` Andrew STUBBS
2006-10-11 14:01 ` Daniel Jacobowitz
2006-10-11 14:44 ` Andrew STUBBS
2006-10-11 15:05 ` Daniel Jacobowitz
2006-10-11 17:47 ` Eli Zaretskii
2006-10-11 17:36 ` Eli Zaretskii
2006-10-16 8:51 ` Denis PILAT
2006-10-10 21:24 ` Eli Zaretskii [this message]
2006-10-11 8:02 ` [TUI] correctly display windows source files Denis PILAT
2006-10-11 8:39 ` Eli Zaretskii
2006-10-11 11:23 ` Frederic RISS
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=ufydvkgoa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=denis.pilat@st.com \
--cc=gdb-patches@sourceware.org \
/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