On Tue, 29 Jan 2019 12:12:12 +0100 Gustaf Neumann <neum...@wu.ac.at> wrote:
> So, i think, it is the best strategy for NaviServer to put the > fingers away on stuff > coming from Tcl. ... indeed, and not *only* Tcl. I doubt we can be absolutely correct at that place, since the task itself is far to complex to be solved in a "cost-effective" way (the task is to replicate a fully loaded Tcl interpreter from one thread to another). So "problems" like this one will re-appear in the future and in other setups. Perhaps we can put the "magic" that ttrace module is doing out of the main configuration setup and use it for special purposes? The people then need to use [ns_ictl] to register callbacks for interp initialization themselves. In that case they (should) know what they can expect. In the moment all is pretty "spooky" and it is difficult to grasp... Cheers, Zoran _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
