LÖVE

It would be a mode that would be returned by getMode, and it is indeed in the same string-to-enum map used by open, but why should we create a separate one, if it currently just ignores it if it's set to close mode?

API design is UI design, and poorly designed user interfaces allow you to do nonsensical operations for no good reason. This is a minor example of just such a case. It would cost practically nothing to just raise an error when a file is being opened in closed mode, whatever the heck that even means.

EDIT: portions redacted.

You aren't getting it, "opening in closed mode" doesn't do anything, why would an error improve that?!

I think I'm with pekka on this one.

If it doesn't do anything, it should throw an error. Just like it would (I hope) if one did something like myFile:open("1234").

As this is something that the lover should have done right in the first place (it is an error or the part of the programmer, not the user), I agree to pekka and kikito. UNLESS "c" mode has some special reason for existing that I don't know about.

This concludes my interest in contributing to the Löve on-line docs. I'm really just wasting my time here.

Wait, why?

Because I am writing a reference document for my own off-line use, and I see no value in adding anything to the Wiki.

Because everything you are writing down is already there? Or is there some other reason?

Because there's no sensible reason to freely give something to benefit a community; especially so if this thing is already created and usable.