Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Gary Benson <gbenson@redhat.com>,
	gdb-patches@sourceware.org,        Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH 1/3 v4] Introduce common/errors.h
Date: Fri, 25 Jul 2014 10:19:00 -0000	[thread overview]
Message-ID: <53D22E0C.8050603@redhat.com> (raw)
In-Reply-To: <21457.18385.59886.323894@ruffy.mtv.corp.google.com>

On 07/24/2014 06:52 PM, Doug Evans wrote:
> Pedro Alves writes:
>  > > +   You should have received a copy of the GNU General Public License
>  > > +   along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
>  > > +
>  > > +#include "config.h"
>  > 
>  > Sorry for the push back, but it's wrong to only include "config.h".
>  > We need to include gnulib's config.h everywhere too.  I think
>  > the best is to add a central common header that handles that
>  > detail first.
> 
> OTOH,
> just including "config.h" is a real common thing to do across all packages.
> I can imagine this coming up again and again.
> 
> IWBN if hacking on gdb didn't require special cases to standard
> programming paradigms wherever possible.
> Can we arrange for config.h to include gnulib's config.h?
> Or, another thought would be to have configure generate gdb-config.h
> (or some such) and then have src/gdb/config.h include both (and similarly
> for gdbserver - haven't looked at the details though).

I fail to see how changing any of that would substantially
improve things.  GDB has had defs.h for a long while, and people didn't
seem to be confused by that -- it's quite common to have a
project-specific global header to include.  If we have something
like that in common, then even if we have only a single config.h,
we'd naturally include that from the common common/ header anyway
instead of in addition to including the common/ file everywhere,
also including config.h directly everywhere too.

Thanks,
Pedro Alves


  parent reply	other threads:[~2014-07-25 10:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 12:51 [PATCH 0/3 v4] Common code cleanups (part 1) Gary Benson
2014-07-24 12:51 ` [PATCH 2/3 v4] Remove some GDBSERVER checks from linux-ptrace Gary Benson
2014-07-24 13:25   ` Pedro Alves
2014-07-24 14:09     ` Tom Tromey
2014-07-24 14:17       ` Pedro Alves
2014-07-24 14:13     ` [PATCH 2/3 v5] " Gary Benson
2014-07-24 14:25       ` Pedro Alves
2014-07-24 15:05         ` Gary Benson
2014-07-24 12:51 ` [PATCH 1/3 v4] Introduce common/errors.h Gary Benson
2014-07-24 13:24   ` Pedro Alves
2014-07-24 18:03     ` Doug Evans
2014-07-25  8:51       ` Gary Benson
2014-07-25 10:32         ` Pedro Alves
2014-07-25 11:38           ` Gary Benson
2014-07-25 12:13             ` Pedro Alves
2014-07-25 13:34               ` Gary Benson
2014-07-29 16:44               ` Doug Evans
2014-07-29 17:45                 ` Pedro Alves
2014-07-30  9:43                   ` Gary Benson
2014-07-25 10:19       ` Pedro Alves [this message]
2014-07-24 17:52   ` Doug Evans
2014-07-24 22:39     ` Doug Evans
2014-07-25  9:34     ` Gary Benson
2014-07-28 20:16       ` Doug Evans
2014-07-24 13:08 ` [PATCH 3/3 v4] Make gdbserver CORE_ADDR unsigned Gary Benson
2014-07-24 13:36   ` Pedro Alves
2014-07-24 14:07     ` 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=53D22E0C.8050603@redhat.com \
    --to=palves@redhat.com \
    --cc=dje@google.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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