>>>>> "SC" == Simon Cozens <[EMAIL PROTECTED]> writes:
SC> On Thu, Aug 03, 2000 at 09:12:45PM -0400, Chaim Frenkel wrote:
>> And while were here, does anyone understand kpathsea?
SC> Yes.
>> Would it be a win. I think it would.
SC> There's been some amount of talk on one of the sekrit cabal TeX
SC> mailing lists about getting rid of it. I can't see where you'd
SC> want to use it. To locate modules and shared objects? No, far
SC> better (and probably actually faster) to search a list of paths as
SC> we're doing right now. It also means you don't have to trust all
SC> the users and packages out there to update their Perl lsrs every
SC> time something changes.
Well, the issue is how much time is spent opening directories and checking
for entries. Also on an NFS mounted file system, the directory has to be
re-requested.
As for keeping hte ls-r updated. That would be the job of the installation
process. perl core would be taken care by install. site-lib (or its
replacement) would be handled by makemaker's replacement.
All other directories would be handled via the fallback to normal searching.
Actually, thinking about it. This may make automatic @INC adjustments.
All the core needs to find is the ls-R, that would give it what to search.
The rest would be PERL[56]?LIB and family.
<chaim>
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
