Re: The set datatype implemented in XPath 3.0

Vladimir,

Probably using a map is one way of implementing a set (the keys in the
each key-value entry of a map, form a set).

There are also other ways to do this.

The set module can easily switch between different implementations
just by changing the import instruction.


Implementing the map datatype itself,  people will have to implement
something similar to set for keeping the keys and it would be good if
they have choice.



--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play
-------------------------------------
Facts do not cease to exist because they are ignored.

On Tue, Feb 22, 2011 at 6:54 AM, Vladimir Nesterovsky
<vladimir@xxxxxxxxxxxxxxxxxxxx> wrote:
> Dimitre,
>
> please take a look at http://www.w3.org/Bugs/Public/show_bug.cgi?id=11493
> My hope is that XPath 3.0 will contain built-in map data type, and that one
> will be free from reimplementing maps, sets (and trees also).
> --
> Vladimir Nesterovsky
> http://www.nesterovsky-bros.com/
>
>
> -------- Original Message --------
>> From: "Dimitre Novatchev" <dnovatchev@xxxxxxxxx>
>> Sent: Tuesday, February 22, 2011 4:33 PM
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> Subject: SPAM-HIGH: B  The set datatype implemented in XPath 3.0
>>
>> I think this new post may be interesting to our xslt programmers:
>>
>> "The set datatype implemented in XPath 3.0", at:
>>
>>
>
http://dnovatchev.wordpress.com/2011/02/20/the-set-datatype-implemented-in-x
> path-3-0/