On Fri, Sep 11, 2009 at 11:24 AM, John Esak <span dir="ltr"><<a href="mailto:john@valar.com">john@valar.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">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.</font></span></div>
<div dir="ltr" align="left"><span></span> </div>
<div dir="ltr" align="left"><span><font face="Arial" size="2">JE</font></span></div></div></blockquote><br>Ah, perhaps I misunderstand how NEXTDIR works? My impression was that NEXTDIR read from @dirlist. Does it do a separate OS call each time? <br>
<br>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.<br><br>From dev ref appendix of system maintained arrays:<br>"@dirlist replaces the NEXTDIR function which used to had to be run to build a list of files found"<br>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???<br>
<br>Tyler<br><br><div class="gmail_quote"><br></div><br>