USER command questions (Fairlight)

[Tyler]

On Fri, Sep 11, 2009 at 11:24 AM, John Esak <john at valar.com> wrote:

>  If you're going to use opehdir() as you say with SYSTEM, then do yourself
> ahother favor and get rid of the NeXTDIR.. Why "execute" that command for
> every file in the folder, when all you have to do is increment a counter and
> it automaticlly points to the next file.  I'm missing your logic here.  Or,
> maybe I didn't explain the @dirlist arrays wlell nough.
>
> JE
>

Ah, perhaps I misunderstand how NEXTDIR works?  My impression was that
NEXTDIR read from @dirlist.  Does it do a separate OS call each time?

NEXTDIR is listed right after OPENDIR, and the last section in OPENDIR is
"Once you have run OPENDIR, the list is stored in the system array,
@dirlist", it made sense to me that NEXTDIR was just an easy way to step
thru said array rather than having to custom build a loop every time.

>From dev ref appendix of system maintained arrays:
"@dirlist replaces the NEXTDIR function which used to had to be run to build
a list of files found"
Why this info isn't in the entry for NEXTDIR in the dev ref or online I have
*no* idea.  Seems important to mark deprecated commands and their
replacements, no???

Tyler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20090911/c6de6287/attachment.html