iostream

I am using the Windows Driver Kit (WinDDK 6001.18001) to build my userspace application rather than Visual Studio 2005. I am taking this approach because we also have to build driver components, so I'd prefer to have a single build environment to build everything. Microsoft itself uses this approach for several products. This was working fine until I started using Boost 1.38.0. I'm not using C++ in the kernel mode components, just the userspace applications. In C++ code, it's natural to use the boost libraries. Unfortunately, the WDK doesn't agree. The first error I noticed is that "#include

I know that there is no concept of threads in current C++ , but this article is saying : A typesafe, threadsafe, portable logging mechanism ..... The fprintf() function is threadsafe, so even if this log is used from different threads, the output lines won't be scrambled. What about cout , cerr and clog ? I think this question is applicable to all kind of stream types in C++ also, like fstream and stringstream . The article makes a claim about the POSIX standard for the fprintf API. It says nothing about C++ streams. And this is quite correct, as there are no such guarantees on those stream.

#include <iostream> #include <string> using namespace std; int main() { wcout << L"Hello"; // OK. wcout << wstring(L"Hello"); // OK. wcout << "Hello"; // OK. Why? wcout << string("Hello"); // Error. Why? } Why does std::wcout accept a narrow string literal as its argument but doesn't accept a narrow string object? This is dictated by § 27.7.3.6.4 of the C++11 Standard, where the following two overloaded operators (among others) are specified: template<class charT, class traits> basic_ostream<charT,traits>& operator<<( basic_ostream<charT,traits>& out, const charT* s ); template<class charT,

I'm testing some snippets I found off the web using g++ from MinGW. This is the C++ compiler...why then does it correctly compile C....why do people intertwine C and C++. The concrete question is: Is it O.K. to use both C and C++ and compile under g++. If the answer is yes, this makes my life easy as I do not have to modify the code. Oddly enough...to get some C++ to work, particularly when passing a string to an ifstream constructor it requires a C type string... My guess would be that because C++ depends upon C constructs at times is is O.K to write the two languages together. However as a

Let's say we have a stream containing simply: hello Note that there's no extra \n at the end like there often is in a text file. Now, the following simple code shows that the eof bit is set on the stream after extracting a single std::string . int main(int argc, const char* argv[]) { std::stringstream ss("hello"); std::string result; ss >> result; std::cout << ss.eof() << std::endl; // Outputs 1 return 0; } However, I can't see why this would happen according to the standard (I'm reading C++11 - ISO/IEC 14882:2011(E) ). operator>>(basic_stream<...>&, basic_string<...>&) is defined as behaving

General use case I am trying to implement a basic shell. Description I need to read user input until some delimiters are pressed so a corresponding action can be performed. Those delimiter could be a single 'a', a single 'b' or a single 'c'. An input example would look like this (where > is the shell prompt): > 111-222-333-444a Ok, '111-222-333-444' entered Why do I want inline delimiter instead of 'new-line' delimiter? Because I would like to listen to keyboard event such as 'up-arrow' to erase the current command and print the last command (implementing a history feature). Because I would