Sophie: lib64sablotron-devel-1.0.3-7mdv2010.0 x86

lib64sablotron-devel-1.0.3-7mdv2010.0.x86_64.rpm

<html><head><link rel=StyleSheet href='api-content.css' TYPE='text/css' MEDIA='screen'><title>.Debugging XSLT</title>
<script>
function navToEntry(entry) {
  window.location.href='api-' + entry + '.html';
}
function navToGroup(group) {
  var f = parent.frames['toc-container'];
  if (!f)
    window.open ('sparse-toc.html#' + group, 'toc_container');
  else {
    if (f.location.href.search('abc') != -1)
        f.location.href = 'sparse-toc.html#' + group;
    else
        f.location.hash = group;
  }
}
</script>
</head><body bgcolor='white'>
<!--
  -- HEADS UP!  This page was *GENERATED* by APIDOC,
  -- DO NOT EDIT THIS FILE BY HAND!
  -- See http://www.mozilla.org/projects/apidoc for information on APIDOC
  -- The original source file was sablot.xml
  -->
<h1 class='title'>Sablotron Guide and Reference</h1>
<center><table class='api-entry' width='100%' cellspacing='0'border='1' cellpadding='10'>
<tr><td class='entry-heading'>
<table class='entry-heading-table' width='100%' cellpadding='5'cellspacing='0'><tr>
<td class='entry-title' valign='center'><font size='+5'>Debugging XSLT</font></td>
<td class='entry-type' align='center' width='25%'>.General</td>
</tr></table>
</td></tr>
<tr><td class='entry-summary'>
<h4 class='entry-subhead'>Summary</h4>
Sablotron can be used as XSLT debugger.
</td></tr>
<tr><td class='entry-syntax'>
<h4 class='entry-subhead'>Syntax</h4><pre>
These commands can be used from the debugger command line:

Processed data:
&nbsp;&nbsp;&nbsp;data filename        - sets the data file
&nbsp;&nbsp;&nbsp;param name value     - sets the external parameter
&nbsp;&nbsp;&nbsp;P                    - lists all params
&nbsp;&nbsp;&nbsp;PP                   - clears all params
&nbsp;&nbsp;&nbsp;sheet filename       - sets the stylesheet
Breakpoints:
&nbsp;&nbsp;&nbsp;break filename:line  - sets the breakpoint
&nbsp;&nbsp;&nbsp;bstat                - shows breakpoint stats (total/enabled/break)
&nbsp;&nbsp;&nbsp;B                    - lists all breakpoints
&nbsp;&nbsp;&nbsp;condition num cond   - for the breakpoint NUM sets the condition COND
&nbsp;&nbsp;&nbsp;del num              - deletes the breakpoint NUM
&nbsp;&nbsp;&nbsp;disable num          - toggles the breakpoint number NUM
&nbsp;&nbsp;&nbsp;D                    - deletes all breakpoints
&nbsp;&nbsp;&nbsp;ignore num count     - ignores the breakpoint NUM for COUNT times
Execution control:
&nbsp;&nbsp;&nbsp;continue             - continues the execution
&nbsp;&nbsp;&nbsp;finish               - finishes the current node parent
&nbsp;&nbsp;&nbsp;kill                 - stops the processing immediately
&nbsp;&nbsp;&nbsp;next                 - goes to the next sibling
&nbsp;&nbsp;&nbsp;run                  - runs the processor
&nbsp;&nbsp;&nbsp;step                 - continues until the next element
&nbsp;&nbsp;&nbsp;templ                - continues until the next template executed
Evaluation:
&nbsp;&nbsp;&nbsp;eval                 - evaluates the XPath expression
&nbsp;&nbsp;&nbsp;x [list | num]       - examines the current context
Miscellaneous:
&nbsp;&nbsp;&nbsp;batch filename       - loads the command set for file
&nbsp;&nbsp;&nbsp;help                 - prints this help
&nbsp;&nbsp;&nbsp;output               - toggles output on/off
&nbsp;&nbsp;&nbsp;point                - shows where you are
&nbsp;&nbsp;&nbsp;quit                 - quites the debugger
</pre>
</td></tr>
<tr><td class='entry-description'>
<h4 class='entry-subhead'>Description</h4>
Run <code>'sabcmd --debugger'</code> to invoke the debugger. Then, you can trace 
execution of your templates. The only point, where the debugger can stop 
the execution is the element start.
<P>
</td></tr>
<tr><td class='entry-notes'>
<h4 class='entry-subhead'>Notes</h4>
<b>Abbreviations</b><BR>
You need to type as few letters to specify the command as is 
needed to recognize, what you mean. The most frequent command may 
be run with single letter not caring, whether another command 
starts with this letter. The `s' abbrev runs the `step' command 
rather the `sheet'.
<P><b>Emacs Integration</b><BR>
There is an Emacs library available. You may use it to debug
your stylesheets in Emacs directly. You need to grab the sabdbg.el 
from the Sablotron source tree and to add a couple of lines into
your .emacs file. Look at doc/misc/DEBUGGER file in Sablotron 
distribution for more details.
</td></tr>
<tr><td class='entry-seealso'>
<h4 class='entry-subhead'>See Also</h4>
<table class='seealso-table'>
<tr class='seealso-groups'><td>Groups</td>
<td>[ <a href='javascript:navToGroup("GROUP_.General")'>.General</a> ]</td></tr>

</table>
</td></tr>
</table></center><br>
&copy; 2002-2003 Ginger Alliance<BR><i>revision 03-06-30</i><BR>
<center>This page was generated by <a href='http://www.mozilla.org/projects/apidoc' target='other_window'><b>APIDOC</b></a></center>
</body></html>