🚀 go-pugleaf

In article <15327@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:

>	Where is the lock coming from?  When was the original Examine() done?
>(You of course know that you must Examine() a directory lock before
>ExNext()ing...)  Every time you do Examine(), you reset and ExNext will
>take you through all the files in the directory.  Note that changing a
>directory while examining it will have, at best, "funny" effects.  Deleting
>files causes the worst problems, since the file being examined with ExNext
>might be deleted, leaving no way to find the next file in the directory, or
>worse yet, it might have been reallocated for a new file header in a different
>directory.  In the ram disk, it might end up referencing deallocated memory,
>leading to a guru or other very bad result.

What is the "accepted" way of scanning through a directory using Examine(),
ExNext() while deleting the files as you go?  Is there an alternative to
having to restart the scan each time you delete a file?

--
Mike Oliphant		    UUCP: alberta!herald!telepro!oliphant
			Internet: oliphant@telepro.uucp
			 FidoNet: (1:140/91) - ZMH only
*
* Call TelePro, the development system for DIALOG Professional
*
*   Phone: +1 306 249 2352	2400/9600/14400 bps HST
*	   +1 306 652 2084	300/1200/2400 bps
* FidoNet: (1:140/90)
*