After the mod_rivet commands moved to the ::rivet namespace, the
configuration stage became the phase where you could tell if the ::rivet
namespace commands were to be exported and if it had to be imported into
the global namespace. Defaults were chosen to enable both the export and
the import so that compatibility with previous versions of mod_rivet was
preserved.
Looking ahead towards the release of rivet 3.0 I think it's time to take
a further step ahead and I think we should:
1 - make all this stuff fully customizable through the module
configuration instead
2 - change the defaults so to force the programmer to at least
intentionally import the commands in the ::rivet namespace either
through the configuration or at interpreter initialization (namespace
import ::rivet:*)
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
