On Wed, 23 Oct 2024, at 14:31, Josep Maria Blasco wrote: > There are some ongoing changes to the ooRexx interpreter that will strongly > affect the language definition, in such a way that the 5.1.0 release may > end up implementing a version of the language that does no longer allow us > to hold true what is asserted in the landing page for the project: > > "Home of the Open Object Rexx Project. ooRexx is the open source version of > IBM's Object REXX Interpreter. *It is upwardly compatible with classic REXX > and will execute classic REXX programs unchanged*. The project is managed > by the Rexx Language Association".
I don't think it makes much difference to me which approach is taken in the new interpreter, for anyone writing new code. But it seems crazy (to me) to deliberately prevent people from running older programs. So, I'd want to know: how can a user turn off the new fussiness of the new interpreter? Will there be an "::options" directive, or even a first(?) use of the "options" keyword instruction which switches off either pre-run syntax checking which objects to labels in funny places, or runtime objections to branches to such labels? Some users might be running code that they don't have source for - ie they've been supplied with the output from rexxc. Why should they not be able to continue to run their programs? I giess such users would need to be able to supply a parameter to the interpreter (as not able to insert ::options|options into the source). Some users, even if they do have source code, will not have the technical knowledge to edit it correctly to remove 'invalid' labels? -- Jeremy Nicoll - my opinions are my own. _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
