I just want to add that when I tested the sample program, I got different results than the author of the bug. Consider that on Linux/Unix/MacOS that the current directory is not automatically searched, unless it is in the environment PATH variable. Perhaps people that are used to Windows add the current directory to PATH, but people that "grew up" on UNIX have been trained not to do that for security reasons.
In the sample program there are four calls to HEY. My results under ooRexx 4.0.1 were: Hello! Hello! ERROR HEY not found ERROR HEY not found This was due to direcories 'a' and 'b' not being in my PATH. While my results under ooRexx 4.2.0 were: Hello! Hello! Hello! Hello! My personal opinion is that ooRexx 4.2.0 is working as the documentation indicates it should work. Also, I think that the way it is documented to work is the way I would like it to work, if I had a choice. The next question is, is there a workaround for the person who entered the bug report. Could the person alter the PATH in the environment to attain the desired results? Bruce On Oct 31, 2011, at 10:54 AM, Chip Davis wrote: > Yes, but that was simply a bug report against 4.0.1 that was applied > to 4.1.0. I found what looks like the original RFE to change the > behavior of 3.2.0 to always look in the caller's directory first. > > RFE1666636 seems to be the point at which ooRexx 'Call' routine lookup > diverges from IBM Object REXX, and Classic Rexx for that matter. > > THAT is where the the trail ends. I can find no reference to that RFE > in any of the Tracker or Forums files. It shows up in five postings > to the Oorexx-svn mailing list. Those postings are nothing but SVN > update logs which include the line: > > + * 1666636 - Add source of caller to function search order. > > The earliest mention of 1666636 is as an RFE update 4087 to 3.2.0 on > 2009-02-06 03:11:42 +0000 (Fri, 06 Feb 2009). > > I can find no information on who submitted the RFE, the rationale > behind it, or any discussion of its merits, necessity, unintended > consequences, or anything else. I have not gone so far as to checkout > the 3.2.0 source to see if there is any commentary in the code, and > frankly that shouldn't be necessary. > > -Chip- > > On 10/31/11 13:31 Uli Zinngrebe said: >> On Sunday 30 Oct 2011 05:54:21 Mark Miesfeld wrote: >>> On Sat, Oct 29, 2011 at 9:38 PM, Mark Miesfeld <[email protected]> wrote: >>>> On Sat, Oct 29, 2011 at 3:46 PM, Chip Davis <[email protected]> wrote: >>>> >>>> >>>> It's doubtful to me that the behavior changed between 4.0.1 and 4.1.0. >>>> But, he did attach a test program, so I'll give it a try. >>> Well, that was a surprise, the behavior did change between 4.0.1 and >>> 4.1.0. I got this result under 4.0.1: >>> >> >> Are you aware of bug ID 2978925 ? >> (External search path: skips "same" takes "current" directory) >> >> Cheers, Uli >> >> ------------------------------------------------------------------------------ >> Get your Android app more play: Bring it to the BlackBerry PlayBook >> in minutes. BlackBerry App World™ now supports Android™ Apps >> for the BlackBerry® PlayBook™. Discover just how easy and simple >> it is! http://p.sf.net/sfu/android-dev2dev >> _______________________________________________ >> Oorexx-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > ------------------------------------------------------------------------------ > Get your Android app more play: Bring it to the BlackBerry PlayBook > in minutes. BlackBerry App World™ now supports Android™ Apps > for the BlackBerry® PlayBook™. Discover just how easy and simple > it is! http://p.sf.net/sfu/android-dev2dev > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
