Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] Remove spurious exceptions.h inclusions
Date: Wed, 08 Oct 2014 17:12:00 -0000	[thread overview]
Message-ID: <CADPb22QC=J=tpyMo_y3mMi22eQh5ub2E6LjGVDrrEOCTXgVPBw@mail.gmail.com> (raw)
In-Reply-To: <CADPb22RcwUGPEwGGc7hG=4R0KvRV9axKDbQ6Nu1PHys5Nk=t8A@mail.gmail.com>

On Wed, Oct 8, 2014 at 1:03 PM, Doug Evans <dje@google.com> wrote:
> On Mon, Sep 1, 2014 at 11:42 AM, Gary Benson <gbenson@redhat.com> wrote:
>> defs.h includes utils.h, and utils.h includes exceptions.h.  All GDB
>> .c files include defs.h as their first line, so no file other than
>> utils.h needs to include exceptions.h.  This commit removes all such
>> inclusions.
>>
>> Doug, I Cc'd you on this one as you asked me to avoid giant mechanical
>> ChangeLog entries but I couldn't figure out how I'd rewrite this one.
>
> For reference sake,
> I said that for two reasons:
> 1) to save you some typing
> 2) to keep the S/N ratio of the ChangeLog file from dropping, and in
> this case from dropping significantly.  Yikes!
>
>> gdb/ChangeLog:
>>
>>         * ada-lang.c: Do not include exceptions.h.
>>         * ada-valprint.c: Likewise.
>>         * amd64-tdep.c: Likewise.
>> [...]
>
> I realize one of the guidelines for changelogs is to document every
> file that's changed, but if we can agree that "All callers updated."
> can apply to all callers in all files, then I don't see why we
> couldn't be ok with something like the following for this case:
>
>         * All .c files: Do not include exceptions.h.
>
> Yeah, it's not pedantically correct, not all .c files were touched.
> But I can live with that given the alternative.

Actually, exceptions.c still includes exceptions.h.

I'd be ok with changing the above entry to "* Most .c files: Do not
include exceptions.h."

Plus, was not removing exceptions.h from exceptions.c an oversight?
[I can't remember if this was discussed in the thread.]


  reply	other threads:[~2014-10-08 17:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 15:42 [PATCH 0/3] Rationalize cleanups/exceptions includes Gary Benson
2014-09-01 15:42 ` [PATCH 3/3] Include common-exceptions.h in common-defs.h Gary Benson
2014-10-07 18:05   ` Pedro Alves
2014-09-01 15:42 ` [PATCH 1/3] Remove spurious exceptions.h inclusions Gary Benson
2014-10-07 18:04   ` Pedro Alves
2014-10-08 17:03   ` Doug Evans
2014-10-08 17:12     ` Doug Evans [this message]
2014-10-08 17:21       ` Pedro Alves
2014-10-08 17:24       ` Doug Evans
2014-10-09  9:43         ` Gary Benson
2014-10-09 11:43           ` Pedro Alves
2014-10-09  9:45     ` Gary Benson
2014-10-09 14:47       ` Doug Evans
2014-09-01 15:42 ` [PATCH 2/3] Include cleanups.h in common-defs.h Gary Benson
2014-10-07 18:05   ` Pedro Alves
2014-10-07  8:58 ` [PING PATCH 0/3] Rationalize cleanups/exceptions includes Gary Benson
2014-10-08  8:47 ` [PATCH " Gary Benson

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='CADPb22QC=J=tpyMo_y3mMi22eQh5ub2E6LjGVDrrEOCTXgVPBw@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gbenson@redhat.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