[Bug libstdc++/9925] ostrstream (buf, size) << "..." does not work properly

[Bug libstdc++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia@physics.uc.edu]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925


pinskia@physics.uc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2003-05-25 21:02:11
               date|                            |


------- Additional Comments From pinskia@physics.uc.edu  2003-05-25 21:02 -------
confirmed on the mainline (20030525) but had to changed the code:
#include <iostream>
#include <strstream>
using namespace std;

int main (void)
{
        char buf [100];

        // the following works fine in GCC 2.96 and other
        // compilers, but fails in GCC 3.1 and 3.2
        ostrstream (buf, 100) << "This is OK." << ends;
        cout << buf << endl;

        // the following works fine in any compiler
        ostrstream s (buf, 100);
        s << "This is OK." << ends;
        cout << buf << endl;

        return 0;
} /* main */


tin:~/src/gnu/gcctest>g++ pr9925.cc
In file included from /home/gates/pinskia/linux/include/c++/3.4/backward/strstream:51,
                 from pr9925.cc:2:
/home/gates/pinskia/linux/include/c++/3.4/backward/backward_warning.h:32:2: warning: 
#warning This file includes at least one deprecated or antiquated header. Please 
consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. 
Examples include substituting the <X> header for the <X.h> header for C++ includes, or 
<sstream> instead of the deprecated header <strstream.h>. To disable this warning use -
Wno-deprecated.
./a.    tin:~/src/gnu/gcctest>./a.out 
0x8048a2c
This is OK.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libstdc++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925



------- Additional Comments From pinskia at gcc dot gnu dot org  2003-08-18 02:54 -------
Note ICC 6.0 in strict mode warns about this:
pr9925.cc(11): warning #504: initial value of reference to non-const must be an lvalue
          ostrstream (buf, 100) << "This is OK." << ends;
          ^

I think gcc should warn or error out here also.

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925


pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|libstdc++                   |c++
           Keywords|                            |diagnostic


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-08-19 04:20 -------
Moving to c++ because it is the front-end that should be emitting this warning or error, 
most likely related to casts as lvalue extension.

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925


pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eckstein at atair dot co dot
                   |                            |at


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-08-22 21:44 -------
*** Bug 12036 has been marked as a duplicate of this bug. ***

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[larssj at nospam dot dk]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925



------- Additional Comments From larssj at nospam dot dk  2003-10-23 17:28 -------
I have a problem with name of the backward/strstream file.
The warning say  "<sstream> instead of the deprecated header <strstream.h>"

But in 3.3 (mainline) it is call 'backward/strstream' NOT: 'backward/strstream.h'

This a BUG and old C++ code expect 'strstream.h' not 'strstream'.

Shall make a new bug entry?

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[larssj at nospam dot dk]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925



------- Additional Comments From larssj at nospam dot dk  2003-10-23 18:01 -------
The old gcc-3.2 has strstream and strstream.h in backward.

The code in the old strstream.h include strstream and used the namespace std
>From <strstream.h>
----
#ifndef _CPP_BACKWARD_STRSTREAM_H
#define _CPP_BACKWARD_STRSTREAM_H 1
 
#include "strstream"
 
using std::strstreambuf;
using std::istrstream;
using std::ostrstream;
using std::strstream;
 
#endif
---------------

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pilarczk at ii dot uj dot edu dot pl]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925



------- Additional Comments From pilarczk at ii dot uj dot edu dot pl  2003-10-24 09:34 -------
Subject: Re:  ostrstream (buf, size) << "..." does not work
 properly


> The warning say  "<sstream> instead of the deprecated header <strstream.h>"
> 
> But in 3.3 (mainline) it is call 'backward/strstream' NOT: 'backward/strstream.h'
> 
> This a BUG and old C++ code expect 'strstream.h' not 'strstream'.
> 
> Shall make a new bug entry?
> 

Yes, please!!! I also noticed this problem, but I thought my installation
was incomplete...

Thanks a lot!

Pawel Pilarczyk

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-08-25 07:24 -------
*** Bug 17181 has been marked as a duplicate of this bug. ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bjornpearson at linuxmail
                   |                            |dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-20 15:36 -------
*** Bug 22566 has been marked as a duplicate of this bug. ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |suckfish at ihug dot co dot
                   |                            |nz


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[kspiteri at ieee dot org]

------- Comment #25 from kspiteri at ieee dot org  2006-06-15 06:25 -------
In reply to comment #24:

> No it should not be. a() is a temporary so it cannot be bound to "a&".  At
> least it should not be.

Then this is not a bug. The C++ standard in 27.6.2.1 defines
* basic_ostream<charT,traits>& operator<<(const void* p);
as a member of class basic_ostream<charT, traits> and
* template<class traits>
*   basic_ostream<char,traits>& operator<<(basic_ostream<char,traits>&,
*                                          const char*);
as a helper function.

If the output for attachment 11669 should be
char
void
then ostreams are behaving correctly.


