Mark Miesfeld wrote: > I agree with you that the reasonable default for the "S" flags would > have been all files. But it wasn't implemented that way on Unix-like > systems. It's been that way for a long time, probably forever. If we > suddenly changed the behavior, programs like the ones Michael has > already written and has been using would no longer produce the same > results. > > Is that okay to do just because the original default wasn't reasonable? > > That's the question I'm interested in.
I vote in favor of leaving the API alone for legacy support and band-aid it with an additional switch. I do not want another big-bang upgrade pain like was felt with the ooRexx FTP class early on. I recall something in that API changed and programs were not portable across the hump. I had to decide to run the new ooRexx, hurry to change my code, and never to go back to older versions. Until I get around to upgrading all places I need to "double SysFileTree" I would like that legacy code not to suddenly really find ALLLL files with '*' search pattern. That would cause duplication of the result set, slow down the program execution, etc... Implement it the same way the L option was added to SysFileTree long long ago. "Oh, I can receive four digit years from SysFileTree. How nice, I will use that." Sincerely, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
