Greetings Rick,
Rick McGuire wrote:
Doing some rework on SysFileTree to clean it up
Much thanks!
First, the question of long file names. Unfortunately, because people might be using positional parsing on the returned string, just unilaterally increasing the size doesn't really work. It's fairly
trivial to add an option to request the longer length. I'm using "Z" for now, unless there's a better suggestion.
So you are worried if programs were written to expect no longer than a string of n, then strip that string to clear the white space, such programs would chop the filename string if we were to suddenly
lengthen it?
If so, I see your point, "Z" sounds good... "z/OS" ;-)
Secondly, the unix version of SysFileTree requires a specific option for caseless searches. However, the Mac normally uses a caseless file system. I'm thinking the default for the Mac should be
caseless too.
I would agree, vote for keeping SysFileTree running similar to the Host OS.
I recall much aggravation on Linux trying to get a complete SysFileTree including nested dot leading directory names, and dot leading filenames. On a note of keeping SysFileTree similar to OS core
utilities, it is actually easier to obtain a complete file tree with command line Linux tools than SysFileTree. What is your opinion to softening the sharp edge on the Linux dot leading name concept?
Currently on Windows, command line verses SysFileTree are very similar... where as on Linux there is a wider gap in functionality.
I am thankful,
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
