Rick McGuire wrote:
> On Mon, May 4, 2009 at 11:43 AM, Rony G. Flatscher
> <rony.flatsc...@wu-wien.ac.at> wrote:
>> ... cut ...
>> Question 1: Is there a way to get to the RexxInterpreter instance pointer or
>> RexxThreadContext pointer (which would allow for finding its RexxInterpreter
>> instance) from within an external classic Rexx function?
> No there is not.  However, if you just add BsfLoadFuncs() to the list
> of function defined in the BSF4Rexx() package and make it a NOP when
> called, then things will appear to behave the same way. This is the
> same approach that's been taken by packages in the interpreter itself
> that have been converted to the new package format.  For example, see
> what the rxsock library is doing in the interpreter build.
>> If there was such a function, then it would be possible to let
>> "BsfLoadFuncs" be implemented in the classic style, but load from the code
>> there the library containing the new typed REXX_ROUTINE functions. This
>> would allow replacing the rest of the external functions by new
>> REXX_TYPEDROUTINEs, which I would prefer over the classic style seeing how
>> easy it is to use the new 4.0 APIs.
> If you implement the suggestion I made above, this will work just
> fine.  The rxmath package is a good example.  It still has a
> registration routine, but all the functions are defined using the
> typed format.  There is no need to register special stubs.

Just turned to the rxmath package (learned that even the loader function
could be defined to be of new type) and saw no explicit library loading,
hence two little questions:

    * does using "RxFuncAdd(...)" cause ooRexx to automatically load the
      given DLL at that time or when the added external function gets
      executed the first time?
    * Does ooRexx load all external routines defined in the
      RexxPackageEntry that is used with the OOREXX_GET_PACKAGE(pkgName)
      automatically at the time of loading the DLL?


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