stdio differences windows vs linux

Hi, I had to write a trivial database program using first principles with the C standard library. I wrote and tested the program on windows in binary mode, because I thought the C standard library was cross platform. However, when I compile the code on linux there seems to be some kind of differences because the database is failing to write the correct bytes to the file. I haven't determined what is causing the failure, that could take some serious time. So what I was hoping was if someone knows of all the differences between windows and linux when it comes to file i/o they could maybe point me in the right direction..

Primarily all i am using is fseek, fwrite, fread, and ftell

Can someone at least confirm that they are aware of differences between windows and linux support of these functions?

Thanks in advance.

There shouldn't be any difference, no. I mean, fread(), fwrite(), ftell() are standard libraries. They should work both in Linux and Windows. I don't think you should have a problem with these functions.
Are you sure you are opening the file in binary format? If not then there are some differences in Windows and Linux, but in any case it is wrong.

I have written quite a few programs for both Linux and Windows that use stdio, and there should be no difference. Of course, if you are bending the rules somehow, you may find that the different OS's do things differently. Also, bear in mind that the different OS's may have different sizes for data types, for example, if you use the 64-bit version of Linux, "long" would be 64-bit, whilst "long" even in 64-bit versions of Windows are 32-bit.

--
Mats

Windows uses "\r\n" for newlines; UNIX uses "\n" for newlines.
That's the only difference I can think of.

Originally Posted by cpjust

Windows uses "\r\n" for newlines; UNIX uses "\n" for newlines.
That's the only difference I can think of.

But that ONLY applies if the file is opened in text mode, which the original post says it isn't.

--
Mats

Originally Posted by matsp

But that ONLY applies if the file is opened in text mode, which the original post says it isn't.

--
Mats

If there's one thing I learned when I did tech support many years ago, it's that you should never trust anything that people tell you unless you've checked it yourself.

Originally Posted by cpjust

If there's one thing I learned when I did tech support many years ago, it's that you should never trust anything that people tell you unless you've checked it yourself.

I agree. That is why I asked if it is sure opened in binary. It is a common mistake to think you opened it in binary mode, but to open it in text mode. Dunno, like putting "w+ b" as a parameter, so possibly " b" will be ignored and it will open in text mode.