public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>,
	Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [pushed 1/4] [gdb/testsuite] Don't use string cat in gdb.dwarf2/dw2-abs-hi-pc.exp
Date: Wed, 26 Apr 2023 08:34:44 +0200	[thread overview]
Message-ID: <97d43c1a-45d2-6ec5-001f-e20709342ce3@suse.de> (raw)
In-Reply-To: <878refyfgn.fsf@tromey.com>

On 4/25/23 20:38, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Tom> +set sources [lmap i $sources { subst $srcdir/$subdir/$i }]
> 
> Tom> My working set of tcl is a bit random, so I don't know what idiomatic
> Tom> is and what not.
> 
> No worries, Tcl expertise isn't exactly a headline skill.
> 
> Tom> I agree that subst is neater since it needs less quoting.
> 
> It probably has to be { subst { $srcdir/$subdir/$i } }
> since otherwise there will be a second substitution if, say, the srcdir
> has a $ or [] in it.

OK, let's try an example.

We currently have this style:
...
set b d
set l { a $b }
set res [lmap v $l { expr {"$v/c"} }]
foreach v $res {
     puts "V: $v"
}
...
which does:
...
V: a/c
V: $b/c
...

Then with subst we have the same:
...
set res [lmap v $l { subst {$v/c} }]
...
unless we forget the quoting:
...
set res [lmap v $l { subst $v/c }]
...
which gets us instead:
...
V: a/c
V: d/c
...

Hmm, in that case I think subst is the worse choice.  With expr, things 
either parse or not, and if it parses you get the right result.

FWIW, reading a bit more about it I get the impression also set is 
idiomatic, so I came up with this:
...
set res [lmap v $l { set v $v/c ; set v }]
...
which works as well.

Thanks,
- Tom


  reply	other threads:[~2023-04-26  6:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 12:48 Tom de Vries
2023-04-24 12:48 ` [pushed 2/4] [gdb/testsuite] Add basic lmap for tcl < 8.6 Tom de Vries
2023-04-24 12:48 ` [pushed 3/4] [gdb/testsuite] Fix gdb.multi/multi-arch.exp on powerpc64le Tom de Vries
2023-04-24 12:48 ` [pushed 4/4] [gdb/testsuite] Require GCC >= 5.x.x in gdb.base/utf8-identifiers.exp Tom de Vries
2023-04-24 16:48 ` [pushed 1/4] [gdb/testsuite] Don't use string cat in gdb.dwarf2/dw2-abs-hi-pc.exp Tom Tromey
2023-04-24 20:22   ` Tom de Vries
2023-04-25 18:38     ` Tom Tromey
2023-04-26  6:34       ` Tom de Vries [this message]
2023-04-26  7:08         ` Andreas Schwab
2023-05-02 15:38           ` Tom de Vries
2023-04-27 13:39         ` Tom Tromey
2023-05-02 15:40           ` 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=97d43c1a-45d2-6ec5-001f-e20709342ce3@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).