From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com, eliz@gnu.org
Cc: cagney@redhat.com
Subject: Re: [5.2.1] quiet warnings for gdbreplay.c
Date: Sat, 21 Jun 2003 18:07:00 -0000 [thread overview]
Message-ID: <20030621180738.GA10044@nevyn.them.org> (raw)
In-Reply-To: <20030621174002.GB14161@nevyn.them.org>
On Sat, Jun 21, 2003 at 01:40:02PM -0400, Daniel Jacobowitz wrote:
> On Tue, Jul 09, 2002 at 05:13:54PM -0400, Andrew Cagney wrote:
> > >Then do we want a separate gdb/gdbint/ directory for this? I strongly
> > >prefer that headers shared between GDB and other directories be clearly
> > >marked and separated. That'd give me a place to move
> > >gdb_proc_service.h, too.
> >
> > I think it would be easier to just clarify the guidelines for
> > ``gdb_XXXX.h'' files - that they be independant as they are included by
> > GDB and friends.
>
> This has been on my TODO list for almost a year... Andrew, how's this?
Hi Eli,
Since it seems I captured Andrew's and my intent correctly, is this
documentation patch OK?
> 2003-06-21 Daniel Jacobowitz <drow@mvista.com>
>
> * gdbint.texinfo (Coding): Clarify use of gdb_XXX.h headers.
>
> Index: gdbint.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
> retrieving revision 1.154
> diff -u -p -r1.154 gdbint.texinfo
> --- gdbint.texinfo 19 Jun 2003 15:04:05 -0000 1.154
> +++ gdbint.texinfo 21 Jun 2003 17:38:47 -0000
> @@ -5191,7 +5191,11 @@ of @value{GDBN}) must be added to @file{
>
> When @value{GDBN} has a local version of a system header file (ex
> @file{string.h}) the file name based on the POSIX header prefixed with
> -@file{gdb_} (@file{gdb_string.h}).
> +@file{gdb_} (@file{gdb_string.h}). These headers should be relatively
> +independent: they should use only macros defined by @file{configure},
> +the compiler, or the host; they should include only system headers; they
> +should refer only to system types. They may be shared between multiple
> +programs, e.g.@: @value{GDBN} and @sc{gdbserver}.
>
> For other files @samp{-} is used as the separator.
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-21 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 20:47 David O'Brien
2002-06-28 9:12 ` Andrew Cagney
2002-06-28 11:08 ` Daniel Jacobowitz
2002-06-28 11:38 ` David O'Brien
2002-06-28 14:20 ` Andrew Cagney
2002-06-28 14:39 ` Daniel Jacobowitz
2002-07-09 14:15 ` Andrew Cagney
2003-06-21 17:40 ` Daniel Jacobowitz
2003-06-21 17:54 ` Andrew Cagney
2003-06-21 18:07 ` Daniel Jacobowitz [this message]
2003-06-22 3:25 ` 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=20030621180738.GA10044@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.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