opendir() - Is there a filename cap ?

Bob Stockler bob at trebor.iglou.com
Sat Nov 12 09:27:45 PST 2005


Mark Luljak wrote (on Sat, Nov 12, 2005 at 06:23:14AM -0500):

| The honourable and venerable John Esak spoke thus:
| > P.S. - Still, to help a little. I don't see what there would be to show as
| > an example. The @arrays simply hold the names (and extensions and long
| > names) of every file retrieved with your opendir() command. There is really
| > nothing to demonstrate further about that. You just set a counter and step
| > through the arrays doing whatever you want with whatever they hold.
| 
| I have a "silly" question, John.  The other day, you made the assertion
| that one need never use nextdir() again--ever.  That was if one uses the
| @arrays feature.
| 
| Is that a special array to fP?  Because fP's arrays in general are
| documented to being a maximum of 999 elements, are they not?  (Last time I
| checked with an fP developer, I was told they were.)

I've never seen it documented that arrays are limited to 999
elements.  In MENU EDIT II I dimensioned the array that holds
all menu names at 999, but only because I thought that was a
reasonable maximum number of menus to be expected in any one
PFMENU directory.

I just edited it to be 9999 and it executed without complaint.

I don't know that there is any limit to the number of elements,
and, as I recall Ken writing one time, there's very little cost
to dimensioning an array for more elements than one thinks will
be required - just in case more might be needed.

Bob

-- 
Bob Stockler  +-+  bob at trebor.iglou.com  +-+  http://members.iglou.com/trebor
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).


More information about the Filepro-list mailing list