An experience user got burned by doing a package require inside a webpage and
then later the httpd processes would malfunction because the procs got loaded
into the request namespace and disappeared with it. It can be extra confusion
because sometimes the pages work and sometimes they don't, depending on which
child gets the request.
That's how it works, and I don't see an easy way to change it. I think we
should document it as a common pitfall, however.
We (flightaware) load all of our packages up front, in the global init script,
and now, instead, the server init script.
Also, a ... namespace eval :: {package require foo} ... should work. As we
sort of replace global, perhaps we should replace package with a frontend.
That seems pretty scary, though. Maybe best just to document the behavior and
move on.
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
