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 wrote: > Working on making the "log4rexx" framework (cf. > ) usable under ooRexx 4.0 I > am stumbling over a problem t

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. > ) 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 ad

[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 ?

Working on making the "log4rexx" framework (cf. ) 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 seq

Re: [Oorexx-devel] Question ad context

Rick McGuire wrote: > 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; > Ah, thank you very much! ---rony

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 wrote: > When creating func

[Oorexx-devel] Question ad context

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 se