public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9215: Problem with reserting a stream to default using setf
Date: Tue, 07 Jan 2003 16:26:00 -0000	[thread overview]
Message-ID: <20030107162601.2283.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/9215; it has been noted by GNATS.

From: Paolo Carlini <pcarlini@unitus.it>
To: Jon Gjerde <Jon.Gjerde@nr.no>
Cc: paolo@gcc.gnu.org,  gcc-bugs@gcc.gnu.org,  gcc-prs@gcc.gnu.org, 
 nobody@gcc.gnu.org,  gcc-gnats@gcc.gnu.org
Subject: Re: c++/9215: Problem with reserting a stream to default using setf
Date: Tue, 07 Jan 2003 17:20:57 +0100

 Jon Gjerde wrote:
 
 >Thank you for the quick reply.
 >
 >Is your solution cout.setf(ios_base::floatfield, ios_base::floatfield) equal
 >to unsetf(ios_base::floatfield)?
 >
 Yes. An alternate solution would be
 
   cout.setf(ios_base::fmtflags(0), ios_base::floatfield)
 
 >I am now using the latter, and it seems to
 >do the same as setf(0, ios_base::floatfield) when using the Sun CC compiler.
 >Btw, the setf(0, ios_base::floatfield) statement is taken from an example in
 >The C++ Programming language by Bjarne Stroustrup.
 >
 ;)
 
 Well, I may be wrong, but in the _final_ standard I cannot find examples 
 of a 'plain' 0 but always ios_base::fmtflags(0). Otherwise, make use of 
 what I replied earlier today.
 
 Barring any additional clarification on the '0' vs ios_base::fmtflags(0) 
 issue, I would close the PR.
 
 Ciao, Paolo.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9215
 
 


             reply	other threads:[~2003-01-07 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 16:26 Paolo Carlini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 13:36 Jon Gjerde
2003-01-07 12:48 paolo
2003-01-07  9:56 jon.gjerde

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=20030107162601.2283.qmail@sources.redhat.com \
    --to=pcarlini@unitus.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=paolo@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).