From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,ad317a1939529811
X-Google-Attributes: gid103376,public
From: David Shochat <shochat@itg-sepg.logicon.com>
Subject: Re: c2ada and "typedef unsigned char X;"
Date: 1996/05/23
Message-ID: <31A4E58F.7C78@itg-sepg.logicon.com>#1/1
X-Deja-AN: 156399224
references: <31A4D0D2.6A34@itg-sepg.logicon.com>
content-type: text/plain; charset=us-ascii
organization: Logicon Information Technology Group
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.01 (Win95; I)
Date: 1996-05-23T00:00:00+00:00
List-Id: <comp.lang.ada>


Ok, I've figured out that my last post was really off-track. If you give 
c2ada the "typedef unsigned char ..." construct in isolation, it has no 
trouble at all. The problem is that things the tool has trouble with 
*prior to* the line flagged as a syntax error don't show up until that 
line. So a message like:
./sys/machlock.h, line 19, Error: syntax error
really means that there's a problem in the *file that included* 
sys/machlock.h, for example (whatever that may be), or perhaps a file 
that was included earlier by the one referred to in the error message.

So now I'm trying to figure out a logical strategy for tracking down 
these problems so I can do something about them. I just wanted to 
correct the false assertion in my last post.
-- David