|
From: Rolf A. <tcl...@po...> - 2025-10-22 14:12:58
|
Florent Merlet writes: > So, everybody in the core team agree with the implementation of a new > math-Expression substitution as a memlink command into the procedure in > charge of variable name substitution ? It isn't necessary at all that everybody in the core team agrees with a proposal to have the implementation in a branch of the repository. It is just one step which helps to play around what is proposed and how it is implemented and to eventually have an informed option. Having a branch with an implementation isn't a preliminary decision at all. Speaking for me I'm still in the listening and considering phase. No surprise that there seems consent that the [expr ...] syntax is somewhat awkward. Everything proposed to far has a (more or less minor) drawback. Perhaps there is no solution without drawback and we will have to pick one. Or none will be picked and things stay as it is until the next round of this disussion start ... rolf > > Le mer. 22 oct. 2025, 14:07, EricT <two...@pu...> a écrit : > >> Hi everyone, >> >> I wanted to update you on the status of TIP 672 (expression substitution >> syntax). >> >> The prototype implementation is now complete and available at: >> https://github.com/rocketship88/tcl-tip-672-prototype >> >> The implementation has been parameterized to support both discussed >> approaches with a simple compile-time flag: >> - Mode 1: $(expr) syntax >> - Mode 2: $=(expr) or $^(expr) - configurable character >> >> Key features: >> - Comprehensive test suite (82 tests covering edge cases) >> - Minimal code changes (~100 lines) >> - Clean integration with existing parser >> - Full Tcl test suite passes (only 3 expected differences) >> >> There is one known issue: a minor memory leak in the synthetic command >> strings that will need attention during integration. >> >> At this point, I need a sponsor to upload the code to a TIP branch on >> Fossil so the core team can review and decide whether to adopt the TIP and, >> if so, which syntax to use. I'm available for any collaborative work, >> questions, or modifications needed. >> >> I'm grateful for all the feedback and support from the community. I look >> forward to the next steps in the process. >> >> Best regards, >> Eric >> >> _______________________________________________ >> Tcl-Core mailing list >> Tcl...@pu... >> https://lists.sourceforge.net/lists/listinfo/tcl-core >> > > _______________________________________________ > Tcl-Core mailing list > Tcl...@pu... > https://lists.sourceforge.net/lists/listinfo/tcl-core |