Xref: utzoo gnu.gcc:265 comp.os.vms:12564
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!ucsd!orion.cf.uci.edu!iglesias
From: iglesias@orion.cf.uci.edu (Mike Iglesias)
Newsgroups: gnu.gcc,comp.os.vms
Subject: Re: Problems with GCC and/or VAX LINK
Keywords: globalref, extern, quotation marks
Message-ID: <1579@orion.cf.uci.edu>
Date: 12 Mar 89 05:51:16 GMT
References: <1680@levels.sait.edu.au> <1153@auspex.UUCP> <9044@paris.ics.uci.edu>
Reply-To: iglesias@orion.cf.uci.edu (Mike Iglesias)
Followup-To: gnu.gcc
Organization: University of California, Irvine
Lines: 16

In article <9044@paris.ics.uci.edu> Doug Schmidt <schmidt@siam.ics.uci.edu> writes:
>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.

I tried compiling a short test program with a single quote in a
comment with the two GCCs I have for VMS - v1.22 and v1.33.  Neither
one of them had a problem.


Mike Iglesias
University of California, Irvine