Maybe exposing all of bin/ would be too much. I could try to refactor the parser so that only the utilities like highlight, elements, etc and the parser package itself can be found, in the same way as yaml.cls or json.cls. The real bulk of the package could reside in its own subdirectory.
Josep Maria Missatge de Rony G. Flatscher <[email protected]> del dia dc., 12 d’ag. 2026 a les 11:52: > RFE # 878, <https://sourceforge.net/p/oorexx/feature-requests/878/>, > proposes to add Jose Maria > Blasco's Rexx parser to the ooRexx distribution. > > Here is the link to the current homepage of the Rexx parser: > https://rexx.epbcn.com/rexx-parser/ > > The Rexx parser is included in net-oo-rexx already: > https://github.com/RexxLA/net-oo-rexx/ > > The main reason for this RFE is the incredible utility it offers for many > different application > needs. One example is the ability it supplies for syntax coloring of the > Rexx code in the ooRexx > documentation, which can be automated with tools supplied with the Rexx > parser like (a very > flexible) syntax highlighting. > > The Rexx parser would allow for creating apps that are able to > cross-reference variables, > attributes, methods, classes, routines, and the like; another possibility > would be to use it for > reformatting (oo)Rexx code to different styles, and much more, confined > only by the phantasy and > creativity of (oo)Rexx programmers. > > Any suggestions on how to install such a toolset on the different > platforms? Just put the path to > Rexx parser's bin directory to the PATH environment variable on all > platforms? > > Any comments? > > ---rony > > > > > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
