public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	paolo@gcc.gnu.org, rdnjr@houston.rr.com
Subject: Re: libstdc++/8469: Obsolete iostream.h and fstream.h?
Date: Tue, 05 Nov 2002 14:59:00 -0000	[thread overview]
Message-ID: <20021105225950.20347.qmail@sources.redhat.com> (raw)

Synopsis: Obsolete iostream.h and fstream.h?

Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Tue Nov  5 14:59:49 2002
Responsible-Changed-Why:
    .
State-Changed-From-To: open->feedback
State-Changed-By: paolo
State-Changed-When: Tue Nov  5 14:59:49 2002
State-Changed-Why:
    What do you mean exatly by "will NOT compile"?
    I can successfully compile and run the following:
    //////////////////////
    #include <iostream.h>
    int main()
    {
      cout << "Paolo" << endl;
    }
    ////////////////
    paolo:~> g++ paolo.cc
    In file included from /usr/include/c++/3.2.1/backward/iostream.h:31,
                     from paolo.cc:1:
    /usr/include/c++/3.2.1/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.
    paolo:~> a.out
    Paolo
    paolo:~>
    ////////////////
    Could you please provide the output of g++ -v your_test.cc?
    Thanks, Paolo.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8469


             reply	other threads:[~2002-11-05 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 14:59 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 12:30 bkoz
2002-11-07 14:06 R. D. Nichols,  Jr.
2002-11-05 16:16 Phil Edwards
2002-11-05 13:46 rdnjr

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=20021105225950.20347.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rdnjr@houston.rr.com \
    /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).