Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

C - freopen or freopen_s

Name: Anonymous 2014-02-08 16:01

These functions, declared inside stdio.h, both have one thing that I couldn't find the use of:


== FILE * freopen( "asd.txt", "r+", oneFILE*variable ); ==

Why does this shit return a (FILE *)?
- The oneFILE*variable gets its previously held file closed, all good.
- The oneFILE*variable gets loaded with the "asd.txt" with "r+" attribute, all good.

Then the function fucking returns the same pointer, again, the same thing that has been fucking stored inside the oneFILE*variable, why?


== errno_t freopen_s( ONEdummyFILE**variable, "asd.txt", "r+", oneFILE*variable ) ==

Same shit again, why am I giving a retarded, no-use, dummy FILE** variable?

What the fuck is this? Does it have another explanation?

Name: Anonymous 2014-02-08 19:11

>>3
freopen returning NULL when an error occurs is a good reasoning for it to have a return value, but why a return value with the 4 byte type (FILE *)? A single byte (char) would be able to do it.

Whatever, I think I'll just use freopen then, and disregard the return value, or maybe use it within "if". I don't want to create a dummy (FILE *) to pass into freopen_s.

What reply codes are here in this board? /b/ has none...
code tags perhaps

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List