[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: Managing debug logging in complex transforms: what
Subject: Re: Managing debug logging in complex transforms: what do people do?
From: "Imsieke, Gerrit, le-tex" <gerrit.imsieke@xxxxxxxxx>
Date: Mon, 24 Mar 2014 21:50:53 +0100
|
+1 for an XSLT function current-mode()
On 24.03.2014 21:46, Eliot Kimber wrote:
I'll have to think about the details of <xsl:message> more before I can
answer the XSLT 3 requirements question.
But something I'd really like is a way to get the current mode name so I
can put it in the message, without having to pass it as a second debugging
tunnel parameter.
E.g.:
<xsl:template mode="#all" match="*">
<xsl:message> + [DEBUG] {$modeName}: Unhandled element <xsl:value-of
select="concat(name(..), '/', name(.))"/></xsl:message>
</xsl:template>
Where here "{$modeName}" is a placeholder for some way to reflect the
current mode.
Cheers,
E.
bbbbb
Eliot Kimber, Owner
Contrext, LLC
http://contrext.com
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
RSS 2.0 |
|
Atom 0.3 |
|
|