From: Jeffrey Holle <jeff.holle@verizon.net>
To: gcc-help@gcc.gnu.org
Subject: incorrect gcc 3.4.1 #pragma use warning
Date: Mon, 26 Jul 2004 03:01:00 -0000 [thread overview]
Message-ID: <ce1s6m$6rc$1@sea.gmane.org> (raw)
Just thought I'd communicate, hopefully to the right people, a problem
I've observed.
In compiling code that compiled cleanly with gcc 2.3.3, with gcc 3.4.1,
I get:
warning: #pragma implementation for calendar.cpp appears after file
is included
The code that produced this was:
#if defined(__GNUG__) && !defined(__APPLE__)
#pragma implementation "calendar.cpp" <-- indicated line
#pragma interface "calendar.cpp"
#endif
There are no inclusions in this file prior to the above code, just a
comment header.
reply other threads:[~2004-07-26 3:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='ce1s6m$6rc$1@sea.gmane.org' \
--to=jeff.holle@verizon.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).