Triage of 818 open and Pending Bug tickets of Tcl with no comment or check-in from me on 2026-10-16 (in Tcl's workflow Pending means "resolved, waiting for confirmation"). Reproduced on Linux (main 9.1 tip, 9.0 tip, 8.7b1, 8.6 tip, 8.5, 8.4 and old releases), on FreeBSD, NetBSD, OpenBSD and OpenIndiana VMs for platform tickets, and on a Windows 11 VM. Rows marked patch link to a prototype patch (287 in all, in tcl-triage/prototypes). Updated 2026-11-11: the emoji before each ticket id shows its progress.
NOT-A-BUG (TIP 732: embedding apps must call Tcl_FindExecutable or TclZipfs_AppHook; reporter confirmed that adding TclZipfs_AppHook fixes it)
info library); with TclZipfs_AppHook both give //zipfs:/lib/tcl/tcl_library. The wish symptom from the description is not reproducible (Jan, 9.1.0).
NOT-A-BUG (it is the normal inline result for a failed conversion; accepting NaN is a feature request, TIP 520)
scan NaN %f → {}, scan NaN %f fl → 0 with fl unset. For comparison scan x %f → {}, scan Nax %f → {}, scan "5 xyz" "%d %f" → {5 {}}, scan "" %f → `` (end of input).
goto done). In inline mode each specifier that was not converted gets an empty element; with variables the count 0 is returned. Both forms say "0 conversions", so they agree. The empty element is used for every failed conversion, not only NaN.
NOT-A-BUG (missing API, RFE). The behaviour matches the current design.
\ before * escapes it; C:\\foo\\* is C:\foo\*) — confirm on Windows with wi…NOT-A-BUG (documented: glob.n "WINDOWS PORTABILITY ISSUES" says \ before * escapes it; C:\\foo\\* is C:\foo\*) — confirm on Windows with win/7eb6b3a53f.tcl
\* is a literal *. apnadkarni's 2026-05-31 analysis is correct.
\* is a literal asterisk. Use forward slashes or -directory {C:\WINDOWS} *. Propose closing as Works as Designed.
NOT-A-BUG (the porting guides are community wiki pages; the API is documented in doc/CrtObjCmd.3, which covers Tcl_CreateObjCommand2/Tcl_ObjCmdProc2)
NOT-A-BUG (obsolete: MemoryModule was never merged — TIP 709 was Rejected 1/5/0; branch tip-709 closed 2025-12-18, last check-in 6b3706cdb7 2025-11-30; no MemoryModule code in main/9.0/8.6)
NOT-A-BUG (long-standing, deliberate behaviour shared with lsort -index; a change would be a feature request / TIP)
lsearch -index 0 {{} one two three} one → element 0 missing from sublist "". lsort -index 0 {{} b a} gives the same error (both use SelectObjFromSublist), and lsort -index has done so since 8.4.
NOT-A-BUG (design/RFE: layout of //zipfs:/app and default auto_path); unchanged on main
zipfs mkimg offset problem discussed here belongs to fc65ff1b66 or a new ticket. Propose changing type to RFE.
NOT-A-BUG (works as documented; RFE at most)
sub/d.tcl two levels below the auto_path entry: in a safe::interpCreate child package require of the one-level package works and the two-level one fails with "permission denied" on main, 9.0.5 and 8.6.18.
http::meta is now an alias of http::responseHeaders, whose names are documented as conv…NOT-A-BUG (documented incompatible change of http 2.10: http::meta is now an alias of http::responseHeaders, whose names are documented as converted to lower case)
set key [string tolower $key]); doc/http.n responseHeaders/meta
NOT-A-BUG (transforms work on bytes by design)
chan push stdout transform receives puts "❽" as the 4 bytes e2 9d bd 0a (the channel's utf-8 encoding), and encoding convertfrom utf-8 gives back the character.
fconfigure ... -encoding utf-8 in initialize does not change that.
::tk::ConsoleOutput stdout [encoding convertfrom [fconfigure $chan -encoding] $data] (or fix the channel's encoding to utf-8 and always decode as utf-8). Propose closing as Works as designed.
NOT-A-BUG (expected Unix signal semantics; Tcl has no job control)
exec sleep 30 & child is in tclsh's process group with no signals ignored; SIGINT to the group (what Ctrl+C on the terminal does) kills it. exit/Ctrl+D send no signal, so the child survives
& without job control; interactive shells use a separate process group)
exec ... & would be a behaviour change needing discussion)
NOT-A-BUG (long-standing, intentional and tested behaviour: append-7.5 "append var does not trigger read trace" since 2008, appendComp-7.9, trace-3.1/3.2 expect no read trace on append)
hello bar) everywhere; Ashok's 2026-05-24 output also shows the reported behaviour, he just did not see it as a problem
append on a Tcl_LinkVar string variable uses the stale Tcl value and overwrites a newer C value (checked with testlink: C side "xyz", append string Z gives "abcZ").
info script returns the path exactly as passed to source/tclsh; same since 8.4)NOT-A-BUG (info script returns the path exactly as passed to source/tclsh; same since 8.4)
tclsh t13d/sub/me.tcl does cd then file normalize [info script] → wrong path (found=0) on all
info script returns the name of the file as given; a relative name becomes invalid after cd. Returning absolute paths would change long-standing behaviour (and the TIP 280 info frame file names)
read $chan 5 returns it in the -data key of the error optio…NOT-A-BUG (works as documented since TIP 653, 9.0.0): "AB" is not lost. The failing read $chan 5 returns it in the -data key of the error options dictionary (catch {read $chan 5} m opts; dict get $opts -data → AB), and the channel stays at the invalid byte, so the next read with -profile replace correctly starts there.
-data checked on main and 9.0. 8.6 has no profiles.
-data (TIP 653, d7fce1ea20/9a94125824, 2023-11); documented in doc/chan.n (read, ENCODING ERROR EXAMPLES).
-data key of the error options, catch {read $chan 5} m opts; dict get $opts -data gives "AB". The next read starts at the invalid byte, as doc/chan.n describes. Suggest closing as Works as Expected.
read that hits an encoding er…NOT-A-BUG (resolved by TIP 653 in 9.0.0): the second option the ticket asks for is what was implemented. A blocking read that hits an encoding error returns the data decoded so far ("hello") in the -data key of the error options, and the position is left at the invalid byte (tell = 5). This is documented in doc/chan.n.
-data hello (main, 9.0); -profile replace then reads "U+FFFD world" (the replacement character, then "world").
-data key, TIP 653, d7fce1ea20, 2023-11-06).
-data key of the error options, and the position stays at the invalid byte, so nothing is lost on unseekable channels either (see doc/chan.n, ENCODING ERROR EXAMPLES). Suggest closing.
NOT-A-BUG (joinable threads work on Windows through the generic/tclThreadJoin.c emulation; the misleading doc sentence is gone in 9.0/main, 9183ace241, 2025-09-26, but still in 8.6 doc/Thread.3:108). The reporter's native-HANDLE rewrite is in branch windows-thread-join (231c699c87 .. 9c9f39bc30, last change 2023-05-03), not merged.
NOT-A-BUG (design decision of TIP #484; still unregistered: main and 9.0 register only bytecode, cmdName, dict, double, list, procbody, regexp, string in generic/tclObj.c; 8.6 registers "int"). An RFE / TIP matter
-all adds inherited methods but still lists only exported ones, and -private adds the non-exported ones. To get every m…NOT-A-BUG (documented): -all adds inherited methods but still lists only exported ones, and -private adds the non-exported ones. To get every method, use -all -private (<cloned> destroy eval unknown variable varname for oo::object). doc/info.n describes this and also notes that the name -private clashes with true private methods (TIP 500, see -scope).
-all means "include superclasses/mixins", -private means "include non-exported methods". Use info class methods ::oo::object -all -private to get all of them, or -scope (Tcl 9). Suggest closing as Works as Expected.
set/namespace resolve to the namespace's own commands)NOT-A-BUG (command resolution inside the namespace: the script's set/namespace resolve to the namespace's own commands)
namespace which set is ::tcl::array::set (= array set), in ::tcl::dict it is ::tcl::dict::set; in ::oo::InfoObject, namespace is the ::oo::InfoObject::namespace ([info object namespace]); ::mk is Metakit's own namespace with a set-like command
set resolves to ::tcl::array::set (array set), in ::tcl::dict to ::tcl::dict::set, and in ::oo::InfoObject namespace is [info object namespace]. Use ::set / ::namespace in such scripts. Closing.
lsort (ASCII), as it has always done (main, 9.0, 8.6 identical). Switching t…NOT-A-BUG (feature request): library/parray.tcl sorts with the plain lsort (ASCII), as it has always done (main, 9.0, 8.6 identical). Switching to -dictionary changes the output order (a small behaviour change), and passing extra lsort options changes the documented signature parray arrayName ?pattern? (library.n), so it needs a decision (TIP-level for the new arguments).
lsort with no options
-dictionary change would be a one-word edit if accepted)
-dictionary the default is a one-word change but changes the output, and extra sort arguments would need a TIP since the signature is documented in library.n. Suggest recategorising as a Feature Request.
NOT-A-BUG (Tcllib bug, wrong tracker; still present in Tcllib trunk)
[namespace origin Chunk] for -in, but no Chunk proc exists in des.tcl, tcldes.tcl or tcldesjr.tcl. No matching Tcllib ticket found (closest: 3002617fff "des, des-mode parameter and key padding").
NOT-A-BUG (design RFE; the size_t migration it worried about shipped in 9.0 — Tcl_Token.size and Tcl_Parse.numWords/numTokens/tokensAvailable are Tcl_Size in tcl.h; the requested new parse interface was never written)
NOT-A-BUG (the hang is in the third-party TclReadLine REPL, not in Tcl)
trace add execution puts leave foo, every [puts] raises invalid command name "foo" once it has done its work, as documented. TclReadLine prints errors with [puts], which fails again, and its error handler loops forever. Plain tclsh writes errors with Tcl_WriteObj, so the prompt keeps working (checked on a pty). Unrelated side note: in 8.6+ the errorInfo says (file "x.tcl" line 1) for a [puts] on line 2, while 8.5 says line 2.
invalid command name "foo" and keeps running. The hang comes from TclReadLine, which prints errors with [puts], and that [puts] fails again because of the trace. Please report it to the TclReadLine author (or have it use the channel commands only inside [catch]). Suggest closing as Invalid / Third Party.
make html How should it work?NOT-A-BUG (discussion/process ticket about the 8.7a5 release, a line that has since been abandoned). On main, make html-tcl DISTDIR=<dir> runs to…NOT-A-BUG (discussion/process ticket about the 8.7a5 release, a line that has since been abandoned). On main, make html-tcl DISTDIR=<dir> runs to completion (257 pages, index.html, Keywords/TclCmd/TclLib/UserCmd, docs.css) with the --useversion/--htmldir/--srcdir arguments from unix/Makefile.in. The 9.0.x and 9.1.0 doc distributions have been built with this since.
make html-tcl into work-a6/dist (Tcl only, no Tk tree next to the wt)
make html works on main (and was used for the 9.0/9.1 releases); 8.7 is no longer developed. Suggest closing unless there is still a specific problem with the release workflow.
NOT-A-BUG (environment: temp dir mounted noexec; same in 8.5.19 per reporter)
NOT-A-BUG (cosmetic; still the same on main, 9.0, 8.6)
bad subcommand "z": must be get or list; get zz gives key not known (errorCode TCL LOOKUP CONFIG zz)
update foo → bad option, after foo → bad argument); "unknown or ambiguous subcommand" comes only from namespace ensembles. Messages are pinned by tests/config.test pkgconfig-2.x and Tk tests/pkgconfig.test.
update, after); only ensembles say "unknown or ambiguous subcommand". Changing it would mean making pkgconfig an ensemble; low value, suggest closing (or an RFE to make key not known name the key).
NOT-A-BUG (settled; behaviour defined and tested on all branches)
testutfnext [testbytestring \xA0\xA0]1 → 2 on main/9.0, 1 on 8.6 (default TCL_UTF_MAX=3, coupled to Tcl_UtfToUniChar as dgp asked); 8.6 has utf-6.88.0 (ucs2 → 1) and utf-6.88.1 (fullutf → 2); main/9.0 utf-6.88 expects 2. testnumutfchars \xE0\x80\x80 → 3 everywhere.
Status now: Pending (Fixed)
NOT-A-BUG (TIME_WAIT on the active closer is normal TCP; Windows behaves exactly like Linux). Ticket status Pending/Fixed is wrong: branch bug-b6d0d8cc2c was never merged
NOT-A-BUG (documented behaviour; API RFE) — unchanged on main/9.0/8.6: an existing equal key keeps the old key object, a zero-ref new key is neither stored nor freed (leaks)
NOT-A-BUG (RFE: line editing/history in the interactive tclsh)
^[[A), which then fail as an unknown command. The session is not actually broken.
NOT-A-BUG (by design; performance/memory RFE)
variable L [list e1 e2 e3] inside namespace eval gives a list with string rep "e1 e2 e3"; with a non-constant word ([list e1 e2 [string cat x y]]) there is no string rep.
NOT-A-BUG (documented behaviour; changing it needs a TIP)
namespace eval ::ns1 {uplevel {#0 b}} -> bad level "#0 b" on all three. uplevel {1 b} -> invalid command name "1" on main/9.0 but bad level "1 b" on 8.6 (the digit case was already relaxed in 8.7+), so only the # case remains.
# that is not a valid #N, even when it is the only argument. uplevel.n on main says "Level cannot be defaulted if the first command argument is an integer or starts with #", so this is documented.
#N argument as the script)
# form (the integer form already falls back to the script). It is documented in uplevel.n, so changing it needs a TIP.
NOT-A-BUG (already documented, also in 8.6.9)
trap matches when the list-length(pattern) prefix of -errorcode equals pattern (whitespace normalized), and "on error is equivalent to trap {}" answers the empty-list question. Checked on 9.0.5: trap {} catches any error, prefix match works.
trap {} (empty pattern) is the same as on error. Suggest closing.
NOT-A-BUG (documented: exec redirections apply to the whole pipeline wherever they appear)
exec echo BLA >ble | ./pe.sh etc. (pe.sh prints COUT/CERR). Same results on all three: >ble gets the last command's stdout (COUT), stderr goes to the exec error result. 1>ble is not an exec redirection, so it is passed to echo as an argument. Stderr only ended up in the file in the reporter's interactive session because unknown runs commands with >&@stdout.
> fileName as "standard output from the last command" and 2> as "standard error from all commands"; redirection operators are pulled out of the arg list regardless of position (tclPipe.c:TclCreatePipeline). Per-stage redirection like sh's is not supported.
> to the last command's stdout and 2> to all commands' stderr; 1> is not a recognised redirection. In interactive tclsh, unknown adds >&@stdout, which is why stderr seemed to land in the file. Per-stage redirection needs sh -c. Suggest closing as "Works as designed".
NOT-A-BUG (behaviour by design; TCT-approved rollback, change needs a TIP)
coroutine "::c1" is already running (the synchronous chan postevent from the watch proc runs the writable handler inside the coroutine), then no further writable events -> timeout.
chan postevent, which is synchronous; data parked in Tcl's output buffer does not trigger new events. pooryorick's d0dd6d19a4 (2019) generated them on a timer, caused 080f846fd5 and socket-14.11.0 failures and was rolled back in 2024 ("Rationale for rollback of refchan event generation in core" wiki page, TCT-approved). The ticket was closed as invalid/RFE by Jan and Harald several times and reopened by the reporter (last: 2024-11-15 "does not affect the unchained branch").
-buffering none on such refchans or a TIP for asynchronous chan postevent.
NOT-A-BUG (application does not initialize the interpreter)
unknown removed (what an interp without Tcl_Init looks like): clock format fails with "invalid command name ::tcl::clock::GetSystemTimeZone" on main/9.0.5, and with an auto-load error on 8.6.18; with normal initialization it works.
clock live in library/clock.tcl (8.6) or are auto-loaded/registered from Tcl scripts (9.x), which needs Tcl_Init (init.tcl, unknown/auto_load). 8.4's clock was C only. The reporter's tclEvalGetResult wrapper was never shown; no reply since 2019.
clock needs Tcl scripts from the library loaded on demand, so the embedding application must call Tcl_Init() (and check its result) after Tcl_CreateInterp(). No reply since 2019; suggest closing.
NOT-A-BUG (works as documented; the proposal is an RFE)
if 0 else {...} runs the else-script, if 1 else {...} → invalid command name "else", as reported.
then/else are optional noise words in if.n, so in if 0 else {...} the word else is the body. Making else in body position a keyword changes language semantics (a TIP matter). No branch with the announced work exists in the repository.
if is specified: else is optional, so in if c else {x} the word else is the then-body. Treating it as a keyword would be a language change needing a TIP; no branch for it was ever committed. Suggest closing or turning it into an RFE.
NOT-A-BUG (C library behaviour: glibc < 2.26 read /etc/resolv.conf only once per process; glibc 2.26 (2017) re-reads it when it changes)
NOT-A-BUG (by design: zippy is a high-water-mark allocator; behaviour unchanged in main, 8.6)
552ed5eac5.patch: VERIFIED
sets, one with [t] in the condition) -> [info cmdcount] deltas a=61 b=4: the compactible loop (no invocation) is recompiled without INST_START_CMD, as triaged (intentional optimization); info.n still says "the total number of commands evaluated"
groff -man -Tutf8 doc/info.n renders the note correctly
NOT-A-BUG (intentional optimization) / DOCS for [info cmdcount]
62 5 38 5 (8.5.19: 62 52 38 37). Command limits still work: a child interp with a body compiled before interp limit c commands was set still hits "command count limit exceeded" on main/9.0/8.6.
NOT-A-BUG (by design: "ago" negates all relative units before it, including yesterday/tomorrow, which are ±1 day units; test clock-34.47 checks "2 days 2 hours ago" = -50 h). Same behaviour in main, 9.0, 8.6.
relunits tAGO multiplies the accumulated yyRelSeconds/yyRelMonth/yyRelDay by -1, and "yesterday"/"tomorrow" are tDAY_UNIT entries (-1/+1 day) that add to yyRelDay
NOT-A-BUG (documented behaviour; the reporter says so too). Behaviour unchanged in main, 9.0, 8.6.
namespace current is still ::n1 after namespace delete, and namespace exists n1 is 0 afterwards
NOT-A-BUG (by design, per dgp's analysis; same on main, 9.0, 8.6)
package require p 1.0 returns 1.1a0 without calling the package unknown handler
$noComp (testevalex) pass, see if {$noComp} at te…NOT-A-BUG (test-design issue; dgp's workaround is on main: string-29.5..29.15 run only in the $noComp (testevalex) pass, see if {$noComp} at tests/string.test:2452)
try {string cat [list] [list x]} at top level still yields a string rep on main and 8.6, a proc-compiled call does not
[list x] argument goes through literal/bytecode handling that gives the result a string rep; the test is about TclStringCatObjv internals, which only the direct-eval path exercises cleanly
NOT-A-BUG (already documented: socket.n "CONFIGURATION OPTIONS" describes -error, -sockname, -peername, -connecting; chan.n and fconfigure.n refer to socket(n) for socket-specific options)
NOT-A-BUG (expected cost of the design: every namespace stores its fully-qualified name, so memory is quadratic in nesting depth)
namespace eval of an N-level name also parses the whole name, so time is quadratic as well.
NOT-A-BUG (performance RFE; unchanged on main: StringMapCmd in generic/tclCmdMZ.c still loops over every key at each position, on the Unicode rep)
NOT-A-BUG (the reporter withdrew it on 2017-05-03: mintty without ConPTY gives the program named pipes, which no Windows API can tell apart from redirection)
isatty(0). On Unix the behaviour is correct.
winpty tclsh, or set tcl_interactive 1 in the shell.
NOT-A-BUG (misunderstanding of TCL_WIDE_INT_IS_LONG; resolution already "Works For Me")
NOT-A-BUG (no EOF and no data loss: a blocking [read] returns early with the data buffered so far, [eof] stays 0 and the rest arrives on the next [read]; a handler told blocking 1 is expected to block instead of throwing EAGAIN)
NOT-A-BUG (code-quality question; the routine is still used)
string match and glob-reducible regexps, when both string and pattern are pure bytearrays and the match is case-sensitive, and recursively for *.
string match, both compiled and direct (e.g. string match [binary format a* a*] [binary format a* ab]), and only for pure bytearrays. As dgp noted, it can stay until it gets in the way. Proposing to close as Works as Expected.
%#.0f); the MSVC %#g bug is NOT-REPRODUCED with the current UCRT (MSVC 2022)NOT-A-BUG ("0." is the C99 result for %#.0f); the MSVC %#g bug is NOT-REPRODUCED with the current UCRT (MSVC 2022)
0.0000e+00 0.0000 0.000|0.e+00 0. 0., matches glibc printf and format-6.3/6.5. format.test passes on main (269/269).
%#.Ng of 0.0. format.test already skips format-6.3/6.5 on MSVC builds through the knownMsvcBug constraint ([tcl::build-info msvc] eq 0, check-in 30e09611ba, 2021).
%#.0f giving "0." is what C99 requires (# always keeps the decimal point). The real difference is MSVC's %#g of 0.0, which is a CRT bug; format-6.3/6.5 are skipped on MSVC builds through the knownMsvcBug constraint. Close as Won't Fix / third-party bug.
%#.0f); the MSVC %#g bug is NOT-REPRODUCED with the current UCRT (MSVC 2022)
%#.4e %#.4f %#.4g|%#.0e %#.0f %#.0g of 0.0 gives 0.0000e+00 0.0000 0.000|0.e+00 0. 0. (same as glibc) on 9.1b1, 9.0.5 and 8.6.18 (all MSVC 1944, UCRT). format.test: 9.1 skips format-6.3/6.5 via knownMsvcBug (269 total, 0 failed); 8.6 runs them under notWinCI locally and passes (266, 0 failed).
%#.Ng of 0.0. The Windows 11 UCRT with MSVC 2022 is correct.
msvc < 1900; the 2021 CI failure may have been an older toolset)
%#.0f → "0." is correct C99 behaviour. The MSVC %#g problem is gone with the UCRT of MSVC 2022: format-6.3/6.5 give the expected results on Windows 11 with 8.6.18, 9.0.5 and 9.1, so the knownMsvcBug constraint in format.test could probably be relaxed. Close as Works For Me / third-party.
NOT-A-BUG (toolchain-specific; workaround exists)
RC="x86_64-w64-mingw32-windres -F pe-i386" configure ends up in the Makefile and produces a pe-i386 tcl.res.o; this mingw has no 32-bit multilib, so the full -m32 link was not tried
RC="windres -F pe-i386" (and CC="gcc -m32") to configure; RC is taken from the environment. The i686 mingw-w64 toolchains build 32-bit out of the box. Suggest closing.
NOT-A-BUG (documented: proc.n says defaulted arguments followed by required ones become de-facto required, "this may change in a future version")
proc f {a {b 1} c} is accepted, f x y fails with should be "f a ?b? c", f x y z works.
?b? in the wrong-args message is pinned by test proc-old-30.8)
Apr12 -format %b%y now g…NOT-A-BUG (8.6 follows documented rule [7] of clock(n): without a complete date set the base date is used). 9.x changed: Apr12 -format %b%y now gives the given year and month with the base's day (16 April 2012 for base 2026-10-16), still not day 1, and the docs don't describe that.
cafef7c585.patch: VERIFIED (test-only patch; NOT-A-BUG ticket, can be closed after the test is added)
set s end-1; list [string replace $s $s $s X] [string replace $s 0 $s Y] -> endX1 Y1 on main and 8.6. The questioned second Tcl_GetUnicodeFromObj exists only in 8.6 (tclCmdMZ.c:2390, already commented); main uses TclStringReplace. The patch is test-only.
endX Y1 instead of endX1 Y1, so the test catches the regression the ticket asked about (on 8.6, where that code lives)
NOT-A-BUG (second fetch is needed; already commented in 8.5/8.6, and the code is gone on 8.7+)
set s end-1; string replace $s $s $s X on main, 9.0.5, 8.6.18 (all give endX1)
string insert side request was done by TIP 504 in 8.7.)
string insert exists since 8.7 (TIP 504). Proposed test string-14.25 for the shared-object case; then close.
NOT-A-BUG (documented in Tcl_StandardChannels(3): in a thread without platform std channels the first three channels opened become stdin/stdout/stderr); the remaining request is an RFE needing a tcl-core decision
NOT-A-BUG (by design; resolution is already "Wont Fix", the ticket was just never closed)
info frame reports lines 2 and 5 (file lines), while info body has the backslash-newline joined, so the second command is on line 4 of the body.
info frame deliberately counts physical source lines, so that debuggers point at the line in the editor.
info frame line numbers follow the source text, not the folded info body. Resolution is already Won't Fix, so closing.
NOT-A-BUG (the flags already agree)
3588512fff.patch: VERIFIED
(!true)==false -> 0, 0 == false -> 0, false==false -> 1 (by design; expr.n on the tip only says "Boolean equal and not equal")
1 == "1.0" -> 1 (numeric), 1 == "1x" -> 0 (string), bool(false)==(!true) -> 1, !!false == 0 -> 1
NOT-A-BUG (by design: == is numeric-preferring and falls back to string comparison; "false" is not numeric). The man page is vague, so a DOCS clarification is worth adding.
NOT-A-BUG (documented in re_syntax.n: "{m} or {m}? has the same preference (possibly none) as the atom itself", while {m,m}? prefers shortest) — the output is unchanged on main, 9.0, 8.6 and 8.4: abcd abc d vs abcd ab cd
regexp -indices -inline {((a?)*|(b?)*)+} aaa → {0 2} {3 2} {3 2} {-1 -1} on main and 8.4, but {0 2} {3 2} {-1 -1} {-1 -1} on 9.0/8.6, so the recent regexp fixes on main (not yet in 9.0) changed this capture result.
NOT-A-BUG (RFE; the concrete problem was fixed in 2012)
NOT-A-BUG (RFE: behaviour unchanged and intentional since 8.5 - main, 9.0, 8.6, 8.5 all raise "couldn't read directory "tmp/": permission denied" even with -nocomplain; 8.4.20 returned an empty list, silently dropping also the readable tmp2/a.c match)
NOT-A-BUG (works as designed in Thread 2.8.13 and 3.0.7: the errorproc is called through an event queued to the thread that registered it)
update after thread::join, the errorproc gets "eval canceled ... while executing "while 1 {}"" 20/20. Canceling a script sent with -async, and cancel -unwind of a thread in thread::wait, are reported as well.
update (or vwait) after thread::join to see it. Works with Thread 2.8.13 and 3.0.7. Proposed to close, possibly with a note added to the thread::errorproc docs.
NOT-A-BUG (RFE; not doing a check before open is intentional)
file exists/stat() before every open in init.tcl/auto.tcl and C code)
file readable, and dkf noted the check-then-open race. Failed opens of optional files (auto_path probing, tclIndex, pkgIndex.tcl) are expected. A stat() would itself be an audited access on most systems.
file exists/stat() is racy and, as noted, unreliable with ACLs, so Tcl deliberately just tries the open. Closing as Won't Fix; specific noisy probes (e.g. at startup) can be reported separately.
NOT-A-BUG (by design, now documented)
vwait ${token}(status))
NOT-A-BUG (Tcl may re-type any value; an ObjType must be able to rebuild its intrep from the string, as dgp said). Partly improved anyway: the reporter's "INF" == "" case no longer shimmers.
$v == "" keeps the list intrep for 123 and INF. 0.5 == abc converts it to double, 123 == 456 to int (8.4 would also convert in the second case). 8.4/8.5 lack ::tcl::unsupported::representation, so they were not compared.
NOT-A-BUG (local setup: reporter found LD_LIBRARY_PATH pointed to an old non-threaded libtcl; works after fixing it)
NOT-A-BUG (intentional: kennykb, dkf, hobbs 2010; the ticket was auto-closed as Pending/Invalid on SourceForge, then reopened by the migration)
NOT-A-BUG (RFE)
NOT-A-BUG (by design; RFE to build a clock locale from the Windows regional settings)
%x gives 07/08/2010 (the {} locale), -locale current gives 08/07/10 (en_gb.msg DATE_FORMAT %d/%m/%y)
Status now: Pending (Works For Me)
NOT-A-BUG (VFS channel driver without readable events; Pending/Works For Me, Serhiy could not reproduce on Windows and Linux with 8.5.8/8.6.18/9.0)
NOT-A-BUG (the Thread commit that claimed it was revoked by its author)
NOT-A-BUG (by design: Tcl_Obj memory is cached by the allocator, not returned to malloc; reported behaviour unchanged)
NOT-A-BUG (calling Tcl_DoOneEvent on an interp/notifier from another thread; das explained the threading model in 2010)
NOT-A-BUG (documented behaviour; RFE for a way to remove a non-local link)
upvar 0 x uv; set uv 34; unset uv, info globals uv still lists uv and a second unset fails. Same on all versions.
NOT-A-BUG (dgp withdrew the claim himself on 2009-10-15; the docs now cover the buffer size)
NOT-A-BUG (documented in glob.n, same as sh; unchanged since 8.5)
.hid, \.hid, {.}hid match a dotfile; [.]hid, [.h]hid, ?hid, *hid match it only with -types hidden. bash and Python's glob also do not match [.]hid.
. or \.; {.} works because braces are expanded before. POSIX 2.13.3 leaves it unspecified whether [.] in a bracket expression matches a leading period.
.mozilla with [.]mozilla, and POSIX leaves it unspecified. glob.n says a leading . "must be matched explicitly or with a {} construct" unless -types hidden is given. Closing as works-as-designed.
TCL_SHLIB_LD='${CC} ${CFLAGS} ${LDFLAGS} -shared'.NOT-A-BUG (by design since 7c64b38c55, 2007). The behaviour is unchanged on main: TCL_SHLIB_LD='${CC} ${CFLAGS} ${LDFLAGS} -shared'.
${CC}/${CFLAGS} unexpanded so that CC can be overridden at make time. Consumers have to provide CC (e.g. CC=$TCL_CC) or eval with their own compiler. TEA does not use TCL_SHLIB_LD.
CC/CFLAGS/LDFLAGS; set CC=$TCL_CC before evaluating it. Closing as "Won't Fix".
NOT-A-BUG (non-POSIX system time; ticket resolution is already Invalid)
clock format 1243137600 gives 05/23/09 23:59:36 (24 s off), the reporter's symptom
NOT-A-BUG (licence is in license.terms in every source distribution, as dkf said)
NOT-A-BUG (systemtap limitation, fixed in systemtap 0.9.5 per the reporter on 2009-05-18). CANNOT-TEST here (no systemtap/sys/sdt.h installed).
_stapprobe1_<name>_<__LINE__> label per probe, so two probes expanded on one source line collided.
NOT-A-BUG (documented-by-usage compatibility behaviour; removal needs a TIP)
interp create foo -safe creates a safe interp "foo"; interp create a b errors correctly
NOT-A-BUG (works as designed since TIP #357 80aa157f45: libraries are unloaded at finalization only with TCL_UNLOAD_DLLS; an ill-behaved library needs --disable-dll-unloading; on Unix a VFS library's temporary copy is deleted right after loading, so nothing ties its lifetime to the VFS). No reproducer was ever given, the ticket is an RFE-like note from 2008
NOT-A-BUG (feature request; the work branch tip-162-branch was abandoned: last check-in acab51185e 2009-01-06, marked Closed by kbk 2011-02-28; IPv6 sockets (TIP 162) went in by another route in 8.6)
NOT-A-BUG (intentional since 8.4.14, consequence of the fix for Bug 943995; dgp said so in 2008)
glob /tmp/ gives /tmp on 8.4.11, /tmp/ on 8.4.15, 8.6.18, 9.0.5, main (Linux)
NOT-A-BUG (refactoring/design idea, no defect described; msofer's 2010 comment says the coroutine blocker is gone)
NOT-A-BUG (vague reminder/RFE; the TclX crash in the comments was TclX using 8.5 internals, msofer 2010)
NOT-A-BUG (an already loaded encoding stays usable while anything, including a literal's Tcl_Encoding intrep, holds a reference; [encoding dirs] only affects future file loads, as documented)
encoding convertto jis0208 ... in a proc, encoding dirs {} and the same literal still converts (0 8C); a fresh name gives "unknown encoding". encoding-2.2 and 11.1 were made robust in 2008 by dgp (llength shiftjis shimmer) and pass.
NOT-A-BUG (documented: on Unix a relative target is relative to the link's location, file.n "file link"). Changed between 8.4.15 (accepts cwd-relative targets) and 8.5.
file link -symbolic td/l1 td/td1; 8.4.15 accepts it.
NOT-A-BUG (on current systems: glibc >= 2.26 (2017) reloads /etc/resolv.conf itself when it changes; other libcs handle it in their resolver, which is the right layer)
1733117fff.patch: VERIFIED
known: 1.0; require -> 1.0; after package forget vfoo -> 2.0. Exactly the behaviour the new text describes.
NOT-A-BUG (documented semantics) / DOCS
NOT-A-BUG (Tcl_EvalObjv runs a single pre-parsed command, not a script, so there is no script location; behaviour unchanged and codified by tests info-41.0/41.1)
type eval line 1 cmd {info frame 0} level 0; Tcl_EvalObjv (flags 0 or TCL_EVAL_GLOBAL) gives type precompiled.
precompiled only as tbcload code; it is also the result for commands invoked directly via Tcl_EvalObjv/invokehidden with no script)
NOT-A-BUG (RFE; behaviour now documented in proc.n since c992833adf, 2008-01-17: such defaulted arguments "become de-facto required arguments ... portable code should ensure that all optional arguments come after all required arguments")
proc prov {{opt 23} man} ... is accepted; prov 1 → wrong # args: should be "prov ?opt? man"; prov 1 2 works; same for [apply].
?opt? although opt is effectively required (ProcWrongNumArgs).
NOT-A-BUG (NFS client access() behaviour; resolution already Wont Fix), CANNOT-TEST (NFS)
NOT-A-BUG (in the tcllib dns package: it closes the socket by a stale name)
close $state(sock) and then calls the -command callback, but leaves state(sock) set; ::dns::cleanup closes $state(sock) again. A socket opened inside the callback can get the freed name (names come from the fd on 8.4/8.6, from the state pointer on 9.x), so cleanup closes the user's new socket and its writable handler never fires. Tcl-only demo (work-a5/sn.tcl): close a socket, open another (same name on main), [close] the old name: closes the new one. There are never two open channels with the same name.
NOT-A-BUG (documented: file.n says "file copy will copy soft links (i.e. the links themselves are copied, not the things they point to)"; same as cp -a / cp -R)
NOT-A-BUG (NaN is a valid double; int() of NaN has no integer value)
string is double -strict NaN = 1, expr {int(NaN)} gives "floating point value is Not a Number" (the same for Inf). Behaviour unchanged and consistent with the docs.
$x == $x, or [string is entier] / [string is integer] in 9.x).
$x == $x (and finiteness) as well. Suggest closing.
NOT-A-BUG (documented limitation; the recommended zero-timeout timer works for what the BUGS section is about)
update idletasks and update loop forever (as documented in DoWhenIdle.3 BUGS); an after 0 callback that reschedules itself does not block update idletasks (returns at once, callback not run) but does make a plain update loop forever, on all versions (8.4.20 same).
update idletasks loop until no idle handlers remain; zero timers are not idle handlers, so they don't block Tk's "wait for idle" paths. Tk bug 1348333 (text widget creating too many timers) is a Tk-side problem and is still open in the Tk tracker.
update idletasks (only a full update, which by definition processes all pending events). The Tk text widget problem is Tk ticket 1348333. Suggest closing this one.
NOT-A-BUG (documented: "Trying to overwrite a non-empty directory ... will all result in errors even if -force was specified"; resolution is already Rejected, reporter said in 2008 "if not just close it")
scan 0.99 %d.%d.%d.%d returns 0 99 {} {} on main and 8.6.18 (one element per conversion, empty …1367506fff.patch: VERIFIED
scan 0.99 %d.%d.%d -> 0 99 {}, scan {} %d.%d -> `` (work-a4/v4docs1.tcl); scan.n describes only the empty-input case.
NOT-A-BUG (intentional, per hobbs 2005) / DOCS: scan 0.99 %d.%d.%d.%d returns 0 99 {} {} on main and 8.6.18 (one element per conversion, empty for unperformed ones); scan "" %d.%d returns ""; scan.n only describes the second case.
NOT-A-BUG (TIP #398: exit does not wait for nonblocking output; the reporter's 10 x 10 KB scenario is NOT-REPRODUCED)
flush; close; exit loses the tail (received 183–191 of 200) in 1–3 of 10 runs on 9.1b1, 9.0.5, 8.6.18; plain exit loses 1 message in 0–2 of 10; fconfigure -blocking 1 before flush, or keeping the event loop alive 1 s after close: 0/10 lost; with TCL_FLUSH_NONBLOCKING_ON_EXIT=1: 0/20 lost on 9.1b1 and 8.6.18. Linux 9.1/8.6 with 200 x 10 KB: 0/20 lost (bigger localhost buffers).
NOT-A-BUG (deliberate idiom: each iteration closes/deletes the entry, so re-fetching the first entry is the safe way to drain the table; andreas_kupries said so in 2005)
NOT-A-BUG (website issue from 2004; www.tcl-lang.org now has release pages and changes files; not a Tcl source bug)
changes.md / README.md release notes
NOT-A-BUG (WinHelp tooling removed in 8.7/9.0 by fadc186aac, 2020-11-25; in 8.6 tools/man2help*.tcl remain but no makefile uses them)
AS {} handler; 9.0/main have no man2help*.tcl, win/makefile.vc builds .chm via tcltk-man2html.tcl (htmlhelp target).
NOT-A-BUG (deliberate design, resolution already "Wont Fix"; ticket just never closed)
NOT-A-BUG (documented in filename.n: "Any number of trailing slash characters ... are simply ignored ... foo/ does not necessarily mean a directory"); the "odder" case from the comments is fixed
test -e says no), [file exists plainfile/.] → 0 (was 1 in 8.4.6), [file exists dir/] → 1
NOT-A-BUG (design limitation / RFE: one owning filesystem per path, linear registration-order lookup)
NOT-A-BUG (obsolete: TCL_TRACE_ENTER_EXEC/LEAVE_EXEC were public in 8.4's tcl.h, but since 8.5 they are internal, defined only in generic/tclInt.h; the C API for execution traces is Tcl_CreateObjTrace, documented in CrtTrace.3)
NOT-A-BUG (obsolete: since 8.5 number parsing is Tcl's own (TclParseNumber/bignums), not libc strtol; get-1.10 now tests testgetint -18446744073709551614 and expects the "integer value too large" error)
Status now: Closed (Invalid)
NOT-A-BUG as reported (by design, close(n): a non-blocking channel with pending output is closed in the background once the flush completes; serial "discard on close" was added by TIP 160 -closemode, 9.0, but that applies only inside the driver close, not to Tcl-level buffers). But it uncovered a REPRODUCED regression (8.7b1, 9.0, main; not 8.6) in the Linux epoll notifier: if the reader goes away during the background flush, the flush never finishes, the closeProc is never called and the process spins at 100% CPU until exit.
open "|sleep 1" w, non-blocking, 300 KB written, close: on 8.6 the fds are released once sleep exits (EPIPE). On main/9.0 they stay open for 17+ s, and strace shows epoll_wait returning EPOLLERR with timeout 0 in a loop. Simpler: chan event $p writable on a pipe whose child exited without reading fires after 7 ms on 8.6; on 8.7b1/9.0/main it never fires (3 s timeout, ~2 s CPU burnt), and close then reports no error, so the data loss goes unreported.
timeout 0 {}) and passes with it (writable 1 {broken pipe}). io, event, socket, chanio, ioCmd, exec, unixNotfy and zlib tests pass. The kqueue notifier (BSD/macOS) looks fine (EV_ERROR is folded into the filter's own mask), not tested.
-closemode discard covers the serial OS buffers. But on 8.7/9.x Linux, a background flush to a pipe whose reader died never ends: the epoll notifier maps EPOLLERR only to TCL_EXCEPTION, so the writable handler never runs and the notifier spins. Proposed fix: map EPOLLERR to readable+writable too (test io-78.1). That one probably deserves its own ticket.
NOT-A-BUG (design question, answered in the 2002 comments; superseded by zipfs)
info library is //zipfs:/lib/tcl/tcl_library (script library embedded in libtcl, TIP 430, i.e. the "internal VFS" idea from the comments); unix/tclUnixInit.c still compiles in TCL_LIBRARY (defaultLibraryDir) and TCL_PACKAGE_PATH as fallbacks/tcl_pkgPath.
NOT-A-BUG (test-suite refactoring suggestion, not a bug)
open "|..." pipelines to child tclsh processes
NOT-A-BUG (reverse DNS lookup by design; synchronous getnameinfo() has no timeout)
::tcl::unsupported::noReverseDNS (undocumented). A real fix (numeric-only option, async lookup) needs a TIP.
::tcl::unsupported::noReverseDNS turns it off (Unix and Windows). Anything better (an option that returns only the address) needs a TIP, so this could be moved to RFE.
NOT-A-BUG (documented: no exit status from closing a non-blocking pipe)
open "|sh -c {exit 33}" read via fileevent until eof. Blocking: close raises CHILDSTATUS pid 33. -blocking 0: close returns 0 with no error. The trigger is -blocking, not buffering.
isNonBlocking, so close never blocks. doc/open.n says: "unless the pipeline is in non-blocking mode then no exit status is returned (a silent close with -blocking 0)". Getting the status of children that have already exited (as the reporter suggested) would be a behaviour change.
fconfigure $fid -blocking 1 before [close] to get the CHILDSTATUS error. Can be closed (or moved to RFE for "report status if the children have already exited").
$name and $name(index), in 8.6, 9.0 and main)NOT-A-BUG (documented: Tcl.n says "Letters and digits are only the standard ASCII ones" for $name and $name(index), in 8.6, 9.0 and main)
"$пи", "$é" stay literal on main build, 9.0.5, 8.6.18, 8.5.19; ${пи} works; expr {пи()} gives "invalid character" everywhere.
_ and ::.
NOT-A-BUG (obsolete: the difference was between Windows 95/98 and NT/2000; Tcl has not supported 9x for a long time)
NOT-A-BUG (BOM detection is an application concern; explicit-order utf-16le/utf-16be encodings exist since 8.7/9.0, covering hobbs' request)