<join host="p5B20DDE6.dip.t-dialin.net" login="n=wolf" nick="wolf77" time="08:10:03.562+01:00"/>
<part host="d51A40105.access.telenet.be" login="n=Mephisto" nick="Mephisto" reason="Read error: 110 (Connection timed out)" time="09:10:17.74+01:00"/>
<join host="deimos.jacobs-university.de" login="n=dimitar" nick="dimitar" time="09:36:29.034+01:00"/>
<part host="deimos.jacobs-university.de" login="n=dimitar" nick="dimitar" reason="Read error: 104 (Connection reset by peer)" time="09:36:34.001+01:00"/>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" time="11:42:13.201+01:00"/>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig_" time="11:54:00.451+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" reason="simmons.freenode.net irc.freenode.net" time="11:55:47.366+01:00"/>
<message nick="wolf77" time="12:27:51.049+01:00">Hi Pierrick</message>
<message nick="wolf77" time="12:27:57.247+01:00">something I don't understand:</message>
<message nick="wolf77" time="12:28:14.771+01:00">for $i in 1 to 10 return <element/></message>
<message nick="wolf77" time="12:28:46.955+01:00">are those <element/> nodes supposed to belong to the same document or is each in a different document or is there no document at all?</message>
<message nick="perig" time="12:32:09.49+01:00">I guess they are not in the same document...</message>
<message nick="perig" time="12:32:20.625+01:00">... because there is no document</message>
<message nick="wolf77" time="12:33:46.121+01:00">which also means that the order of those nodes is only determined by the sequence in which they are returned</message>
<message nick="perig" time="12:34:41.446+01:00">yes. trying to imagine a test case that demonstrates it</message>
<message nick="wolf77" time="12:35:41.828+01:00">there's one in the test suite...</message>
<message nick="wolf77" time="12:36:30.264+01:00">ConstructedNodesTest.testIterateConstructedNodes</message>
<message nick="wolf77" time="12:37:41.19+01:00">eXist used to add the nodes to the same document object, which led to some issues demonstrated by one of DiZzZz' tests</message>
<message nick="perig" time="12:38:03.581+01:00">I see</message>
<message nick="wolf77" time="12:38:16.959+01:00">I changed that so the nodes are now added to distinct docs - which leads to the question of ordering</message>
<message nick="perig" time="12:38:50.625+01:00">I also see ;-)</message>
<message nick="wolf77" time="12:39:47.883+01:00">ValueSequence.sortInDocumentOrder will reorder the docs, which is bad</message>
<message nick="perig" time="12:42:48.047+01:00">Yes, I see.</message>
<message nick="perig" time="12:44:19.732+01:00">In fact, this common case can also be seen as a particular one : the context might want to order the generated sequences</message>
<join host="62.232.6.162" login="n=XIRCProx" nick="DiZzZz" time="12:51:55.11+01:00"/>
<part host="62.232.6.162" login="n=XIRCProx" nick="DiZzZz" time="13:02:31.104+01:00"/>
<join host="62.232.6.162" login="n=XIRCProx" nick="alphatester2" time="13:40:52.189+01:00"/>
<message nick="alphatester2" time="13:41:07.871+01:00">.</message>
<part host="62.232.6.162" login="n=XIRCProx" nick="alphatester2" time="13:41:21.669+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" reason="Read error: 104 (Connection reset by peer)" time="13:59:53.039+01:00"/>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" time="14:00:57.717+01:00"/>
<join host="151.80.11.134" login="n=Steeler" nick="akht" time="14:11:33.7+01:00"/>
<message nick="akht" time="14:12:07.436+01:00">hi</message>
<part host="151.80.11.134" login="n=Steeler" nick="akht" time="14:15:10.144+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" reason="Read error: 113 (No route to host)" time="15:07:29.208+01:00"/>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" time="15:34:49.055+01:00"/>
<join host="d51A40105.access.telenet.be" login="n=Mephisto" nick="Mephisto" time="16:38:07.114+01:00"/>
<join host="c83-253-30-113.bredband.comhem.se" login="n=ljo" nick="ljo" time="16:57:56.159+01:00"/>
<join host="vh036a.halls.manchester.ac.uk" login="i=xt" nick="Cassi3" time="18:15:51.328+01:00"/>
<part host="vh036a.halls.manchester.ac.uk" login="i=xt" nick="Cassi3" time="18:15:56.215+01:00"/>
<join host="c83-253-30-113.bredband.comhem.se" login="n=ljo" nick="lj1" time="18:54:00.077+01:00"/>
<part host="c83-253-30-113.bredband.comhem.se" login="n=ljo" nick="ljo" reason="Read error: 113 (No route to host)" time="19:10:45.182+01:00"/>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig_" time="19:51:44.112+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" reason="Read error: 113 (No route to host)" time="20:06:57.071+01:00"/>
<join host="host81-155-50-215.range81-155.btcentralplus.com" login="n=k-9" nick="k-9" time="21:09:10.162+01:00"/>
<part host="host81-155-50-215.range81-155.btcentralplus.com" login="n=k-9" nick="k-9" reason="Client Quit" time="21:13:33.569+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig_" reason="Read error: 113 (No route to host)" time="21:58:01.072+01:00"/>
</xlog>