Mark... I misunderstood the question, mostly because I was not thinking about how functions work.
I thought the question was more in the realm of the "call" where I as the programmer specified a rountine (file name) to be called. With the additional explaination - I agree, the "dir.rex" should be looked for before "dir" is. Does this change how a "call" would be resolved? if I said "Call dir" would you resolve to "dir.rex" before you went after "dir"? From a teaching point of view, I think it would be better to have a single "external naming" convention. i.e. whatever you reference as an external function or called routine will be found as "thingy.rex" before it is found as "thingy" Or by convention (or historical reasons) are these two separate issues? /s/ Bill Turner, wb4alm > The search we have been talking about is how the interpreter locates > the external routine dir(). More specifically, should it first search > for a file in the path with the name of "dir" exactly, or should it > first search for dir.rex. > > One of Rick's arguments is that on Linux you have binaries without an > extension and if you search for dir first, you pick up the binary. > (Because it is in the path.) When the user really wants dir.rex and > has used the extension to be sure it is not confused with the binary > of the same name. > ------------------------------------------------------------------------- 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
