You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/12/30 17:59:15 UTC

DO NOT REPLY [Bug 6079] - Enhancement request: trace modes

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6079>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6079

Enhancement request: trace modes





------- Additional Comments From David_Marston@lotus.com  2002-12-30 16:59 -------
Ideas: this could be a new -TM command line option or could be an enhancement
to -TT (and -TTC). You want to know when a mode is entered and exited. Use of
built-in rules (XSLT section 5.8) in a mode is not directly interesting, but
it's important to know when you are staying in a mode due to action of a
built-in template.

Implementation as part of -TT probably requires other enhancements to make a
clearer distinction between call-template and apply-templates. Example: put
the name='a' part of the message in parentheses when the template was invoked
by apply-templates, to signify that the name is being reported only for ease
of identifying which template was invoked. Likewise, one could put match='x'
in parentheses when a named template is invoked by call-template but happens to
have a match attribute as well.