[bitc-dev] C interfacing vs. portability
Jonathan S. Shapiro
shap at eros-os.com
Thu Feb 26 17:11:35 EST 2009
Yes to all of what Philipp says, but also, if a C interface is
specified as taking "int" (e.g. anything that is specified as taking
an argument of enum type), it is not correct to specify that argument
as one of {int16, int32, int64}. Any of those answers might be correct
on a particular target, but none of those answers is correct on *all*
targets.
For example, there are LOTS of procedures out there that accept or
return an argument of type size_t, which is a platform-specific
typedef. How should these be typed in BitC?
shap
More information about the bitc-dev
mailing list