Re: c2ada and "typedef unsigned char X;"

[David Shochat <shochat@itg-sepg.logicon.com>]

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