corecheckno has quit [Remote host closed the connection]
rob_w has joined #picolisp
rob_w has quit [Ping timeout: 252 seconds]
rob_w has joined #picolisp
casaca has quit [Remote host closed the connection]
cpli has quit [Remote host closed the connection]
payphone has quit [Remote host closed the connection]
payphone has joined #picolisp
cpli has joined #picolisp
casaca has joined #picolisp
z4k4ri4 has quit [Ping timeout: 252 seconds]
z4k4ri4 has joined #picolisp
tankf33der has quit [Quit: Ping timeout (120 seconds)]
tankf33der1 has joined #picolisp
mario-goulart has joined #picolisp
mario-goulart has quit [Remote host closed the connection]
tankf33der1 is now known as tankf33der
rob_w has quit [Remote host closed the connection]
<beneroth>
abu[7], to get the minKey object of a tree (e.g. rel 'id (+Need +Key +Number), (leaf 'tree) could be used. To get the object with the maxKey it is (db 'id '+Item (maxKey (tree 'id '+Item))) right? Or is there a leaf-equivalent for maxKey?
<beneroth>
I guess (leaf) only needs one index access, while (db ... (maxKey)) accesses the index twice
<beneroth>
I just looked at implementation of (leaf), it's just a while going through the index, so I guess it would be trivial to implement a variant leafMax or so...
ygrek has joined #picolisp
ygrek has quit [Remote host closed the connection]
<abu[7]>
Hi beneroth! The number of accesses should be the same iirc, just maxKey is more complicated because is supports a range
<abu[7]>
I would not worry here
<beneroth>
T about the not worrying, you're right :)
<beneroth>
but access should be two, or do I overlook something? 1. maxKey accessing the index to find the maximal key, 2. db accessing the index to find the obj for the key
<beneroth>
other question: what's the reason for the existence of (leaf) ?
<beneroth>
if you recall - otherwise nevermind ;-)
<abu[7]>
The object is in the same node
<abu[7]>
I don't reme member well, pro bably for a optimized access