Path: utzoo!telly!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ERIC.CCS.NORTHEASTERN.EDU!steck
From: steck@ERIC.CCS.NORTHEASTERN.EDU (Paul Steckler)
Newsgroups: gnu.gcc.bug
Subject: Char consts/gcc-cpp
Message-ID: <8912090233.AA21191@eric.CCS.Northeastern.EDU>
Date: 9 Dec 89 02:33:45 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 47


Here is a bug in gcc 1.35's preprocessor that I found:

There is a header file on our Sun3 running SunOS 4 used for compiling
SunView applications, /usr/include/sundev/vuid_event.h.

Near the beginning of this header file, instead of a normal C comment,
Sun has something like this:


#ifdef COMMENT

  ....

#endif

Since COMMENT is undefined, this part should be ignored by the
compiler.  However, the preprocessor chokes on this section, because
there is a word that ends in apostrophe t.

The offending line ends with

         	The vuid interface doesn't

The preprocessor says "unterminated character constant" referring,
presumably to the "'t".

Should the preprocessor be doing that level of lexical analysis this
soon?

Here's the output:

> gcc version 1.35
>  /usr/local/lib/gcc-cpp -v -undef -D__GNUC__ -Dmc68000 -Dsun -Dunix 
	-D__mc68000__ -D__sun__ -D__unix__ -Dmc68020 draw_graph.c 
        /tmp/cca26996.cpp
> GNU CPP version 1.35
> /usr/include/sundev/vuid_event.h:39: unterminated character constant


If this has been fixed in 1.36, I apologize, I haven't installed it yet.


  ------------------------------------------------------------------------
 | Paul Steckler                     |     << Were I Britannia,           |
 | steck@eric.ccs.northeastern.edu   |        I'd waive the rules >>      |
  ------------------------------------------------------------------------