Tcl Source Code

I don't think it's difficult to add those to the public API: Those functions are MODULE_SCOPE, and named `TclRegisterCommandTypeName`/`TclGetCommandTypeName`. But ... would any extension need those?

I think the answer to this question is `No`, so I would suggest to leave the implementation as-is. We can modify the TIP, mentioning this change-of-insight.

That said, I don't object to making this public (if there is an interest implementing the Tk-part, as mentioned in the TIP). In that case, I recommend only doing this for 9.0, not for 8.7.

I do not have any particular need for the aforementioned functions so I am fine leaving things as they are. Only brought it up in case they were omitted as an oversight and not by intent.

Donal, please close ticket if the functions in question were not exported by intent.

I would like to see this as part of the public API to (hopefully) improve introspection in some mainstream packages.

for example the command created by 'sqlite3 dbcmd' is of type native - and I'd like to identify it as belonging to sqlite3 (for documentation & command completion) without the risk of calling unknown native commands that may have side effects. 

If this were public I'd be inclined to submit an RFE on the sqlite forum for adding a specific type such as sqlite3::dbcmd via this mechanism.

Presumably some guidance for package developers to avoid collisions via something like a prefix matching the package name would be nice too.(?)

I'd be interested also to hear if this may eventually be coming - or if there is perhaps some concern about collisions or type name proliferation?