Re: [XQuery] IfExpr should allow an optional else clause

The FLWOR construct is a new syntax which unlike IfExpr is a borrowed
grammar. FLWOR does not contend with a mindset precedence and
I don't think making the else clause optional necessitate a change on FLWOR.
Making the else clause optional does not in any way make
IfExpr any less as an expression. Making it mandatory does not
enhance its functional value either (even perceptively) but its redundancy
becomes a syntactic nuisance.

The balance to enforce IfExpr with a mandatory else clause doesn't feel
right. My sincere apologies for the seemingly painful revisit of IfExpr
but please reconsider.


----- Original Message ----- 
From: "Kay, Michael" <Michael.Kay@softwareag.com>
To: "Jonathan Robie" <jonathan.robie@datadirect.com>; "TAN Kuan Hui"
<kuanhui@xemantics.com>; <public-qt-comments@w3.org>
Sent: Thursday, January 29, 2004 1:36 AM
Subject: RE: [XQuery] IfExpr should allow an optional else clause


>
> For just this one expression, I agree - but if we went that
> way, we should
> do the same for other expression types, including FLWOR expressions.
> Working this through...it seemed to make the language more cumbersome.
>

I agree - since there are many ways a FLWR expression can start, it's
hard to come up with a closer that feels right.

Michael Kay

Received on Wednesday, 28 January 2004 22:03:16 UTC