Hi Harald

thank you, I'm tuned on the thread at TCLCORE. When Tcl will be changed to address this issue we'll see what are the repercussions on Rivet and decide what's best for us.

I don't have a test in mind, but it should be easy to imagine one. IIRC the whole stuff was about asynchronous I/O, there is plenty of possible test examples


 -- Massimo

On 07/15/2015 03:32 PM, Harald Oehlmann wrote:
Two years ago, same time, we integrated a patch into TCL to support fork
of an interpreter with loaded packages but no open channels, after
scripts running etc.

The TCL patch had a bad impact on the TCL exec command and must be revised.
It might happen that we have to change rivet for that.

The related discussion is on the TCL core list.

I have flaged our cooperation to eventually do modifications on Rivet.

Thank you all,
Harald

---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org

Reply via email to