I develop on Windows but my question is may my C code be ported and EOF work on both

Onceler · 02-18-2013, 04:01 PM

I am writing a program that generates a file, will the EOF marker for Linux be readable on a Windows system and vise versa?

EagleKeeper · 02-18-2013, 04:04 PM

The EOF is a code that both file systems should recognize.

Now a *nx file may not be directly readable on a windows platform.
We used to have to send the files across TCP/IP between platforms back in the 90's. Unsure if that issue still exists

Ken g6 · 02-18-2013, 06:34 PM

If your file is a text file, you may run into the CRLF/LF issue. This can be manually solved with the "unix2dos"/"dos2unix" programs. Otherwise you may want to check for an extra CR (Carriage Return) character in case you need to discard it.

Onceler · 02-18-2013, 06:54 PM

it will be a binary file the object is to have it readable on both systems without the ctrl-z ctrl-d being a problem.

Markbnj · 02-18-2013, 08:12 PM

Quote:

Originally Posted by EagleKeeper

The EOF is a code that both file systems should recognize.

Now a *nx file may not be directly readable on a windows platform.
We used to have to send the files across TCP/IP between platforms back in the 90's. Unsure if that issue still exists

Sounds like you were curing an endian-ness problem by calling hton* on one side and ntoh* on the other. You were probably using a version of Unix that is big-endian. Windows and most versions of Linux on x86 architectures are all little-endian, so it shouldn't be an issue for most cases now.

EagleKeeper · 02-19-2013, 07:36 AM

Quote:

Originally Posted by Markbnj

Sounds like you were curing an endian-ness problem by calling hton* on one side and ntoh* on the other. You were probably using a version of Unix that is big-endian. Windows and most versions of Linux on x86 architectures are all little-endian, so it shouldn't be an issue for most cases now.

One reason why I specified the date - demonstrates aging

Very few version of *nx existed at the time on a x86. we had SCO at the timeon a x86.
The files though were on some mainframe that were being used.

Would the Mac line have the same issue?

Markbnj · 02-19-2013, 09:22 AM

Quote:

Originally Posted by EagleKeeper

One reason why I specified the date - demonstrates aging

Very few version of *nx existed at the time on a x86. we had SCO at the timeon a x86.
The files though were on some mainframe that were being used.

Would the Mac line have the same issue?

OS X on Intel is also little endian. OS X and earlier systems on power pc and Motorola architectures were big endian.