From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Charles Wilson <cygwin@cwilson.fastmail.fm>, gdb-patches@sourceware.org
Subject: Re: RFA: ensure binary objects opened in binary mode
Date: Wed, 01 Mar 2006 22:11:00 -0000 [thread overview]
Message-ID: <44061BF9.4020403@redhat.com> (raw)
In-Reply-To: <uirr7kzsh.fsf@gnu.org>
Eli Zaretskii wrote:
>>Date: Wed, 22 Feb 2006 00:30:46 -0500
>>From: Charles Wilson <cygwin@cwilson.fastmail.fm>
>>CC: gdb-patches@sourceware.org
>>
>>Okay, I've attached two patches that hopefully address all the issues
>>raised in this thread.
>
>
> Thanks.
>
>
>>(1) for every file that #includes both defs.h AND <fcntl.h>, remove the
>><fcntl.h> inclusion.
>
>
> I'm not sure this is a good idea. What if tomorrow we remove fcntl.h
> from defs.h--do we go through all these files again and add it back?
> Why bother? fcntl.h should be idempotent, so including it several
> times does no real harm.
It's an extra file open and file read during make.
These things add up. gdb's include heirarchy is quite
tangled.
> I actually quite dislike source files that don't include standard
> headers because they are included in defs.h and its ilk. It makes me
> wonder how come foo.c uses something defined in bar.h, but there's no
> "#include <bar.h>" anywhere in sight.
A stylistic question, alas...
next prev parent reply other threads:[~2006-03-01 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 22:02 Charles Wilson
2006-02-17 23:41 ` Christopher Faylor
2006-02-18 10:45 ` Eli Zaretskii
2006-02-18 11:19 ` Mark Kettenis
2006-02-18 11:47 ` Eli Zaretskii
2006-02-18 11:55 ` Mark Kettenis
2006-02-22 5:52 ` Charles Wilson
2006-02-22 17:06 ` Christopher Faylor
2006-02-22 18:50 ` Eli Zaretskii
2006-02-22 21:55 ` Daniel Jacobowitz
2006-02-24 10:37 ` Charles Wilson
2006-02-24 11:44 ` Eli Zaretskii
2006-02-25 7:29 ` Charles Wilson
2006-03-01 22:11 ` Michael Snyder [this message]
2006-02-18 10:50 ` Eli Zaretskii
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=44061BF9.4020403@redhat.com \
--to=msnyder@redhat.com \
--cc=cygwin@cwilson.fastmail.fm \
--cc=eliz@gnu.org \
--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