On Thu, Jun 26, 2008 at 7:41 AM, Rick McGuire <[EMAIL PROTECTED]> wrote: > I'm of two minds on this one. That *could* be the appropriate place > to insert the search, but then I'm reminded of the problem that Mike > Cowlishaw encountered when I first implemented the (more) > case-insensitive searches on Linux. Suddenly, we started picking up > real binary executables that happened to have the same names as Rexx > programs, with fairly disastrous results. That would sort of argue it > should be the option of LAST choice, to ensure the appropriate Rexx > programs are located first. > > And, the more I think about it, if you are writing an application that > is using ooRexx as a macro language and have a list of extensions you > wish to have picked up, then those should be checked BEFORE an > extensionless file to ensure the version for your targetted > environment gets used. That, I think, is enough to convince me it > should be last in the order.
Both of those are good arguments. And I really agree. The other argument is that I think it is a rare use case, that happened to get used a lot in the test cases. If most people don't write external functions as a program file, without an extension, then it should be last simply because it would rarely be encountered. -- Mark Miesfeld ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