Also, in the attachment, if the line
    a() << "";
is changed to
    a() << "" << "";
then the output corresponding to that line is changed from
    void
to
    void
    char
Does this mean that a() << "" is returning the temporary variable bound to "a&"
while a() itself cannot be bound to "a&"?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

------- Comment #24 from pinskia at gcc dot gnu dot org  2006-06-14 15:30 -------
(In reply to comment #23)
> Instead, the output is:
> char
> void

No it should not be. a() is a temporary so it cannot be bound to "a&".  At
least it should not be.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[kspiteri at ieee dot org]

------- Comment #23 from kspiteri at ieee dot org  2006-06-14 15:28 -------
The test case in attachment 11669 shows that this bug has nothing to do with
ostreams. The output from the test case should be:
char
char
Instead, the output is:
char
void


-- 

kspiteri at ieee dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kspiteri at ieee dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[kspiteri at ieee dot org]

------- Comment #22 from kspiteri at ieee dot org  2006-06-14 15:24 -------
Created an attachment (id=11669)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11669&action=view)
Minimal test case.

Test case showing bug is independant of ostreams.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

------- Comment #21 from pinskia at gcc dot gnu dot org  2006-05-19 16:35 -------
*** Bug 27678 has been marked as a duplicate of this bug. ***


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yotam dot medini at gmail
                   |                            |dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

------- Comment #20 from pinskia at gcc dot gnu dot org  2006-01-31 01:21 -------
More comments about this issue can be found in the following libstdc++ thread:
http://gcc.gnu.org/ml/libstdc++/2006-01/msg00177.html


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

------- Comment #19 from pinskia at gcc dot gnu dot org  2006-01-31 01:20 -------
*** Bug 26040 has been marked as a duplicate of this bug. ***


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Raimund dot Merkert at
                   |                            |baesystems dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[aburger at cea dot fr]

------- Comment #18 from aburger at cea dot fr  2005-12-14 19:16 -------
This does not compile, and it is much simpler than ostr(ing)stream:

class A {
public:
    int a;
    A() : a(0) {}
    A& operator<<(int aa) { return *this; }
};

A& operator<<(A& thys, A& (*f)(A&))
{ return f(thys); }

A& tic(A& a)
{ return a; }

int main()
{
    A()    << 12 << tic; // ok
    A a; a << tic << 12; // ok
    //A()    << tic << 12; // does not compile:
#if 0
err.cxx:28: invalid conversion from 'A&(*)(A&)' to 'int'
err.cxx:28:   initializing argument 1 of 'A& A::operator<<(int)'
#endif
}

#if 0
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--host=i386-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-53)
#endif


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

------- Comment #17 from pinskia at gcc dot gnu dot org  2005-12-14 15:11 -------
*** Bug 25410 has been marked as a duplicate of this bug. ***


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aburger at cea dot fr


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[igodard at pacbell dot net]

------- Comment #16 from igodard at pacbell dot net  2005-12-01 00:20 -------
Sorry Gaby; I fat-fingered a partial post. Is there any way to delete a posting
made in error?

Ivan


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[gdr at integrable-solutions dot net]

------- Comment #15 from gdr at integrable-solutions dot net  2005-12-01 00:10 -------
Subject: Re:  ostrstream (buf, size) << "..." does not work properly

"igodard at pacbell dot net" <gcc-bugzilla@gcc.gnu.org> writes:

| Two bugs: 

with no more details, that does not help me :-)

--Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[igodard at pacbell dot net]

------- Comment #14 from igodard at pacbell dot net  2005-12-01 00:06 -------
Two bugs: 
 1) diagnostic, about location of deprecated files
 2) constructor as non-const lvalue, where using a constructor as left-operand
of
    "<<" produces screwey output.

I'm concerned about the second. I can write:
   foo& f = foo();
so the constructor is yielding non-const. I can pass the constructor to a
function:
   void bar(foo& f){}; bar(foo());
So why can't I pass a constructor to operator<< and get the correct output?

Emitting a diagnostic for this usage makes no sense to me.

Ivan

Ivan


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[igodard at pacbell dot net]

------- Comment #13 from igodard at pacbell dot net  2005-11-30 23:58 -------
Two bugs: 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[gdr at gcc dot gnu dot org]

------- Comment #12 from gdr at gcc dot gnu dot org  2005-11-30 23:27 -------
(In reply to comment #11)
> *** Bug 24291 has been marked as a duplicate of this bug. ***
> 

Is thi PR really about "diagnostic"?  I don't see what is "wrong" and
what is not.

-- Gaby


-- 

gdr at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gdr at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925

[Bug c++/9925] ostrstream (buf, size) << "..." does not work properly

[pinskia at gcc dot gnu dot org]

------- Comment #11 from pinskia at gcc dot gnu dot org  2005-10-09 20:54 -------
*** Bug 24291 has been marked as a duplicate of this bug. ***


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |igodard at pacbell dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9925