Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Harald Oehlmann <wortkarg3@yahoo.com>
Newsgroups: comp.lang.tcl
Subject: Re: Show argument values in bgerror
Date: Wed, 18 Sep 2024 13:50:21 +0200
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <vceept$3vk7h$4@dont-email.me>
References: <b42edc7a9bab2a468f2694eda7a2df32@www.novabbs.com>
 <vcdukq$3vk7h$2@dont-email.me>
 <6124e3922c51988d84ad3d7945d8e5bd@www.novabbs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 18 Sep 2024 13:50:22 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="80665d74369c5ed68fd8bfbd0399f919";
	logging-data="4182257"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19NgmDnDNXPNEUaYub0+JRr"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:/PRs2c0mhhH/b/f2s+DbswZAXg8=
Content-Language: en-GB
In-Reply-To: <6124e3922c51988d84ad3d7945d8e5bd@www.novabbs.com>
Bytes: 1672

Am 18.09.2024 um 12:23 schrieb alexandru:
> As you can see, upstream procedure calls are printed with dollar sign,
> unevaluated values.
> In more complex nested calls, the information about arguments gets lost
> and errorInfo does not show which argument values were used.

That is exactly what "info errorstack" is about.
See, that the "a" is substituted as argument "v".
It only works for items putting something on the call stack, so, it will 
not help for your eval example. But you get the values supplied to all 
procedures...

Take care,
Harald