Re: [xslt] Variable setting with libxslt, possible API features, and, update of xsldbg



On Fri, Sep 21, 2001 at 02:59:20AM +0000, k_isdale@tpg.com.au wrote:
> Hi all,
> 
> At this point I've mentioned my thoughts on the 
> break point API for basic break point setting. It 
> would be good to be also be able to change 
> variables when running a debugger session. I 
> think it's a bit tricky, so I ask for suggestions 
> on what could be used to achieve changing 
> variables. An algorith would be great but some 
> hints would be good. Otherwise its difficult to 
> define that API interface if there is no clear 
> method of achieving this. :-(

  int
  xsltSetVariable(xsltTransformContextPtr ctxt,
                  const xmlChar *name,
                  const xmlChar *ns_uri,
		  xmlXPathObjectPtr value);

  xmlXPathObjectPtr
  xsltGetVariable(xsltTransformContextPtr ctxt,
                  const xmlChar *name,
		  const xmlChar *ns_uri)

  and 
  xsltSetGlobalVariable()
  xsltGetGlobalVariable()

Only local variables from the current frame would be
accessible, maybe something better is needed.

> I also think it worthing considering if the 
> libxslt library would support "watching" 
> variable, and setting conditions on the "break 
> points". The first I think is outside the scope 
> of the libxslt library. The latter , I'm not 
> sure?  

  I would wait for this.

> The major changes to the libxml patch are that 
> debugXML.c has now got
>    long xmlGetLineNo(xmlNodePtr node) 

  Makes sense

> The major changes to the libxslt patch are in
>   breakpoint.c where a "breakpoint number" is 
> used whereever possible to simplify usage and get 
> better efficiencies.
> int xslAddBreakPoint(xmlChar *fileName, int 
> lineNumber)
> int xslDeleteBreakPoint(int breakPointNumber)
> xslFindBreakPoint(xmlChar *fileName, int 
> lineNumber)
> xslEnableBreakPoint(int breakPointNumber, int 
> enable)
> xslLookupBreakPoint(int breakPointNumber )
> xslIsBreakPointNode(xmlNodePtr node)
> xslIsBreakPoint(xmlChar *fileName, int lineNumber)
> 
> Call stack methods should be changed to follow 
> the same style of parameters and have a method 
> that returns the "callStack" object.

  I'm really busy this week-end, I will probably not
have time to look at it further before end of next week.
In the mean time please make sure that your suggested
patches follows the comment conventions of the rest of libxml
and libxslt code (wasn't the case when I looked a few days ago).

Daniel

-- 
Daniel Veillard      | Red Hat Network http://redhat.com/products/network/
veillard@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/





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