Greetings Rony, Rony G. Flatscher wrote:
What would be a "dynamic method" for you and what would you expect of it and why?
Starting with your last question first.... A Persistence framework builds run-time code dynamically to match up with physical database table schema. We make use of calls to self~SetMethod() to build out the needed class object code at run-time matching up with the table schema.
What do you assess to be an "odd environment" (and why would it be odd for you?) "which dynamically created methods execute their code in" ? Can you explain? What would be a "dynamic method" for you and what would you expect of it and why?
Calling from the main class code into these dymaically created methods lands execution in some sort of a jailed environment. Code there does not have access to objects visible within the real class object, nor access to loaded Rexx DLL's. However, we found if we call back to another static method within the class (meant only to be called by these dynamically crated methods) then the correct environment visibility is restored. So we ended up doing just the minimal code in those methods defined with self~SetMethod() and then from there call to one of the special methods intended only to be called from a self~SetMethod() created section of code. The run-time environment of methods created with self~SetMethod() seem funky. 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
