I'm a software developer with ActiveState and we have been shipping
two IDE products for the last 6 months or so that include a debugger
based on Xalan C (1.0 and 1.1). I found an (old) screenshot at:
http://aspn.activestate.com/ASPN/img/shots/VisualXSLT_screenshot_large
.gif
Anway, I would like to contribute my debugger patches to core Xalan
and am sending this e-mail in the hopes that we can begin a discussion
on that topic.
My current patches (attached) are against Xalan C 1.1. A rough summary
of the functionality that I added is:
1. make I/O unbuffered so the debugger gets it's output immediately
2. preserve the match pattern of templates so that you can display
them in a callstack viewer
3. make the variable stack public and add a few methods to retrieve
variable information at any stack level and to infer the callstack
4. changes to the XalanSourceTreeContentHandler to collect source line
numbers
I would like to clean up the patches and update them for Xalan C 1.2.
Before I do that, we should probably discuss the design a bit. I am
imagining the addition of a new define, say XALAN_DEBUG_EXTENSIONS,
with my modifications contained within ifdefs. The changes to the
variable stack are reasonably extensive so a subclass is probably
warranted there (with an ifdef to decide if it should be used).
I am not adverse to significantly changing my implementation if a
better design can be found.
--
Brian Quinlan
Python and XSLT Developer
[EMAIL PROTECTED]
ASPN - ActiveState Programmer Network
Essential programming tools and information
http://aspn.ActiveState.com/ASPN
xalan.diff
