Guenter,
well done!
> 1. Are the functions SablotSetBase and SablotSetBaseForScheme new or
> are they old? Will they be maintained? The sabcmd program has a
> command line option to set some base, but this is never done (in
> version 0.44).
They are old, but should be supported. There were som discussion on this
topic, Tom has to say more.
> 2. What are SablotSetInstanceData() and SablotGetInstanceData() for?
> Normally I would create a struct containig all the stuff needed in my
> Python object, including the sablotron processor.
>
> One situation that comes to mind: I could store the
> address of the Python object with SablotSetInstanceData() and retrieve
> it when I get called from Sablotron giving me tha processor only (and
> I need the Python object). Where can this happen? Looks like
> handlers have there own private data pointer so I don't need it there,
> right?
Yes, the handlers were at the beginig of SetInstanceData life.
> 3. Why is the first arg to SablotSetBaseForScheme declared "void *"?
> Should we pass NULL-Pointers here?
It should be SablotHandle, of course (which is actually void* :)
> 4. Are there any plans for further APIs that allow me to extend XSL
> and more important, XPath (eg. I want to write simple string
> conversion functions in Python and use them in XSL)?
Tom?
> 5. What else besides the converted output can be put in the ResultArgs
> and how? Is there a way to retrieve error messages with the %ses
> replaced by their values?
As far as I know, in this time is result buffer (output) the only one
accessible via GetResultArgs. To trap the error messages use the message
handler.
I do not understand the last question.
Regards
Pavel
--
Pavel Hlavnicka
Ginger Alliance Ltd.
Prague; Czech Republic
