W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2016

[Bug 29983] [XSLT30] Scanning expressions and function calls

From: <bugzilla@jessica.w3.org>
Date: Sun, 06 Nov 2016 17:25:21 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29983-523-7iBwCk0UYG@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29983

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Thanks, that helps and I remember now (the discussion, the whiteboard). Do you
think it makes sense to enlighten the section by explaining how we got to those
rules, in other words, add something along the following lines?

Note:

These rules grab those situations where an expression can be rewritten as a
pattern and therefor can assess upon visiting a node whether or not it fits
this pattern, which effectively makes it streamable....

(no wordsmith here, doesn't sound too clear to me, maybe something better? ;) )

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 6 November 2016 17:25:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:03 UTC