From: Andrew Cagney <ac131313@cygnus.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Wrappers again.
Date: Tue, 30 Oct 2001 18:10:00 -0000 [thread overview]
Message-ID: <3BDF5D43.6050809@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0110252354180.23990-100000@makita.cygnus.com>
> Hi,
>
> Resubmitting this for (dis?)aprroval.
>
> Keith
>
> ---------- Forwarded message ----------
> Date: Fri, 19 Oct 2001 11:41:43 -0700 (PDT)
> From: Keith Seitz <keiths@makita.cygnus.com>
> To: gdb-patches@sources.redhat.com
> Subject: Re: [RFA] More wrappers in varobj
>
> Sorry for the delay. I got a little caught up in debugging some
> other stuff...
>
> On Mon, 15 Oct 2001, Andrew Cagney wrote:
>
>
>> have a look at breakpoint.c:gdb_breakpoint for a more robust / current
>> way of implementing these wrappers.
>
>
> Is this better?
Yes, much better - no casts. Thanks for the effort.
> Slightly off-topic: We are going to be calling externally visible
> functions something like "gdb_FOO", right? Example: gdb_breakpoint and
> gdb_breakpoint_query. How are we going to name internal functions? Leading
> "_" or something?
>
> I ask because I don't really want to have this patch introduce
> internal variations of gdb functions into the "libgdb" namespace.
Good question, I don't know. A leading ``_'' isn't valid though.
Andrew
next parent reply other threads:[~2001-10-30 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.33.0110252354180.23990-100000@makita.cygnus.com>
2001-10-30 18:10 ` Andrew Cagney [this message]
2001-10-30 19:16 ` Keith Seitz
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=3BDF5D43.6050809@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@cygnus.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