Question: How to handle the new error checking in Tcl

[tmtvl]

A little over a year ago the following message popped up in the Debian bug tracker:

This seems to be caused by a recent change in libtcl-perl, which grew
a Tcl::Code::DESTROY method; it looks like the error doesn't refer to
the calling script (t/tcl.t) any more but to the module.
Not sure if we should just relax the test or if there's something to
be done in Tcl (all those warnings about DeleteCommand, also in the
same new method, don't like good either).

source

The question now is whether we should adapt our test to the update in Tcl, or whether we should have them update their code.

[chrstphrchvz]

Related issue on RT: https://rt.cpan.org/Public/Bug/Display.html?id=115662

Also see PR #2

[chrstphrchvz]

I've published Tkx 1.10 which ignores the test failure for now. I do agree currently that it's due to changes in newer Tcl.pm.