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
