From: Frederic RISS <frederic.riss@st.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New threadnum command for breakpoints
Date: Thu, 31 Aug 2006 07:23:00 -0000 [thread overview]
Message-ID: <1156941204.3429.252.camel@crx549.cro.st.com> (raw)
In-Reply-To: <1155716115.28300.526.camel@crx549.cro.st.com>
ping?
> > > If you want it to be the last stopped thread, which seems reasonable,
> > > is there a better name we could give it? Or is $_gdb_thread
> > > sufficiently clear?
> >
> > I'm not sure. The name itself looks fine to me but, speaking as a user,
> > I find the leading '_' a bit strange. It seems to imply something about
> > the variable, but it's not clear what.
> > If it was a convention and all variables would share the same prefix,
> > then it wouldn't feel so strange. On the other side if we want to use a
> > common convention we've got to start somewhere.
> > Anyway that's just a personal feeling, and really no big deal, maybe
> > others could share their opinion?
>
> Nobody seems to care. How about we go on with the current patch (modulo
> the doco fix that Eli requested)?
>
> Current patch:
> http://sourceware.org/ml/gdb-patches/2006-07/msg00434.html
>
> Fred.
>
next prev parent reply other threads:[~2006-08-30 12:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 13:44 Frederic RISS
2006-07-28 14:03 ` Andreas Schwab
2006-07-28 14:13 ` Daniel Jacobowitz
2006-07-28 14:20 ` Andreas Schwab
2006-07-28 14:59 ` Frederic RISS
2006-07-28 15:14 ` Daniel Jacobowitz
2006-07-31 8:32 ` Frederic RISS
2006-07-31 12:53 ` Daniel Jacobowitz
2006-07-31 14:00 ` Frederic RISS
2006-07-31 20:07 ` Frédéric Riss
2006-07-31 20:14 ` Eli Zaretskii
2006-08-08 18:22 ` Daniel Jacobowitz
2006-08-08 19:43 ` Frédéric Riss
2006-08-16 14:15 ` Frederic RISS
2006-08-31 7:23 ` Frederic RISS [this message]
2006-07-28 14:28 ` Frederic RISS
2006-07-28 14:30 ` Frederic RISS
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=1156941204.3429.252.camel@crx549.cro.st.com \
--to=frederic.riss@st.com \
--cc=drow@false.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