Re: IfExpr has a mandatory else clause

"TAN Kuan Hui" <[email protected]>
Newsgroups gmane.comp.web.query-languages
Organization Xemantics Software Pte Ltd
Message-ID <000a01c3e46c$3905ace0$4445bada@pinecone>
Appreciate the clarification.

However making the else clause optional does not make the
IfExpr expression less of an expression does it ?
Implicitly returning an empty sequence in the absence of an
else clause is not intuitive ?

----- Original Message ----- 
From: "Kay, Michael" <[email protected]>
To: "TAN Kuan Hui" <[email protected]>; "Bas de Bakker"
<[email protected]>; <[email protected]>
Sent: Monday, January 26, 2004 7:38 PM
Subject: RE: IfExpr has a mandatory else clause



> So is grammar ambiguity the reason that IfExpr has a
> mandatory else clause ? Are there other design considerations

Making the else clause mandatory emphasizes that this is an expression
and not a procedural statement: it always returns a result. In most
languages where I've seen a conditional expression, both branches are
mandatory.

An exception of course is <xsl:if> in XSLT, but perhaps that's because
the semantics have only recently been recast into expression form, and
the spec still talks of this as an "instruction" rather than an
"expression".

Michael Kay
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.