public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: paolo@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/8469: Obsolete iostream.h and fstream.h? Date: Tue, 05 Nov 2002 16:16:00 -0000 [thread overview] Message-ID: <20021106001603.10200.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/8469; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: rdnjr@houston.rr.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/8469: Obsolete iostream.h and fstream.h? Date: Tue, 5 Nov 2002 19:14:03 -0500 On Tue, Nov 05, 2002 at 09:36:06PM -0000, rdnjr@houston.rr.com wrote: > >Description: > Compiling any program that includes iostream.h, or fstream.h yields an > 'Obsolete header file' warning, but will NOT compile the program. And the error message is...? We're not telepathic. > If I take > those includes out and replace cout's with printf's, so on and so forth, Then you're no longer using the C++ library. > >How-To-Repeat: > compile any program with '#include <iostream.h>', and include a 'cout <<' statement in it. This works for everybody else. The I/O headers with .h were never part of any language standard, so their contents vary from one compiler to another. We provide them just to help in moving old C++ code to correct C++ code. You may be assuming that a .h file provides more than it does. As a start, try including <foo> instead of <foo.h>, and placing a 'using' statement after the header. Phil -- I would therefore like to posit that computing's central challenge, viz. "How not to make a mess of it," has /not/ been met. - Edsger Dijkstra, 1930-2002
next reply other threads:[~2002-11-06 0:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-05 16:16 Phil Edwards [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 14:59 paolo 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=20021106001603.10200.qmail@sources.redhat.com \ --to=phil@jaj.com \ --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: linkBe 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).