willett wrote:
I find there are only five values put in. One, @cf_cv_type_of_bool@, seems to be taken care of by the gpc type CBoolean. Unless I'm missing something, I don't need to do anything about that.
I don't think so. At a quick glance, there seem to be cases where it's set to `int' (i.e., `CInteger'). But I really can't do all the checking -- as I said, I don't think it's really the best way to go, so I won't do the work, sorry.
A second, @cf_cv_typeof_chtype@ is for the type of chtype. Is there any way to compute this in the compiler and have a type?
No, the compiler doesn't know what ncurses' configure script does, that's basically the problem. (And the basic difference compared to `int' etc. -- those are predefined by the C compiler, and thus provided by the backend, so GPC can access them directly.)
Unless you get the results from its output (i.e., ncurses.h) in some way or another, I guess you have to understand the configure script yourself (and I never said this was easy ...).
The only thing I was asking about "compiling in" was additional types to make it easier to write c interfaces that work across all platforms. Frank has given us "CBoolean" and "CInteger" which make it MUCH easier to interface to c cross- platform. Thanks, Frank!
BTW, no false credits please. GPC has always had C compatible types (originally `Integer' = `int'), being GCC based. The change to `CInteger' last year originated from a discussion by Waldek Hebisch, Scott Moore and others. I only did the boring part of it.
Frank