On Thu, Jun 25, 2009 at 6:17 PM, James Johnson<j...@iland.net> wrote:
>
> 1) Open a terminal session. Your are in some directory that we will call
> "home".
> 2) Within the "home" directory is a sub directory "dirA".
> 3) Within "dirA' is a sub directory "dirB".
> 4) Within "dirA" is a rexx program named "progA".
> 5) "progA" calls "progB" which resides in "dirB".
Okay, after sleeping on it, I'll revise what I said.
When progA calls progB, it searches a *path* for the file progB. The
first entry in that path is the *directory* dirA. progB is not in
dirA. Nor is progB in any other directory in the path. So it
shouldn't be found on either Windows or Linux.
So the bug is that it is found on Windows. The bug is not that it
should be found on Linux.
And in fact if you run your example under 3.2.0 on Windows, progB is not found:
E:\ooTest\home>rexx -v
Open Object Rexx Interpreter Version 3.2.0
Build date: Oct 30 2007
Copyright (c) IBM Corporation 1995, 2004.
Copyright (c) RexxLA 2005-2007.
E:\ooTest\home>rexx dirA\progA
In progA. Current working directory: E:\ooTest\home
6 *-* call (prog)
Error 43 running E:\ooTest\home\dirA\progA line 6: Routine not found
Error 43.1: Could not find routine "dirB\progB"
E:\ooTest\home>
Now personally, I sort of feel that:
* the first attempt to find progB should be to treat the target of the
call (dirB/progB) as a relative file name to the directory that the
executing program resides in.
* the second attempt to find progB should be to treat the target of
the call (dirB/progB) as a relative file name to the current working
directory.
* then search the paths:
3) The extension path
4) The REXX_PATH
5) The system path.
However, as your example shows, the behavior you want was not present
in Windows ooRexx 3.2.0, so that would be a change in behavior.
And, since Rick hasn't responded to this, I sense that he is opposed
to a change here.
You could open up a Request For Enhancement for the behavior you want.
Maybe it would be accepted and implemented in a future version.
--
Mark Miesfeld
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
