Not necessary IMO, for the way ooRexx is structured now the ooRexx binary directory MUST be in the PATH Otherwise a generic rexx, would never be able to use rxqueue and rxsubcom
Using objects locating them by the relative position might be needed only to Guarantee consistency to the environment , multiple oorexx binary directories in the path It might be important to do that when loading the rexx image, less important for the rexx.cat ( got burned a couple of times because of that ) Enrico > On 5 Jan 2019, at 23:06, Rick McGuire <object.r...@gmail.com> wrote: > > > On Sat, Jan 5, 2019 at 4:54 PM Enrico Sorichetti via Oorexx-devel > <oorexx-devel@lists.sourceforge.net > <mailto:oorexx-devel@lists.sourceforge.net>> wrote: > > >> On 5 Jan 2019, at 22:32, Gil Barmwater <gbarmwa...@alum.rpi.edu >> <mailto:gbarmwa...@alum.rpi.edu>> wrote: >> >>> Actually, the path we really need is the location of librexxapi. > > > Why ? > > Because ooRexx can be used by any application. so the program for the process > need not be one of the oorexx executables. For example, if you are using > bsfoorexx from a java application, then the process will be the java process. > rxapi will not be found at that location. However, it will be found at the > same location of the librexxapi (which is the bit of code that does the > launching). > > Rick > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net <mailto:Oorexx-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
