I/O manipulators | ||||
Print functions(C++23) | ||||
C-style I/O | ||||
Buffers | ||||
(C++23) | ||||
(C++98/26*) | ||||
(C++20) | ||||
Streams | ||||
Abstractions | ||||
File I/O | ||||
String I/O | ||||
Array I/O | ||||
(C++23) | ||||
(C++23) | ||||
(C++23) | ||||
(C++98/26*) | ||||
(C++98/26*) | ||||
(C++98/26*) | ||||
Synchronized Output | ||||
(C++20) | ||||
Types | ||||
Error category interface | ||||
(C++11) | ||||
(C++11) |
Member functions | ||||
State functions | ||||
Formatting | ||||
Miscellaneous | ||||
basic_ios::tie | ||||
Protected member functions | ||||
(C++11) | ||||
(C++11) | ||||
(C++11) |
std::basic_ostream<CharT, Traits>* tie()const; | (1) | |
std::basic_ostream<CharT, Traits>* tie(std::basic_ostream<CharT, Traits>* str); | (2) | |
Manages the tied stream. A tied stream is an output stream which is synchronized with the sequence controlled by the stream buffer (rdbuf()), that is,flush() is called on the tied stream before any input/output operation on*this.
Contents |
str | - | an output stream to set as the tied stream |
The tied stream, or a null pointer if there was no tied stream.
May throw implementation-defined exceptions.
By default, the standard streamstd::cout is tied tostd::cin andstd::cerr. Similarly, its wide counterpartstd::wcout is tied tostd::wcin andstd::wcerr.
#include <fstream>#include <iomanip>#include <iostream>#include <string> int main(){std::ofstream os("test.txt");std::ifstream is("test.txt");std::string value("0"); os<<"Hello"; is>> value; std::cout<<"Result before tie(): "<<std::quoted(value)<<"\n"; is.clear(); is.tie(&os); is>> value; std::cout<<"Result after tie(): "<<std::quoted(value)<<"\n";}
Output:
Result before tie(): "0"Result after tie(): "Hello"
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR | Applied to | Behavior as published | Correct behavior |
---|---|---|---|
LWG 835 | C++98 | two streams could be tied to each other[1] (either directly or through another intermediate stream object) | the behavior is undefined in this case |
flush()
is called on a stream object, theconstructor of the sentry object will callflush()
on its tied stream, and thatflush()
will construct another sentry object and its constructor will callflush()
on the tied stream of that stream and so on. Therefore, if streamsa andb are (directly or indirectly) tied to each other, callinga.flush() will eventually callb.flush(), which will eventually calla.flush(), and will result in an infinite loop.