[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Sort function modifies the table being sorted?
- From: Dimiter 'malkia' Stanev <malkia@...>
- Date: Wed, 13 Jun 2012 22:26:37 -0700
I think you are introducing non-determinism.
You are getting two values to be compared (a and b), and yet
instead you use these values as indices to the current state of the
array (which is not your business, hence the non-determinism).
the sort routine just asked you to compare two things, not to use them
as indices vs the current (random in a sense) state of the array.
On 6/13/2012 8:56 PM, Paul K wrote:
I'm utterly puzzled by the behavior of this fragment:
local alphanumsort = function(o)
print('---', a, b) for k,v in ipairs(o) do print(k,v) end
return (o[a] or 9)..a< (o[b] or 9)..b
This is a simplified fragment from an application I have been working
on. On my machine (Windows with Lua 5.1.4) it dies with:
sort.pl:4: attempt to concatenate local 'b' (a nil value)
sort.pl:4: in function<sort.pl:2>
[C]: in function 'sort'
sort.pl:2: in function 'alphanumsort'
sort.pl:6: in main chunk
Where does this "nil" value come from? It is clearly not in the
original table. if I replace ..a and ..b with tostring(a) and
tostring(b), I get "invalid order function for sorting", which usually
indicates that the function returns inconsistent results (1< 5 in one
case and 1> 5 in another), but I don't see why it would do it in this
case. Basically, the idea is to sort elements that match their
positions first and sort everything else after that.
Even more puzzling, when I replace "o[a] or 9" with "o[a] and 0 or 9",
things start working as expected, but maybe it just hides the issue;
If you review the output, you notice that some elements got swapped
even though I would not expect them to be (that may be a red herring
though as they get swapped in "normal" cases too). For example, values
for 5 and 9 get swapped, even though 5 is "before" 1.2 given the
result of the comparator.
--- -1 5
--- 2 5