Great, thanks! I didn't know about "xotcl::interp."
Can you say anything more about 1.1--when it's coming and what it contains?
Uwe Zdun uwe.zdun@wu-wien.ac.at wrote on 09/16/2003 05:48:32 AM:
Michael,
this problem does not seem to exist anymore in the forthcoming 1.1 release ... in the 1.0.* releases it should work to use the xotcl::interp command (which pre-initializes xotcl in the child interp) instead:
package require XOTcl
xotcl::interp create Interp Interp eval {package require XOTcl} xotcl::interp delete Interp
Uwe