Greetings ooRexx'ers,

Rick McGuire wrote:


On Wed, Sep 4, 2024 at 12:07 PM Erich Steinböck <erich.steinbo...@gmail.com 
<mailto:erich.steinbo...@gmail.com>> wrote:

    Ok, thanks.

    As, except for tracing, there seems to be little value in labels that 
cannot be branched to, should we completely disallow them already in the 
translation phase, like it is done for labels within
    INTERPRET?

    One of the open bug reports claims we should allow `label: THEN` within an 
IF (it's the ANSI argument) and I wonder whether we really want a fix with so 
lottle vealue.


I think I'd be in favor of not allowing them at those locations. I agree there 
is very little value in having them there, and the control structure of how 
instructions are linked together probably
would not accommodate that well.



This topic of an IF block being contained within a "Do we intentionally allow 
SIGNAL/CALL into IF/DO/LOOP?" context...


Is this similar to the run-time environment of a dynamically created method? 
Back on Object Rexx 2.x and 16 years ago, a coworker built a Persistence class 
architecture to encapsulate a class wrapping
the old official DB2 Rexx driver which shipped with IBM DB2. Some prior 
developer had contributed a quite nice Object Rexx class to encapsulate the DB2 
Rexx DLL calls. Said coworker I worked with went
a step further and wrapped that class into a Persistence class. That class 
would dynamically create class methods / attributes on the fly to match with 
the table schema of a given table. I recall he
ran into a funky operating environment existed while code was running in the 
dynamically created method. However said dynamically created method could 
itself call static code, and then proper variable
exposure would resume. So he ended up defining statically methods meant only to 
be called by the dynamically created methods... a call would go there first 
matching the dynamically created methods to
match up with a given table schema, and then that would call back to static 
code.... one of those methods intended only to be called by dynamically created 
methods. The whole thing worked fabulously.

So my question... is what Erich was inquiring about at all similar to the funky 
/ primitive environment those dynamically created methods run Rexx code in?

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

Reply via email to