Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
C Programming
Dealing with a large integer
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Jordan Abel, post: 2453370"] My interpretation is the opposite - that it's intended to change stdin to be _another file_ open in read mode, or stdout/stderr to another file open in write mode. It's also possible that on some systems extra magic may be needed to make a re-opened stdout become the standard output of a command executed via system(), or even for a re-opened stream to become the standard stream used by functions not implemented in standard C such as perror(). It also might be desirable for the buffering state of a stream to be retained in some cases. For example, there is a good reason why stderr is not fully buffered at program start. (It's unclear to me whether freopen can even change the buffering state at all - though it could be desirable to do so when changing stdout to be a regular file when it was an interactive device at program startup) [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
C Programming
Dealing with a large integer
Top