From db79156fd528e0a9729ae8bc260452489fc2d4af Mon Sep 17 00:00:00 2001 From: Antonio Borneo Date: Fri, 22 Aug 2025 14:49:16 +0200 Subject: [PATCH] doc: drop incorrect lack of namespaces in Jim Tcl Since 2011 [1], Jim Tcl supports namespaces as an optional package that is compiled-in by default. Drop the incorrect sentence in OpenOCD documentation that reports namespaces as not supported by Jim Tcl. It was true in 2008 when the sentence was added with [2]. The meaning of the paragraph in the documentation does not change. Change-Id: I30b422e369d106e70f5e1e20b21f0b6ea0fe6b8d Signed-off-by: Antonio Borneo Link: https://github.com/msteveb/jimtcl/commit/7f383c6726fd [1] Fixes: a28eaa85f ("jtag newtap change & huge manual update") [2] Reviewed-on: https://review.openocd.org/c/openocd/+/9093 Tested-by: jenkins --- doc/openocd.texi | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/openocd.texi b/doc/openocd.texi index 987339eb7..7f7c8892f 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -1440,7 +1440,6 @@ In addition to target-specific utility code, another way that board and target config files communicate is by following a convention on how to use certain variables. -The full Tcl/Tk language supports ``namespaces'', but Jim Tcl does not. Thus the rule we follow in OpenOCD is this: Variables that begin with a leading underscore are temporary in nature, and can be modified and used at will within a target configuration file.