Chriis,
I think Arne is right. Most likely inside FGetS2 the runtime uses a 32 bit offset in a file that is 6 Gb. That will result in an overflow with unexpected results.
Robert
Reading Very Large files
Reading Very Large files
XSharp Development Team
The Netherlands
robert@xsharp.eu
The Netherlands
robert@xsharp.eu
Reading Very Large files
Hey, that was my first thought, too, but I was too timid to voice it... Thanks for confirming
Regards
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
Reading Very Large files
Arne, Robert,
Ah, I am sorry, I completely misread Arne's message! I thought it was about memory size, while it was about file pointers. Summer here is not a good time for the brain to work
Of course it makes sense what you guys say, hadn't thought about this.
.
Ah, I am sorry, I completely misread Arne's message! I thought it was about memory size, while it was about file pointers. Summer here is not a good time for the brain to work
Of course it makes sense what you guys say, hadn't thought about this.
.
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu