LÖVE

Jasoco wrote:It has in my experience of sorting my objects by Y.

You can't depend on it, in the documentation it says:

The order in which the indices are enumerated is not specified, even for numeric indices.

slime wrote:Well, if you use a numeric for then you're probably going to be using the # operator on the table, and that will also not like gaps in the array part. Just try to either not have gaps in arrays (use table.remove), or discard the notion of iterating over the whole array sequentially if there are gaps. :p

I just tried table.remove... Now I don't have to use something that I hate Thank you, Slime!

Using table.remove instead of setting a particular index to nil will re-order your indices so there are no gaps as well.

Robin wrote:

Jasoco wrote:It has in my experience of sorting my objects by Y.

You can't depend on it, in the documentation it says:

The order in which the indices are enumerated is not specified, even for numeric indices.

Well I'm just saying in all the time I've depended on it for making sure my objects are drawn from top to bottom even when moving around, I've never had it get out of order as long as I use pairs(). And this is with it sorting every single frame.

Personally, if table.sort didn't work right, I don't know what I would do.

y'know, table.sort only works with indices 1 to #table -- are you sure you're not talking about ipairs?

I am sure. I have done it numerous times. My Adventure Engine proves that.

I probably misunderstood you. Could you please explain very clearly and carefully what you do then and what the result in?

I'd like to learn something new.

if you're getting a meaningful iteration order out of pairs then that means you're either really lucky or it's not actually working like you think it is but haven't seen it mess up yet

the fun starts when the table rehashes

The fun starts when you switch Lua versions or implementations and you wonder why seemingly random bugs occur at seemingly random times.