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-09 19:06

>>7
Usually when somebody says they are ignoring a return value it means that they are doing nothing with it (e.g. that the resulting program would behave the same if the return value of the function whose argument is ignored is cast to void).

You are testing the return value for null there; that is perfectly fine.

>>8
And in a case where all that's really needed is puts!

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