5 replies to this topic

[EveryOS]

I tried the following code in the Lua console:

h = fs.open("x", "w")
h.write("\13")
h.close()
h=fs.open("x", "r")
string.byte(h.read())
h.close()

And the result was 13, even though I expected it to be 10

It's causing major flaws in a program that I am writing, it took a tremendous amount of debugging to find this issue, and I can't really escape it in the auto-generated file that easily

Edited by EveryOS, 30 June 2018 - 01:00 AM.

[KingofGamesYami]

Carriage return (\r) and line feed (\n) are handled differently at the OS level by eg. OSX vs. Windows. Sometimes git will change these around, if you're using that for versino control.

[Bomb Bloke]

I'm not entirely sure that this is an "OS level" thing, but the behaviour is certainly decided according to the OS in use.

If this actually matters to your code, then odds are you should be using binary mode for your file handles instead:

h = fs.open("x", "wb")
h.write(13)
h.close()
h=fs.open("x", "rb")
result = h.read()
h.close()

If you really feel that you must use text mode, then convert through base64 or similar before writing to disk.

[EveryOS]

Whoa, binary mode might actually be really useful for what I am writing! It will decrease the amount of code, and increase effeciency

[KingofGamesYami]

Bomb Bloke, on 30 June 2018 - 09:05 AM, said:

I'm not entirely sure that this is an "OS level" thing

Yeah, I doubt the OS is actually doing anything. I suspect another program (eg. Git) is changing it for that reason.

[EveryOS]

I wasn't even using git, so it couldn't have. But using binary mode fixed it