From: Eljay Love-Jensen <eljay@adobe.com>
To: "Anthony Christopher'" <anthonyc@blarg.net>, gcc-help@gcc.gnu.org
Subject: Re: bug or not
Date: Sun, 21 Sep 2003 14:59:00 -0000 [thread overview]
Message-ID: <5.2.1.1.0.20030921095602.01967c48@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <3F6D3568.8070106@blarg.net>
Hi Anthony,
The problem isn't that you are using a ostringstream's string-parm constructor.
The problem is that you are printing out the string used to INITIALIZE the ostringstream. What you should be doing is printing out the CURRENT contents of the ostringstream buffer.
Use the...
cout << outBuffer.str() << endl;
...method of accessing the ostringstream's string in the first situation.
HTH,
--Eljay
next prev parent reply other threads:[~2003-09-21 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 5:14 Anthony Christopher'
2003-09-21 14:59 ` Eljay Love-Jensen [this message]
2003-09-21 16:54 Anthony Christopher'
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.2.1.1.0.20030921095602.01967c48@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=anthonyc@blarg.net \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).