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

[Bug 30015] TransformWithExpr and ArrowExpr grammar entries conflict for Update Facility 3.1

From: <bugzilla@jessica.w3.org>
Date: Sat, 19 Nov 2016 14:51:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30015-523-lZ0vPIw0b1@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30015

Michael Dyck <jmdyck@ibiblio.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jmdyck@ibiblio.org

--- Comment #1 from Michael Dyck <jmdyck@ibiblio.org> ---
Your suggested EBNF allows
    $x transform with {} => upper-case()
and not
    $x => upper-case() transform with {}

I.e., it's the solution that you refer to as `TransformWithExpr > ArrowExpr`,
whereas you said that `ArrowExpr > TransformWithExpr` would make more sense.

So it's unclear which you actually prefer.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 19 November 2016 14:51:13 UTC

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