Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!shelby!mcnc!xanth!uakari.primate.wisc.edu!uwm.edu!cs.utexas.edu!tut.cis.ohio-state.edu!LANL.GOV!dwf%hope
From: dwf%hope@LANL.GOV (David W. Forslund)
Newsgroups: gnu.g++.bug
Subject: Re: g++-1.36.0 file suffix handling
Message-ID: <8910040346.AA02362@hope.lanl.gov>
Date: 4 Oct 89 03:46:52 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 14

I've noticed that g++-1.36.0- uses the file suffix to decide whether
to treat the code as C code or C++ code.  I don't think this is a
proper way to decide how to interpret a file.  I think that C++ code
should be allowed to have .c as suffixes as specified in C++ 2.0.
This certainly was very confusing to me when I was trying to get some
code working under g++ that was running fine under C++ 2.0.

David Forslund
MS E531
Los Alamos National Laboratory
Los Alamos, NM 87545

(505) 665-1907
(dwf@lanl.gov)