opendir() - Is there a filename cap ?

[Fairlight]

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.)

If that's true, what if you had more than 999 files in a directory?  Ignore
the improbability a second--I'm asking if it's a potential limitation.
It might be improbable for those with a clue, but people have done
far stranger and less efficient things than dumping everything in one
directory.

If it's not a "special" array to fP, would one not need nextdir() again to
handle this scenario?

Just a thought.

mark->
-- 
There is no "I" in TEAM.
This would be the primary reason I've chosen not to join one.