my e-mail address [email protected]
background :
Graduated engineer in 2001 and working the railway industry. I support engineering tools based on Tcl/Tk since several years (refer to the 2009 Tcl conf in Strasbourg)
interests :
My concern is to put forward the Tcl/Tk language to make it less confidential and more widely used as it is a fabulous language for tools in the engineering area.
HE 2022-04-09: Hello Adrien, I see you are changing a lot of code inside this wiki and I ask myself why you are doing it? What is the reason to change it?
What I see is that you change foreach with lassign without need, even breaking code in some cases. 'foreach' works well even with Tcl 8.6 to assign list elements to variables. On the other hand Tcl 8.4 doesn't support 'lassign' native. And some code claims to run with Tcl 8.4.
You also change "trace variable" to "trace add variable". Again, the old way still works today.
If your purpose is to make the code using modern Tcl commands, than it is interesting that you not change other parts like using 'eq' for comparing strings in expression. There are examples near by the changed code. That leads me to the conclusion that you changed the code with some kind of pattern search without looking inside the code to assure that it really runs as expected.
This conclusion is supported by the fact that you not documented the change on the edited pages. Not as comment somewhere on the page nor with a comment inside the code. That means you change code silent and it looks on the page like as the original editor has written the code like that. That is not the nice way, from my point of view.
If your purpose is to take care about making code modern, why you not rework the scripts completely and add an updated version with a meaningful comment in addition to the page.
We are not speaking about syntax errors, typos or bug fixes which everyone is glad if one takes care about.
Even if Tcl 8.4 is no longer a maintained native Tcl version, you should also kept in mind that there are still 8.4 syntax out there. For example jTcl is still using Tcl 8.4 syntax.
I can confirm that "it is a fabulous language for tools in the engineering area.". But, one of its strength is, that Tcl is stable in syntax for such a long time. That mean you can keep the Tcl installation up to date without breaking running scripts. One of my Tcl programs runs since 2006 without need of a change. And that is what I expect as an engineer from my tools that I not have to maintain them regularly because commands or syntax have changed. And I believe, that this should be shown also in this wiki to convince other to use our preferred programming language.