- From: <bugzilla@jessica.w3.org>
- Date: Fri, 10 Jul 2015 13:18:04 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28933 --- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> --- (In reply to Michael Kay from comment #1) > Note, this change means it is no longer possible to control assertion > enablement in this kind of way: > > <xsl:variable name="ASSERTIONS_ON" select="true()" static="true"/> > > <xsl:assert test="2=2" use-when="$ASSERTIONS_ON"/> Interesting. But I have always found it extremely cumbersome to have the requirement to switch assertions on/off by having to use use-when on each and every xsl:assert, which kind-of violates the whole idea behind assertions as being a light-weight simple and quick approach to asserting your code. Your code suggests the requirement or wish to be able to switch assertions on/off in the stylesheet, which, on the WG meeting was considered a non-necessity. Which brings us back to the idea of having an enable-assertions as a global attribute on xsl:stylesheet and xsl:package, with scope to the current package. I'm still somewhat silently rooting for it ;). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 10 July 2015 13:18:08 UTC