W3C home > Mailing lists > Public > www-xpath-comments@w3.org > October to December 2000

boolean inconsistency

From: Elliotte Rusty Harold <elharo@metalab.unc.edu>
Date: Thu, 30 Nov 2000 10:21:03 -0500
Message-Id: <p04330109b64c1fc9b2a0@[192.168.1.6]>
To: xsl-list@mulberrytech.com
Cc: www-xpath-comments@w3.org
I've noticed an inconsistency in the XPath 1.0 spec. The boolean() 
type conversion function is defined like this:

boolean boolean(object)

However the other type conversion functions are defined like this:

string string(object?)
number number(object?)

In other words, all the type conversion functions except boolean() 
will operate on the context node if the argument is omitted. Is there 
a reason for this inconsistency?

If not, I wouldn't suggest changing it now, but it's probably 
something to think about for XPath 1.1. This change shouldn't make 
illegal any existing legal XPaths.

-- 

+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | elharo@metalab.unc.edu | Writer/Programmer |
+-----------------------+------------------------+-------------------+
|                  The XML Bible (IDG Books, 1999)                   |
|              http://metalab.unc.edu/xml/books/bible/               |
|   http://www.amazon.com/exec/obidos/ISBN=0764532367/cafeaulaitA/   |
+----------------------------------+---------------------------------+
|  Read Cafe au Lait for Java news:  http://metalab.unc.edu/javafaq/ |
|  Read Cafe con Leche for XML news: http://metalab.unc.edu/xml/     |
+----------------------------------+---------------------------------+
Received on Thursday, 30 November 2000 11:27:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 October 2007 16:05:54 GMT