Re: [xslt] Relase of xsldbg-0.7.9, : release of xsldbg-0.8.1

On Fri, Nov 30, 2001 at 04:24:08AM -0500, Daniel Veillard wrote:
>   Basically I'm tempted to do somthing similar to the SAX
> interface of libxml. The upper layer provide a "driver" block
> containing all the callback routines. And when of the routines
> are called from the lower level, it checks if the current callback
> is non-NULL and simply call it.
>   Very simple, very flexible, and adds only a single entry point
> to the library.

  Okay following feedback from Keith, I implemented that strategy.

libxslt does not requires libxsltbreakpoint anymore. The mechanism
is based on the following:

#include <libxslt/xsktutils.h>

struct mycallbacks {
    xsltHandleDebuggerCallback debuggercallback;
    xsltAddCallCallback addcallback;
    xsltDropCallCallback dropcallback;
} = {

  where mydebuggercallback myaddcallback and mydropcallback are the debugger
implementations of xslHandleDebugger(), xslAddCall() and xslDropCall()
the fsimplest in a first time being to simply grab the code from the
existing libxsltbreakpoint.

  Then just call 
    xsltSetDebuggerCallbacks(3, &mycallbacks);
ajust xslDebugStatus (now exported directly from libxslt)
and you should be all set.
In case we realize later that we need more callbacks, then this can
be plugged in libxslt. If the installed library has not been upgraded then
the call will simply fail, but normal processing won't break.

  What is left to do is:
    - Keith to check that the new interface works for him
    - me to then strip out libxsltbreakpoint content, keeping a single C
      module providing the same set of empty APIs for the compatibility
      library, and check this in practice
    - others to test that the problems they were experiencing due to the
      libxsltbreakpoint dependancy are solved


Daniel Veillard      | Red Hat Network  | libxml Gnome XML XSLT toolkit | Rpmfind RPM search engine

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]