Thanks for the swift reply!
Steve Baker wrote:
>> * are there any ways to bundle a group of extension functions, let's
>> say a math-package, and to import it more library like?
>
> I deliberately left that stuff up to the application. There may be very
> good reasons why an application developer might not WANT the script
> programmer
> to be able to pull in a particular library...for example, that might allow
> the script to do things that would violate network security or something.
Sorry, I was equivocal here, I completely agree that it may be against
the general design to allow the import from the script side. My point
was from the C++ side, I rather wanted to bundle math and stdio
interface functions in extra files separated from application specific
interfaces, in order to make them more easily reusable. As far as I
understand, currently I would have to combine a large array of
pslExtension objects by hand quite cumbersomely. To my mind it would
be more elegant to provide these arrays already in the respective
extension c++ library files, and do something like:
pslExtension pslExtMath[], pslExtStdio[];
// defined in extra collection files
pslExtension extensions [] = { { NULL, 0, NULL } } ;
// defined rather locally
pslProgram *prog_1 = new pslProgram ( "code1" ) ;
prog_1 -> import(pslExtMath);
prog_1 -> import(pslExtStdio);
prog_1 -> import(extensions);
prog_1 -> compile ( "data/test.psl" ) ;
...
>> The 1.8.1 examples and documentation package seems to lack the
>> documentation?
>
> Really?
I just downloaded it again, the
plib_examples-1.8.1.tar.gz/plib_examples-1.8.1/doc subfolder just
contains a CVS folder, nothing else, or am I looking at the wrong place?
Thanks and best regards
Gerald
|