c2ada and "typedef unsigned char X;"

c2ada and "typedef unsigned char X;"

[David Shochat]

We have recently switched from Rational's cbind to the enhanced version, 
c2ada by Randy Hudson and Mitch Gart of Intermetrics. I'm fairly new to 
this version and I keep running into the following problem: c2ada 
(aka cbfe) reports a construct of the form:

  typedef unsigned char uchar_t;

as a syntax error. This occurs, for example, in sys/types.h. I've 
studied the documentation 
(http://www.inmet.com/~mg/c2ada/c2ada.html), and although there seem to 
be lots of great things you can do in the Python config file, I didn't 
see anything about typedef's (maybe I missed it).

If anyone knows how to solve this, I'd appreciate hearing about it. 
We're using Solaris 2, by the way.
-- David

Re: c2ada and "typedef unsigned char X;"

[David Shochat]

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