What exactly wrong in JSON.adept?

[ghost]

Syntactic sugar doesn't work as expected? I found you replaced unless with the plain old if. Naming conflict? You also replaced length with capacity and read. This language has so many syntactic sugar that sometimes you get lost when reading code. It's kind of like you are reading code in another language. This will definitely cause problems. I admit I can't remember all of the syntactic sugar and only stick to the C-like syntax.

[IsaacShelton]

The error was that the Window's function ftello64 and fread were not agreeing on the number of bytes to read. I fixed it by using ftello64's larger guess and then if fread didn't read all the bytes, it would be okay if at the end of file.

There must be something weird with ftello64 or something, because it seems include the size of the file metadata or something, which isn't the case normally.

I changed those other things to improve the readability a little bit while I was there, since the code was pretty bad and unnecessarily compacted.

[ghost]

fseeko64 and ftello64 are compatibility functions added by MinGW. Windows itself has no such functions.

[ghost]

Windows has _fseeki64 and _ftelli64:

https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/fseek-fseeki64?view=msvc-170

https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/ftell-ftelli64?view=msvc-170

[ghost]

Btw, even if you replaced fseeko64 and ftello64 with _fseeki64 and _ftelli64, the code still fails. I discovered this when tried to fix the issue myself without but success.