tcloo | Tcl OO Package | Script Programming library

1. Tcl waits to build the package list until you ask for a package whose name it does not currently know. catch {package require thereisnosuchpackage} should mostly populate the list.

   However, there are some packages that are stored as Tcl modules and that never get entered into the list. They use a more efficient loading mechanism, but are somewhat restricted in format. tcl::tm::path list will give a list of directories where they can be found, and the package name and version are built from that into a file.

   I don't like that there isn't a way to get a list of those modules neatly, even if just for maintenance and discovery purposes.

1. The expr command rewrites the call to the log(1.23) function from:

You can get the name of the object with self object, or just self. You can then get the class of the object with info object class. And finally, you can get the member variables of a class with info class variables.

Putting it all together results in:

Im not sure what else must be done for TclOO. Any thoughts.

pkgIndex.tcl: The placement of the mixin-defining script mixin_action_chains.tcl is wrong, it comes after the mixin has already been required in the previously sourced script webdriver.tcl, like entering directly:

The gpg-agent formula was removed by commit 965e1. The reason is given in the commit message:

TclOO defines no equality system for you by design; as the objects are in general modifiable, there's no automatic notion that would apply other than object identity, and you can just compare the name of the object to get that (or the results of info object namespace $theObj, if you're being very paranoid; I think Tcl 8.7 will provide more options, but that's not yet accepted).

If you want to define an equality system such as you are proposing, you could do this:

This is a bug in ::logger::utils::createLogProc in loggerUtils.tcl in that the %M substitution is not aware of TclOO. If it was, it wouldn't be using the name of the object that the method was invoked on, but rather the name of the method. (It appears that it was designed to work with [incr Tcl], which does name methods like you appear to want.)

Ideally you'd be setting up the logger once per class, not once per instance. Here's how you'd do that:

TclOO methods are not commands. (Technically, it's because they have a different C signature.) To make this work, you need to create an extra command in the object that acts as a delegate for the method; the trick to doing this efficiently is to use tailcall my to do the dispatch.

The TclOO API, unlike much of the rest of Tcl, only exports itself via a stubs table. You should #define the symbol USE_TCL_STUBS to be 1 before you #include the Tcl header file, and link against the tclstub library. (This is the recommended way of building extensions anyway.)

[EDIT]: If you're embedding Tcl within your program, you need a more complex procedure. Basically, you need to partition your program into the parts that are an application and the parts that are an internal extension. The parts that call Tcl_CreateInterp are most likely the application part, and the parts that access the TclOO API are the extension (and will need to call Tcl_InitStubs and Tcl_OOInitStubs in an initialisation function).

The extension parts need to be compiled with USE_TCL_STUBS defined. (As it is critical, you might put that as a #define at the top of the file. The wiki page mentions USE_TCLOO_STUBS as well, but that's implied by USE_TCL_STUBS.) The extension parts need to be built without it. You can call the initialisation function that installs your internal extension immediately after the Tcl_CreateInterp call, before you start running any (non-built-in) scripts. Then when you link everything you link both against libtclstub and libtcl.

The reason for this complexity is that TclOO started out as a separate extension itself, and that never supported external API references. I probably ought to relax those restrictions for Tcl 8.7…

Methods with names that start with a lower-case letter are public, others are private. You can also use export and unexport.