And it doesn't make sense to put the onus on solving this on the interpreter. If it is desired to store binary code in an inherently text-based interface, then BSF4ooRexx should handle this be including a utility to perform the transform and then decoding the format before passing it to the interpreter.
Rick On Tue, Apr 9, 2019 at 9:10 AM Michael Lueck <mlu...@lueckdatasystems.com> wrote: > Greetings Rony, > > > Rony G. Flatscher wrote: > > > > However, since he started to use "rexxc" to compile/tokenize all of the > Rexx source files that comprise his elaborate application to shelter his > code, he has started to run into abends/errors 13.1. > > > "sheltering code" is the only reason he chose to compile/tokenize his > code... there is no requirement to do so when using BSF4ooRexx? > > While tokenizing ooRexx code seems appealing, I have seen time after time > where tokenized ooRexx code fails to cooperate. I personally have > "staunchly" decided against ever tokenizing any of my ooRexx > code. > > Thus asking if it is a requirement I have somehow missed that "Programs > utilizing / touching BSF4ooRexx MUST be tokenized." > > I am thankful, > > -- > Michael Lueck > Lueck Data Systems > http://www.lueckdatasystems.com/ > > > _______________________________________________ > 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
