Tcl/Tk 9.1
- ID
- 30471
- Status
- summarized
- Published
- 30 Sep 2026, 1:13 AM
- Fetched
- 01 Oct 2026, 3:20 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://www.tcl-lang.org/software/tcltk/9.1.html
- Source URL
- https://hnrss.org/best
Summary
- Score
- 4.0
- Created
- 01 Oct 2026, 3:21 AM
- Tags
- Audience
- developers
What happened
Tcl/Tk 9.1.0 was released on Sep 29, 2026 as the development line continuing on top of 9.0. Tcl gains a unicode normalization command, a timer command with a monotonic microsecond clock, lfilter, interp set, new subst (-backslashes/-commands/-variables) and switch (-integer) options, C99 math routines exposed as expr functions, and extended 64-bit size support; Tk adds accessibility screen-reader support, initial bidirectional/RTL text, a ttk::toggleswitch widget, tk attribtable, and rotated label text. The notable break: applications must now call an initialization routine, Tcl_FindExecutable or TclZipfs_AppHook, and macOS case-insensitive filesystem paths plus reworked Windows auto_execok/exec search change how scripts and binaries are located.
Why it matters
If you maintain Tcl/Tk tooling — internal GUI utilities, test harnesses, launcher scripts — a drop-in upgrade to 9.1.0 can fail at startup until you add the now-mandatory Tcl_FindExecutable or TclZipfs_AppHook call, and the reworked macOS path case handling and Windows auto_execok/exec search can silently change which binary or script gets picked. If Tcl/Tk is not in your stack, nothing here changes what you ship this week; the 293-point, 138-comment thread is mostly long-tail-language discussion rather than a decision point. No Malaysian or Southeast Asian angle is stated in the release notes.
Discussion angle
Take the one concrete break — the required Tcl_FindExecutable / TclZipfs_AppHook init call — and ask who in the room still ships Tcl/Tk tooling and whether the macOS case-insensitive path and Windows exec search changes would break their existing launchers.