From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][gdb/testsuite] Support .debug_aranges in dwarf assembly
Date: Fri, 27 Aug 2021 07:35:17 -0600 [thread overview]
Message-ID: <87eeafovsa.fsf@tromey.com> (raw)
In-Reply-To: <20210826115625.GA22715@delia> (Tom de Vries via Gdb-patches's message of "Thu, 26 Aug 2021 13:56:26 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> + # arange [-c <comment>] [<segment selector>] <start> <length>
Tom> + # -- adds an address range.
I wonder if there's a way to make this more tcl-ish, say by rearranging
the order of arguments so that things can be defaulted. I think the
"args"-parsing style should normally be a last resort.
Tom> + proc arange { args } {
This is nested in 'aranges', but that's weird style in Tcl.
It redefines the proc every time 'aranges' is invoked.
I think it's better to just namespace scope this.
Tom
next prev parent reply other threads:[~2021-08-27 13:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 11:56 Tom de Vries
2021-08-27 13:35 ` Tom Tromey [this message]
2021-08-27 14:39 ` Tom de Vries
2021-08-27 15:09 ` Simon Marchi
2021-08-27 16:11 ` Keith Seitz
2021-08-27 16:14 ` Tom Tromey
2021-08-27 17:03 ` Simon Marchi
2021-08-27 17:10 ` Tom Tromey
2021-08-27 17:23 ` Simon Marchi
2021-08-28 15:31 ` Tom de Vries
2021-08-28 20:29 ` Simon Marchi
2021-08-28 21:28 ` Simon Marchi
2021-08-29 15:31 ` Tom de Vries
2021-08-29 19:54 ` Simon Marchi
2021-08-29 21:11 ` Tom de Vries
2021-08-30 8:35 ` Tom de Vries
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=87eeafovsa.fsf@tromey.com \
--to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).