On Wed, Jul 2, 2008 at 11:45 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> As part of the recent merge back into the trunk, I introduced the > concept of an "extension path" as an option to the APIs. > ... > So, this will make the search order for files to be: > > 1) The directory of the calling file (only for external function > calls), and only if the program was loaded from disk. > 2) The current directory > 3) The extension path > 4) REXXPATH > 5) PATH > > How does this sound to people? Should 1) and 2) be reversed so that > we always look in the current directory first? That sounds good. I don't think 1 and 2 should be reversed. I think in any application you are more likely to only change directory to do something that doesn't involve your application files. If you then need a file that is part of your application, the first place to look is your application location. -- Mark Miesfeld ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
