Search:

Type: Posts; User: lost_in_code

Search: Search took 0.01 seconds.

  1. Replies
    12
    Views
    4,112

    Sorry to double post, but after doing some...

    Sorry to double post, but after doing some research, I've come to the conclusion that it is generally OK to call fwrite/fread after a preceding call causes an error. Granted you would want to do...
  2. Replies
    12
    Views
    4,112

    Take for example, I need to read a small binary...

    Take for example, I need to read a small binary data file. This might consist of several calls to fread. It would be darn inconvenient to check the result of each one instead of calling fread several...
  3. Replies
    12
    Views
    4,112

    I guess that's my final question then. Is it...

    I guess that's my final question then. Is it "safe" to continue using fread/fwrite after an error, or is it "proper" to make sure you never call it for a file whose error state is set. If any experts...
  4. Replies
    12
    Views
    4,112

    Yeesh.... Why on earth did I even write that....

    Yeesh.... Why on earth did I even write that. Thanks for pointing that out.

    EDIT: I remember actually why I did that. I realized that in order to get correct behavior out of the functions that...
  5. Replies
    12
    Views
    4,112

    I thought using "unsigned char" and "short" would...

    I thought using "unsigned char" and "short" would be adequate, as long as I assume that they can hold at least an 8-bit unsigned value and 16-bit signed value respectively.



    I'm not sure I...
  6. Replies
    12
    Views
    4,112

    Portable binary file I/O library attempt

    Hi everyone. This my first post here. I'm a bit of novice C programmer and am very insecure about my programming skills. I needed to write a small wrapper for handling binary file I/O for use by a...
Results 1 to 6 of 6