opendir() - Is there a filename cap ?

[Enrique Arredondo]

----- Original Message ----- 
From: "Fairlight" <fairlite at fairlite.com>
To: <filepro-list at lists.celestial.com>
Sent: Thursday, November 10, 2005 4:15 PM
Subject: Re: opendir() - Is there a filename cap ?


> At Thu, Nov 10, 2005 at 03:55:40PM -0800 or thereabouts,
> suspect Enrique Arredondo was observed uttering:
>> Why doesn't opendir detect this files :
>>
>> E-Mitsu183-15-A22-1_0000.gif
>> E-Mitsu183-15-A22-1_0001.gif
>> tnailE-Mitsu183-15-A22-1_0000.gif
>> tnailE-Mitsu183-15-A22-1_0001.gif
>>
>> I have hundres of files and some are not detected and some are detected ,
>> Is there a lenght cap ?
>
> Not detected at all, or truncated in the array that shows the names.  The
> offsets and lengths indicated a 32 character length would be represented.
>
> Actually, opendir() shouldn't have any limits--it just does an opendir()
> internally.  It's nextdir() you have to be concerned about.  I should 
> think
> they'd appear but be truncated.  Is this not the case?
>
> mark->
> -- 

The first thing I do is check how many files exists in the folder that 
matches my search criteria, using opendir():

   fn = opendir("t*","/docs")

   where fn = 0   that means there are no files in that /docs folder

     and fn > 1   it found files in that folder.

   Am I right ?  I'm getting fn =0 , even though I have 4 files in that 
folder , in which only 2 start with the t*.This behavior happens when the 
filenames are long.

How come ?

Is there a free guide on the internet that teaches how to do this operation 
using the @dirlist, @dirlist_ext, @dirlist_filena and @dirlist_name ? The 
filepro help doesn't gives examples.