|
From: EricT <tw...@gm...> - 2025-10-21 17:40:57
|
Jan:
Thanks for the support and looking at a knob.
This is exactly the approach I was hoping for - an interpreter-bound knob
for opt-in in 9.1, with a path to default in 10. I really appreciate you
taking this on.
I'm working on expanding the test suite with comprehensive edge cases to
ensure the implementation is solid. I'll have an updated subexpr.test file
ready soon that can be dropped into the test directory.
Regarding subst and $(, I'd be interested to hear your thoughts on any
options that might help there.
Eric
On Tue, Oct 21, 2025 at 6:42 AM Jan Nijtmans <jan...@gm...> wrote:
> Op ma 20 okt 2025 om 22:59 schreef EricT:
>
>> There is one other edge case with $(expr): the subst command currently treats it as variable substitution. This means:
>> subst -nocommands {$(expr)} # Doesn't work - still substitutessubst -novariables {$(expr)} # Works - suppresses substitution
>>
>>
> Good catch ! How about adding a "subst -noexpr"? It works almost the
> same
> as "subst -novariables", but whether it substitutes depends on whether '$'
> is
> followed by '(' or not. That shouldn't be too difficult to implement.
>
> Regards,
> Jan Nijtmans
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core
>
|