Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!tut.cis.ohio-state.edu!mailrus!iuvax!bsu-cs!jbwaters
From: jbwaters@bsu-cs.UUCP (J. Brian Waters)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Question about EXAMINE/EXNEXT
Summary: Manx' scdir() does this...
Message-ID: <5977@bsu-cs.UUCP>
Date: 1 Mar 89 15:34:55 GMT
References: <8374@netnews.upenn.edu> <757@microsoft.UUCP>
Distribution: na
Organization: The Binary Bin
Lines: 18

In article <757@microsoft.UUCP>, w-colinp@microsoft.UUCP (Colin Plumb) writes:
> A few notes: apparently, there exists a wildcard-matching utility that
> unlocks a directory between calls to ExNext().  THIS IS A BAD THING.
> The FFS has (and my filesystem will have) kludges to make this work
> most of the time, but people who do this are EVIL.  The kludges slow
> things down dramatically (when they're invoked).

The Manx scdir() function does this....  I have written a replacment for it
that I link in with most of my programs.  Unfortantly,  my replacment requires
the arp library.  I think they do this to avoid leaving a lock around if someone
aborts the program between calls to scdir(),  my replacment gets around this
by using arp's resource tracking.  Does anyone have a replacment that avoids
leaving a lock if aborted,  and avoids calling UnLock() after every call?

Sigh,  I hope the next Manx fixes this,  and also includes a atexit() which
would make fixing this easier.
-- 
Brian Waters              <backbone>!{iuvax|pur-ee}!bsu-cs!jbwaters