From: David A. <dav...@gm...> - 2009-03-16 20:04:00
|
All - I am converting Mod_Rexx to Mod_ooRexx and I have run into a little problem. Mod_ooRexx is a self contained DLL. The old version called RexxRegisterFunctionExe to register its external functions. After the rewrite I have changed everything over to the oo methods and now I am not sure what the best method is to get these functions registered. I can deal with either an RexxInstance registration or some other method. Obviously I cannot use the standard function block for an external function library because Apache will be loading this DLL, not ooRexx. Any help would be appreciated. David Ashley |
From: Rick M. <obj...@gm...> - 2009-03-17 09:41:43
|
If you are converting over to RexxCreateInterpreter, then just directly provide the exit handlers when you create the interpreter instance. No need to use registered exit handlers any more. Look at what is done in the test code in orxinstance.cpp. Search for DIRECT_EXITS, which is where the exits are declared when the instance is created. These are direct callbacks without needing to go through all of the registration muck from the past. Also, exits created this way will be passed a RexxExitContext vector, which gives you access to the oo APIs in the exit context. Rick On Mon, Mar 16, 2009 at 4:03 PM, David Ashley <dav...@gm...> wrote: > All - > > I am converting Mod_Rexx to Mod_ooRexx and I have run into a little > problem. Mod_ooRexx is a self contained DLL. The old version called > RexxRegisterFunctionExe to register its external functions. After the > rewrite I have changed everything over to the oo methods and now I am > not sure what the best method is to get these functions registered. > > I can deal with either an RexxInstance registration or some other > method. Obviously I cannot use the standard function block for an > external function library because Apache will be loading this DLL, not > ooRexx. > > Any help would be appreciated. > > David Ashley > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Rick M. <obj...@gm...> - 2009-03-17 09:47:15
|
Oops, just as I hit send, I realized you weren't asking the question I was answering. You should be able to use the standard header function package header ok. To the Rexx loader, it shouldn't matter if your library has already been loaded by Apache. As long as it's resolvable and the special entry point can be located, Rexx should still be able to process the package. You can even specify that this package be loaded into the interpreter instance at startup using the LOAD_REQUIRED_LIBRARY option. Rick On Mon, Mar 16, 2009 at 4:03 PM, David Ashley <dav...@gm...> wrote: > All - > > I am converting Mod_Rexx to Mod_ooRexx and I have run into a little > problem. Mod_ooRexx is a self contained DLL. The old version called > RexxRegisterFunctionExe to register its external functions. After the > rewrite I have changed everything over to the oo methods and now I am > not sure what the best method is to get these functions registered. > > I can deal with either an RexxInstance registration or some other > method. Obviously I cannot use the standard function block for an > external function library because Apache will be loading this DLL, not > ooRexx. > > Any help would be appreciated. > > David Ashley > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Rick M. <obj...@gm...> - 2009-03-17 13:26:06
|
Hmmm, it might make sense to have an option on RexxCreateInterpreter() also to allow you to pass in a package entry table for "in-process" created packages. Not sure I'd want to add this to 4.0.0 because it might require a little reworking of some of the internals. Rick On Mon, Mar 16, 2009 at 4:03 PM, David Ashley <dav...@gm...> wrote: > All - > > I am converting Mod_Rexx to Mod_ooRexx and I have run into a little > problem. Mod_ooRexx is a self contained DLL. The old version called > RexxRegisterFunctionExe to register its external functions. After the > rewrite I have changed everything over to the oo methods and now I am > not sure what the best method is to get these functions registered. > > I can deal with either an RexxInstance registration or some other > method. Obviously I cannot use the standard function block for an > external function library because Apache will be loading this DLL, not > ooRexx. > > Any help would be appreciated. > > David Ashley > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |