Xref: utzoo gnu.gcc:263 comp.os.vms:12559 comp.lang.c:16878
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!ucsd!orion.cf.uci.edu!uci-ics!siam.ics.uci.edu!schmidt
From: schmidt@siam.ics.uci.edu (Doug Schmidt)
Newsgroups: gnu.gcc,comp.os.vms,comp.lang.c
Subject: Re: Problems with GCC and/or VAX LINK
Keywords: globalref, extern, quotation marks
Message-ID: <9044@paris.ics.uci.edu>
Date: 12 Mar 89 00:31:50 GMT
References: <1680@levels.sait.edu.au> <1153@auspex.UUCP>
Sender: news@paris.ics.uci.edu
Reply-To: Doug Schmidt <schmidt@siam.ics.uci.edu>
Followup-To: gnu.gcc
Organization: University of California at Irvine: ICS Dept.
Lines: 23

In article <1153@auspex.UUCP> guy@auspex.UUCP (Guy Harris) writes:
++ However, I'm *extremely* surprised that GCC cares; I don't even think
++ twice about using apostrophes in comments, and I've seen lots of code
++ that uses them.

Lest GCC (cccp actually) acquire the totally undeserved reputation as
``the compiler than can't grok apostrophes in comments'' let me remark
that the current version (1.34) certainly does not have this problem,
nor have I *ever* seen this problem with GCC.  I've been collecting
bug reports since version 1.18 (which appeared over a year ago), and
have not seen this problem mentioned before.  I would be interested
in hearing which release of GCC this purported problem occurred in.

Running ``gcc -v'' will provide the relevant information.

thanks,

   Doug
--
schmidt@ics.uci.edu (ARPA) |   Per me si va nella citta' dolente.
office: (714) 856-4043     |   Per me si va nell'eterno dolore.
                           |   Per me si va tra la perduta gente.
                           |   Lasciate ogni speranza o voi ch'entrate.