BUG: Invalid Extraction from istrstream Does Not Set failbit

• Microsoft C/C++ for MS-DOS, version 7.0
• Microsoft Visual C++ for Windows, versions 1.0, 1.5, 1.51, 1.52
• Microsoft Visual C++ 32-bit Edition, versions 1.0, 2.0, 2.1, 4.0, 4.1, 4.2, 5.0

SYMPTOMS

If you extract an integer of an invalid octal value from istrstream, 0 is extracted and the ios::failbit is not set. In addition, the ios::fail() function returns FALSE, incorrectly indicating that the istrstream is valid.

RESOLUTION

Use the manipulators (dec, hex, oct, binary, text) explicitly to set the correct conversion base for the characters represented by the stream.

STATUS

Microsoft has confirmed this to be a bug with the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

A scenario that produces an unexpected result, and which may also reflect this problem, involves using the string "08" to initialize the buffer used by the istrstream (or any string where the first character is 0 and one of the following characters is greater than 7).

This string causes the istrstream extraction operator to load the int with 0 instead of the expected value. This is because when 0 is the leading character in a number and it is not followed by an x or X, the number is treated as an octal number. Therefore, only the characters 0 through 7 after the leading 0 are valid.

Sample Code

   /* Compile options needed: none
   */

   #include <strstrea.h>

   void main()
   {
      char buffer[10] = "08";
      int i;
      istrstream* str;

      str = new istrstream( buffer, 10 );

      // The following extraction is made with the expectation that
      // the i will be set to 8. However, it will be set to 0.
      *str >> i;

      // To fix this, change the line to:
      // *str >> dec >> i;

      cout << "i = " << i << endl;
      cout << "str->fail()=" << str->fail() << endl;
      delete str;
   }