On Thu, Jun 25, 2009 at 6:17 PM, James Johnson<j...@iland.net> wrote:
> Consider the following:
James,
Sorry no one replied on the forum, every one is busy. This list is
easier to work with anyway.
I see what you're saying, I just had a chance to try it. I added a
line to print the current directory to better see what was happening.
On windows:
E:\ooTest\home>rexx dirA\progA
In progA. Current working directory: E:\ooTest\home
In progB. Current working directory: E:\ooTest\home
In dirB/progB
E:\ooTest\home>
So, progA is executing in dirA and the current working directory is
E:\ooTest\home
According to Rick:
This is the defined search order for external programs. The search path is
constructed from:
1) The directory holding the currently executing file
2) The current directory
3) The extension path
4) The REXX_PATH
5) The system path.
The directory holding the currently executing program is dirA, so it
seems to me that it should be expected to find dirB\progB.
As you noted that fails on Linux, and it seems like a bug on Linux to me:
[r...@osprey home]# rexx dirA/progA
In progA. Current working directory: /ooTest/home
6 *-* call (prog)
REX0043E: Error 43 running /ooTest/home/dirA/progA line 6: Routine not found
REX0417E: Error 43.1: Could not find routine "dirB/progB"
[r...@osprey home]#
--
Mark Miesfeld
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
