From: dj@stealth.ctron.com (DJ Delorie)
To: gas2@cygnus.com
Subject: [ghogenso@u.washington.edu: Problems with .cpp extension: minor annoyances]
Date: Wed, 28 Sep 1994 04:39:00 -0000 [thread overview]
Message-ID: <9409281141.AA06727@delorie> (raw)
Is this the desired behavior? gcc *does* support a lot of file
extensions for each language.
Return-Path: <ghogenso@u.washington.edu>
X-Sender: ghogenso@stein2.u.washington.edu
Date: Tue, 27 Sep 1994 10:25:42 -0700 (PDT)
From: Gordon Hogenson <ghogenso@u.washington.edu>
Sender: Gordon Hogenson <ghogenso@u.washington.edu>
Reply-To: Gordon Hogenson <ghogenso@u.washington.edu>
Subject: Problems with .cpp extension: minor annoyances
To: djgpp@sun.soe.clarkson.edu
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
DJ-Mail-Sort: djgpp@, djgpp
There are a few problems with the .cpp filename extension under
DJGPP. It seems that the various utility programs don't
deal well with it. ld reports errors with the wrong filename
extension -- always 'foo.cc' even if the file is really 'foo.cpp'.
It doesn't seem to be a serious problem with errors and warnings
from ld, since I can easily tell what is meant [although I suppose
editors that rely on this to locate a position in a source file will not
work], but I find that GDB can't find the source files.
It looks for 'foo.cc' when it should be looking for 'foo.cpp'.
Gordon
next reply other threads:[~1994-09-28 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-09-28 4:39 DJ Delorie [this message]
1994-09-28 8:33 ` Ian Lance Taylor
1994-09-28 19:07 ` [ghogenso@u.washington.edu: Problems with .cpp extension] Gordon Hogenson
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=9409281141.AA06727@delorie \
--to=dj@stealth.ctron.com \
--cc=gas2@cygnus.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).