Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!ucsd!ucbvax!agate!helios.ee.lbl.gov!lll-tis!lll-winken!snll-arpagw!paolucci
From: paolucci@snll-arpagw.UUCP (Sam Paolucci)
Newsgroups: comp.sys.amiga.tech
Subject: Manx 3.6a compiler bug
Message-ID: <173@snll-arpagw.UUCP>
Date: 5 Jun 88 01:16:42 GMT
Reply-To: paolucci@snll-arpagw.UUCP (Sam Paolucci)
Organization: Sandia National Laboratories, Livermore
Lines: 42

Here is a bug in the Manx 3.6a compiler.  It seems that the compiler knows 
about the "const" keyword but is not using it.  I tried to E-Mail this
to Jim Goodnow but the mail keeps bouncing back to me.  I would appreciate
if someone would pass this along to him.  Here is the four line sample
followed by the two compilation outputs.  By the way, the manual says that
internal error 17 means that that data type is not supported. I can't win
in this situation.

/* test.c */

#ifndef ANSI
#define const
#endif

static const short line[] = { 0, 1, 2, 3 };

----------------------------------------------------------------------

cc test.c

Aztec C68K 3.6a  12-18-87  (C) 1982-1987 by Manx Software Systems, Inc.
#define const
             ^
test.c:2: ERROR 115: keyword redefined: const
1 errors

----------------------------------------------------------------------

cc -DANSI test.c

Aztec C68K 3.6a  12-18-87  (C) 1982-1987 by Manx Software Systems, Inc.
static const short line[] = { 0, 1, 2, 3 };
            ^
test.c:5: ERROR 17: internal error: 
1 errors

----------------------------------------------------------------------

					-+= SAM =+-

"the best things in life are free"

				ARPA: paolucci@snll-arpagw.llnl.gov