Re: [Oorexx-devel] Question ad .context~package in a required file, or: how to add a public routine dynamically and making it globally available in ooRexx 4.0 ?
Rony G. Flatscher wrote: Working on making the log4rexx framework (cf. http://wi.wu.ac.at:8002/rgf/rexx/orx18/log4r/) usable under ooRexx 4.0 I am stumbling over a problem that has to do with the intent of making a public routine dynamically available using .context~package and addPublicRoutine(...). This is the sequence of requiring files: 1. log4rexx.cls, which requires 1. log4rexx_logger.cls which requires 1. *log4rexx_init.cls* (defines dynamically public routines via .context~package~addPublicRoutine(...) ) and 2. log4rexx_appender.cls which requires 1. log4rexx_filter.cls and 2. log4rexx_layout.cls When running the prologue code of log4rexx_filter.cls one of the dynamically created routines (created in log4rexx_init.cls) named pp() is used, but ooRexx cannot find that routine in log4rexx_filter.cls. Is this intended by design (it seems so, just wanted to be sure) ? --- In the pre-4.0 version the undocumented .PUBLIC_ROUTINES environment symbol is used to define dynamically the public routine pp() in log4rexx_logger.cls sorry the above filename should read *log4rexx_init.cls* instead ! , and it is afterwards globally available. How could one achieve the same behaviour in ooRexx 4.0 (making sure a dynamically added public routine is available globally from then on, like it is the case with loading external Rexx functions dynamically)? ---rony -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad .context~package in a required file, or: how to add a public routine dynamically and making it globally available in ooRexx 4.0 ?
There's no mechanism for defining globally public routines in that manner. Rick On Thu, Oct 29, 2009 at 4:16 PM, Rony G. Flatscher rony.flatsc...@wu-wien.ac.at wrote: Working on making the log4rexx framework (cf. http://wi.wu.ac.at:8002/rgf/rexx/orx18/log4r/) usable under ooRexx 4.0 I am stumbling over a problem that has to do with the intent of making a public routine dynamically available using .context~package and addPublicRoutine(...). This is the sequence of requiring files: log4rexx.cls, which requires log4rexx_logger.cls which requires log4rexx_init.cls (defines dynamically public routines via .context~package~addPublicRoutine(...) ) and log4rexx_appender.cls which requires log4rexx_filter.cls and log4rexx_layout.cls When running the prologue code of log4rexx_filter.cls one of the dynamically created routines (created in log4rexx_init.cls) named pp() is used, but ooRexx cannot find that routine in log4rexx_filter.cls. Is this intended by design (it seems so, just wanted to be sure) ? --- In the pre-4.0 version the undocumented .PUBLIC_ROUTINES environment symbol is used to define dynamically the public routine pp() in log4rexx_logger.cls, and it is afterwards globally available. How could one achieve the same behaviour in ooRexx 4.0 (making sure a dynamically added public routine is available globally from then on, like it is the case with loading external Rexx functions dynamically)? ---rony -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question ad context
The only common denominator with the context is the RexxThreadContext. The thread context exists as a member of the other contexts, so you can pass that into common functions by using context-threadContext; Rick On Thu, May 14, 2009 at 3:10 PM, Rony G. Flatscher rony.flatsc...@wu-wien.ac.at wrote: When creating functions, procedures in native code, and expecting as an argument a context (one of ThreadContext, MethodContext, CallContext, ExitContext), then sometimes the same functionality is needed, but currently one must copy the entire body of the native function/procedure, because there seems to be no common context defined, which one could use instead. Or phrased differently: is it possible to define a function or a procedure in native code that expects as its first argument a context object, but one is allowed to pass any of the four ThreadContext, MethodContext, CallContext or ExitContext? Maybe some common context that would of course only have those functions that are available in all of these four contexts (somewhat a little inheritance hierarchy among the contexts)? ---rony -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
