On Thu, Jun 26, 2008 at 7:39 AM, David Ashley <[EMAIL PROTECTED]> wrote: > > I don't think that we should even be considering this option. In the Unix > world file extensions are meaningless to the operating system. They are only > useful to a human. The OS could care less. So I don't think we should be > making assumptions about the default/possible extensions that could be in > use on the system.
David, This is for the search where an external program file is called as a function. Object Rexx has always had this functionality. From the docs on the search order: 5. Rexx functions in the current directory, with the current extension. 6. Rexx functions along environment PATH, with the current extension. 7. Rexx functions in the current directory, with the default extension (.REX or .CMD). 8. Rexx functions along environment PATH, with the default extension (.REX or .CMD). The case that got dropped when Rick was reworking the code was found by some or your excellent test cases. <grin> Take for example: ::method "test_18" -- Create our external functions. path = .ooRexxUnit.dir || .ooRexxUnit.directory.separator src = .array~new() src[1] = "return arg(1)" call createFile src, path'SCIIF18' -- now do the tests If SCIIF18(1) Then r=1 ; Else nop self~assertSame(r, 1) -- now remove the external functions call deleteFile path'SCIIF18' -- 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
