Hi folks, I noticed this sentence on the Tcl Scripting API page in the docs:
> Tcl commands are stateless; e.g. the telnet command has a concept of > currently active target, the Tcl API proc’s take this sort of state > information as an argument to each proc. This doesn’t seem to be correct as far as I can tell. The “targets” command definitely *can* be sent to a Tcl RPC socket or executed in a Tcl proc (even though maybe you *shouldn’t* usually do the latter), and commands like “program” and “verify_image” don’t exist in target-name-prefixed form, so AFAICT you *have* to switch the current target to use those commands, whether you’re using them from Telnet, Tcl script, or Tcl RPC. I’m not sure what this should say, but if people agree I can probably put together a patch. Thoughts? -- Christopher Head
