W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1566] [FS] technical: 4.1.1 Literals

From: <bugzilla@wiggum.w3.org>
Date: Wed, 20 Jul 2005 23:31:15 +0000
To: public-qt-comments@w3.org
Message-Id: <E1DvO1z-0007q5-Dx@wiggum.w3.org>


simeon@us.ibm.com changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED

------- Additional Comments From simeon@us.ibm.com  2005-07-20 23:31 -------

Thanks for the comment. It seems that a somewhat cleaner way to write the
semantics would be to introduce an auxiliary judgment to go from
literalexpressions to literalvalues. This would be a bit less heavy-handed than
a function.

This could look as follows. Would that be better?

- Jerome

We could introduce an auxiliary judgement to go from the syntax tree
literal to the value literal. As follows.

Instead of writing:

  dynEnv |- IntegerLiteral => xs:integer (IntegerLiteral)


  IntegerLiteral has literal value IntegerValue
  dynEnv |- IntegerLiteral => IntegerLiteral of type xs:integer

Instead of writing:

  dynEnv |- DoubleLiteral => xs:double(DoubleLiteral)


  DoubleLiteral has literal value DoubleValue
  dynEnv |- DoubleLiteral => DoubleValue of type xs:double

where the has literal value raises a static error if the literal

Instead of writing:

  dynEnv |- StringLiteral => xs:string(StringLiteral)


  StringLiteral has literal value StringValue
  dynEnv |- StringLiteral => StringValue of type xs:string

Where the judgment 'has literal value' deals with character
references, and predefined entity references.
Received on Wednesday, 20 July 2005 23:31:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC