Steve Bennett

Thanks. All feedback is useful. I am hesitant about adding new error codes, but I'll consider yet. Yes, info tainted with no arg should be an error.

Yes, for sure with Win32_ShellExecute. Not so sure about the redis extension, as there is no quoting in args passed to redis, it is hard to get an injection attack....

Thanks. Will merge once I've updated the documentation.

Tcl 8.6 does seems to be moving to towards standardising on "unknown or ambiguous subcommand ...", thus not differentiating between unknown and ambiguous, so that is a reasonable choice. Although...

Thanks. Looks interesting. I actually have something similar myself out-of-tree, it has never become "production ready". I'll push mine to a branch so you and others can have a look,...

Take a look here: https://github.com/msteveb/jimtcl/commits/xtrace But as I say, I won't be able to get to this for a while.

The heart of my debugger is the xtrace command. The idea is to push all the decision making out to a script/command rather than build it in.

I mentioned my concerns about the libffi port in #55. It seemed very cumbersome (and possibly slow). If ffidl gives a better interface, that would be good.

I put an explanation in examples/testbed/subdir/Makefile.in, but it might be hard to discover. Where should this go in the documentation to make it easy to find?

Thanks for the report. I don’t know much about Debian packaging so we are equal 😀. What version of jimtcl is it using?