Could grab some time to test adding a package to the context of another routine
from native/C++ code.
Here is the basic outline:
1. a routine object is created for
::requires BSF.CLS
which sets up all kind of public routines and classes among them one public
routine named "pp";
then the message "call" is sent to the routine object, followed by the
message "package" to
obtain its package which makes those public routines and public classes
available.
2. another routine object is created for the following code:
*
say pp("hey") -- pp() defined in BSF.CLS
say pp(test())
::routine test public
return "this is from the public routine test()"
There are two different scenarios tested so far which both lead to errors:
1. when creating the second routine object supply the first routine's
package as third argument
[r=.routine~new(name,code,context)]
2. when creating the second routine object, get its package object and
send it with the
addPackage message the first routine's package to inherit its public
routines and public classes
In both scenarios described above the routine pp() from BSF.CLS is found and
used when
calling/running the second package object. However the code in the second
routine object cannot find
its own public routine "test()"!
The error message is:
Error 43 running rexxPackage2 line 2: Routine not found
Error 43.1: Could not find routine "TEST"
It seems that in both scenarios the first routine object's package /replaces
/the package created
for the second routine object rather then inheriting from it.
Before filing a bug in the tracker system I just would like to be sure that I
am not
misunderstanding the mechanics here.
---rony
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
