binaryfiles

We often use fgetc like this: int c; while ((c = fgetc(file)) != EOF) { // do stuff } Theoretically, if a byte in the file has the value of EOF , this code is buggy - it will break the loop early and fail to process the whole file. Is this situation possible? As far as I understand, fgetc internally casts a byte read from the file to unsigned char and then to int , and returns it. This will work if the range of int is greater than that of unsigned char . What happens if it's not (probably then sizeof(int)=1 )? Will fgetc read a legitimate data equal to EOF from a file sometimes? Will it alter

For the sake of learning C and understanding the difference between Binary Files and Text Files, I'm attempting to write a string to file as both file types like so: char * string = "I am a string!"; FILE * filePtrA = fopen("/output.txt", "wt"); fwrite(string, strlen(string), 1, filePtrA); FILE * filePtrB = fopen("/output.bin", "wb"); fwrite(string, strlen(string), 1, filePtrB); fclose(filePtrA); fclose(filePtrB); However both "wt" and "wb" are writing as a Text File, where "wb" should be writing as a Binary File. Hex appears like so for both files: 49 20 61 6D 20 61 20 73 74 72 69 6E 67 21

How do you edit a Single-Record-type Binary Mainframe file in the RecordEditor using Cobol Copybook on a Windows or Linux PC. Note: This is an attempt to split a very broad question into a series of simpler Question and Answers. To Edit a File in the RecordEditor with a Cobol Copybook you must first load the copybook and then edit the file Loading the Cobol Copybook into the RecordEditor Select Record Layouts >>> Load Cobol Copybook menu options On the Cobol Load Screen enter the Cobol Copybook and your Mainframe Data file . The RecordEditor will read the file and try and work out what the

I am having some trouble with packing and unpacking of binary floats in python when doing a binary file write. Here is what I have done: import struct f = open('file.bin', 'wb') value = 1.23456 data = struct.pack('f',value) f.write(data) f.close() f = open('file.bin', 'rb') print struct.unpack('f',f.read(4)) f.close() The result I get is the following: (1.2345600128173828,) What is going on with the extra digits? Is this a rounding error? How does this work? On most platforms, Python floats are what C would call a double , but you wrote your data out as float instead, which has half the