Given the following scenario:

   1. an interpreter instance is created with RexxCreateInterpreter(),
      loading a native library "ABC" via the options argument, all
      loaded routines will be visible from thereon to every program that
      gets called
   2. using CallProgram() for some program "d.rex" which loads a library
      "DEF", then ends
   3. using CallProgram() for some program "g.rex" which loads a library
      "GHI", then ends
   4. using CallProgram() for some program "j.rex" which loads a library
      "JKL", then continues to run and via native code there will be
      callbacks to ooRexx that occur via another CallProgram() from
      native code

Questions:

   1. in 3. above: would all public routines and public classes that got
      loaded in 2. (e.g. via a "::requires DEF") be visible in 3. ?
   2. would the program in 4. see all public routines and public classes
      of the previously loaded libraries DEF and GHI ?
   3. for a callback from native code to Rexx in 4. above, which public
      routines/classes would be available to the callback, how would one
      be able to use (actually to fetch a reference to) those available
      public routines/classes?
         1. Scenario: the only thing available to native code currently
            is a reference to an ooRexx object that got stored in the
            native interface layer in an earlier call from a running
            Rexx program.
         2. It would be possible to fetch a reference to routine's
            package object and store that with the ooRexx object and
            then on callbacks use that. Is this advisable?
   4. if this is possible at all: how could one determine from native
      code whether a given library is loaded and if so, how could one
      get access to its routines and classes?

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

Reply via email to