Historically, commands that listed files, limited the display for one reason or another. LISTFILE in CMS showed only one minidisk at a time, 'ls' in Unix (Multics?) omitted 'dot-files', TSO limited you to the low-level qualifier or a single PDS. The main reason was to save console printer/display real estate, which was at a premium for interactive use.
SysFileTree() otoh, was never intended for interactive use and is more accurately regarded as a application interface to the file system. From that standpoint, SysFileTree() should, by default, return ALL files. Wildcards (RE's) and arguments may be provided to limit the information returned, but the basic behavior should be to return everything. Especially now that memory is cheap and I/O is not. IMHO, of course. -Chip- On 8/27/2012 22:06 Michael Lueck said: > Mark Miesfeld wrote: >> Opening up a RFE is the only way to get that enhancement. But, >> opening up a RFE is not guaranteed to get it. > I took that as a hint that a prior RFE was not on file. > > I had to hunt around for the "developer links" to the SF site. Finally found > a static link to the RFE tracker at the ooRexx site. ( > http://www.oorexx.org/support/ ) Through the many SF redesigns, most > all of the useful links have been lost at the main link ( > https://sourceforge.net/projects/oorexx/ ): > > My RFE as follows: > https://sourceforge.net/p/oorexx/feature-requests/482/ > > Sincerely, > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
