Rick McGuire <[email protected]> wrote: > Because it IS part of the search order. But that really only applies to > the searches using file extensions. This is not done with the "raw" name > because it resulted in too many false positives with non-rexx programs > (this was actually added at one point, but it had to be backed out). In > the poster's situation, he's created his files without extensions, so only > the matching case is used. If he renamed them to have a ".rex" extension, > then there is much less case insensitivity involved.
Ok, that makes sense. I've raised a Documentation bug (hopefully correctly, I don't understand te new ticketing software), so maybe someone can clarify this in future manuals. Separately from the doc issue, is there any point in making a feature request that in some way - maybe a trace option? - one could have oorexx tell you in succession all the places it looked for a specific-named file? The whole process strikes me as being mind-bogglingly complicated and although descriptions go some way to describe what's being taken into account, actually having a clear understanding of precisely which name of something is being looked for and in what location is ... hard. I'd like to see output something like: trace Search Call NoSuchFunction() 3 *-* Call NoSuchFunction() 'NOSUCHFUNCTION' not found in REXX_PATH 'NOSUCHFUNCTION' not found in PATH 'NOSUCHFUNCTION' not found in ... 'NOSUCHFUNCTION.XYZ' not found ... etc with whatever details are appropriate, preferably showing the exact case and file extensions looked for in the order they are tested in. For things like search in REXX_PATH or PATH, if the oorexx code itself identifies the separate directories involved then I'd rather see those enumerated in the trace output, but if it just uses some system function to search for file x on path y then the environment var name would be enough detail. For a function call where the search is successful I think the trace output shouls also show the location where the item was found. -- Jeremy Nicoll - my opinions are my own ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
