#6 ``package require'' misbehaves

[Mikhail T.]

In the standard TCL, tclPkgUnknown will look into the
directories listed in auto_path AND into each
subdirectory of those, looking for the pkgIndex.tcl
file.

The NWS' tclPkgUnknown only looks into the listed
directories themselves.

Is there a reason for it? Can the stock unknown.tcl be
used now?

-mi

[Andy Doerr]

Logged In: YES
user_id=99759

I believe that the original development was for an ISP
(NeoSoft) and as such it package require would only allow
specific packages to be allowed only packages explicily
defined by the ISP would be available from the webpages.

If you work in a closed development environment much of the
safe interp are not nessessary.

easiest way to add a package is to add it in the devel.tcl
in the proc devel_init:
$safeInterp eval [NeoPkgAdd load <package name>
<version> <library filename>]
it will look in libPath (defined in init.tcl) to find the
library file.

libPath

[Mikhail T.]

Logged In: YES
user_id=173641

I know the _workaround_. But I'd like to see the problem
fixed in the next release. Why can't the same package
loading
mechanism be used as in the regular TCL?

Regular TCL handles safe interpreters...