Menu
▾
▴
Re: [TCLCORE] [Ext] Prototype Implementation of TIP 672 - $(expr) Syntax
|
From: Florent M. <flo...@gm...> - 2025-10-21 17:35:10
|
Jan,
Mathematical expression shorthand has been a long term debate, but
consensus has never emerged on this subject.
But, the fact is that the $(...) syntax is breaking code, but the {=}
syntax is not.
Moreover, the concept of word prefix, to modulate interpretation of
words, is a room for many improvements, in a backward compatible way.
One of this improvement is the multiline or inline comments prefix {#}.
So, why prefer a syntax that is breaking code, when it exits an
alternative syntax that is not breaking any code ?
Is it to make people to go far away from Tcl ?
Le 21/10/2025 à 15:28, Jan Nijtmans a écrit :
> Op di 21 okt 2025 om 14:53 schreef EricT:
>> The main reason for the $(...) syntax is to encourage the use of safer, compiled, expression code. Since it would also be easier to read and write, users would gravitate to its use and automatically get the benefit of braced expr code.
> I think the best way forward is simply to go for the $(...) syntax, as
> proposed now in the TIP. Just make it an opt-in feature in Tcl 9.1, and
> deprecate the use of empty-string array variables in $-substitutions
> (but keep everything as-is for 'set'). I'll try to implement some
> interpreter-bound knob (I think that's better than a global knob)
>
> That opens the way to make this behavior the default in Tcl 10....
>
> Thanks!
> Jan Nijtmans
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core
--
------------------------------------------------------------------------
*Florent MERLET*
/4 rue Johann Strauss
Logement 7
86180 BUXEROLLES/
------------------------------------------------------------------------
*Mél.* : /flo...@gm.../
*Tél.* : /06 70 00 63 48/
|
