<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18812"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=312434202-13092009><FONT size=2
face=Arial>No, you are accessing the same array, but once you pass the file
you've just NEXTDIR'd you can't go back and do anything to something previous in
the list with NEXTDIR. I misrepresented that it was doing more system
calls with the nextdir. I find it harder to parse the @dirlist than to just use
the parts I need with @dirlist_name, etc. But I was referring originally
to your doing mv's or cp's with an ls/user combination. That I thought
would executing over and over, until I read in your note that you were getting
the ls just once and somehow working the list retrieved one at a time.
Like I said, I skipped over a quick glance at your first posting to push you
towards opendir(). Pointing to items in the 3 @dirlist_* arrays is just easier
than employing nextdir(). No savings in system calls.</FONT></SPAN></DIV>
<DIV><SPAN class=312434202-13092009><FONT size=2 face=Arial></FONT></SPAN><FONT
size=2 face=Arial></FONT> </DIV>
<DIV><SPAN class=312434202-13092009><FONT size=2
face=Arial>JE</FONT></SPAN></DIV>
<DIV dir=ltr align=left><BR></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Tyler [mailto:tyler.style@gmail.com]
<BR><B>Sent:</B> Friday, September 11, 2009 3:36 PM<BR><B>To:</B>
john@valar.com<BR><B>Cc:</B>
filepro-list@lists.celestial.com<BR><B>Subject:</B> Re: Re: USER command
questions (Fairlight)<BR></FONT><BR></DIV>
<DIV></DIV>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
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff size=2 face=Arial>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 size=2
face=Arial>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></BLOCKQUOTE></BODY></HTML>