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


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

Reply via email to