From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] ARI fix: Replace sys/wait.h by gdb_wait.h in linux-fork.c
Date: Mon, 08 Oct 2007 07:44:00 -0000 [thread overview]
Message-ID: <005901c8097f$0bc90880$235b1980$@u-strasbg.fr> (raw)
In-Reply-To: <20071005200154.GC3570@adacore.com>
Thanks, committed.
Pierre Muller
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Joel Brobecker
> Sent: Friday, October 05, 2007 10:02 PM
> To: Pierre Muller
> Cc: gdb-patches@sourceware.org
> Subject: Re: [RFC] ARI fix: Replace sys/wait.h by gdb_wait.h in linux-
> fork.c
>
> Hello Pascal,
>
> > 2007-10-04 Pierre Muller <muller@ics.u-strasbg.fr>
> >
> > * linux-fork.c: ARI fix: include "gdb_wait.h" instead of
> <sys/wait.h>.
> > Makefile.in (linux-fork.o): Add gdb_wait.h dependency.
>
> This patch is OK. I ran it against the regression testsuite just
> to double-check.
>
> > 2) Are there rules about the order in which
> > the different headers are listed?
>
> There are some rules, like "defs.h" should always be included first.
>
> Usually speaking, in C, I always try to write include files in a way
> that the order in which I include them is not important. To the best
> or my knowledge, GDB also tries to accomplish that.
>
> > I did put the gdb_wait.h together with other local
> > headers, which seems to be a common practice in GDB sources.
>
> That's perfect.
>
> > 3) I also updated the dependency of linux-fork.o in
> > Makefile.in, but stumbled on the same problem:
> > is there some preferred ordering of the dependency list?
>
> I don't know if there is a prefered ordering. Definitely, the ordering
> in the makefile does not matter, but I try to maintain the dependency
> list in the same order as the includes. It makes it a lot simpler to
> double-check that the list is still accurate. So your change is great.
>
> > trying to reduce ARIs...
>
> Thanks!
>
> --
> Joel
prev parent reply other threads:[~2007-10-08 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 7:42 Pierre Muller
2007-10-05 20:02 ` Joel Brobecker
2007-10-08 7:44 ` Pierre Muller [this message]
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='005901c8097f$0bc90880$235b1980$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.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