From: miguel <ms...@us...> - 2006-10-16 15:50:23
|
OMG, I had forgotten you guys :} Please refer to the tip text: http://tip.tcl.tk/278 I am trying to establish how much breakage this TIP is likely to cause. All testing is welcome. Please bang on it, and provide feedback. I have opened a tip-278-branch on Tcl cvs. You can get it from anonymous cvs by cvs -d:pserver:ano...@tc...:/cvsroot/tcl login (hit return on pwd request) cvs -z3 -d:pserver:ano...@tc...:/cvsroot/tcl \ co -r tip-278-branch tcl Please note that we expect that this tip will fix more errors and code fragility than it will cause. Testing the branch may actually provide pointers to current bugs - in the sense that the code is working, but not according to what one was expecting. There were quite a few such cases in Tcl's testsuite itself ;) Devels of amsn found at least one problem in bwidget: <quote> However, Tip 278 also breaks (at least) BWidget. In widget.tcl, one can find this: proc Widget::init { class path options } { ... set Widget::_class($path) $class Which needs to be ... set ::Widget::_class($path) $class or perhaps ... set _class($path) $class </quote. Cheers Miguel |