Re: Tcl bytecode
- From: "Larry W. Virden" <lvirden@xxxxxxxxx>
- Date: 31 Jan 2007 04:13:27 -0800
On Jan 30, 1:58 pm, Don Porter <d...@xxxxxxxx> wrote:
[...] [tclPkgUnknown] crawls all over trying to
discover every package it can find.
What matters is the number of directories in the value of $::auto_path,
the number of subdirectories in those directories, and the access speed
to the storage those directory pathnames represent.
Typical slow configurations have /usr/lib on $::auto_path, with
[llength [glob /usr/lib/*]] very large, and with storage at the other
end of a (possibly several... automounted?) network connection(s).
Don, how far down does it crawl? Certainly it looks in the
subdirectories directly under the $auto_path elements. But does it go
further? When Bwidgets installs with BWman and the demo directories,
does it look there? I wonder how many extensions install with stuff
that need not be present in the actual $exec_prefix/lib or $prefix/lib
- stuff that could go into $prefix/share or whatever.
.
- Follow-Ups:
- Re: Tcl bytecode
- From: Don Porter
- Re: Tcl bytecode
- References:
- Tcl bytecode
- From: Googie
- Re: Tcl bytecode
- From: Googie
- Re: Tcl bytecode
- From: Jeff Hobbs
- Re: Tcl bytecode
- From: Keith Nash
- Re: Tcl bytecode
- From: Cameron Laird
- Re: Tcl bytecode
- From: Don Porter
- Tcl bytecode
- Prev by Date: Re: Tcl bytecode
- Next by Date: Re: Whats a good way to write GUI apps
- Previous by thread: Re: Tcl bytecode
- Next by thread: Re: Tcl bytecode
- Index(es):
Relevant Pages
|