From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] $thread convenience variable
Date: Mon, 14 Jun 2010 18:36:00 -0000 [thread overview]
Message-ID: <m3pqztzck2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C158675.9090001@codesourcery.com> (Stan Shebs's message of "Sun, 13 Jun 2010 18:31:33 -0700")
>>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:
Stan> Although the original request was for "$thread", it might be better to
Stan> make it "$_thread" instead, so as not to interfere with possible use
Stan> in existing scripts. But I'll only change it if I get enough votes in
Stan> favor. :-)
I have a vague memory that the last time this came up we decided that
all new built-in convenience variables would start with "_", or
something like that.
Tom
next prev parent reply other threads:[~2010-06-14 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 1:31 Stan Shebs
2010-06-14 3:00 ` Eli Zaretskii
2010-06-14 9:14 ` Pierre Muller
2010-06-14 18:36 ` Tom Tromey [this message]
2010-06-18 17:46 ` Stan Shebs
2010-06-18 17:58 ` Pedro Alves
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=m3pqztzck2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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