> On 29 Jun 2018, at 09:39, Andy Wingo <wi...@pobox.com> wrote: > > It would seem that the first four > features of C99 are OK for all platforms that we target, with the > following caveats: > > * We should avoid using C++ keywords (e.g. throw) in Guile API files. > > * We might want to avoid mixed decls and statements in inline functions > in Guile API files. > > We should probably avoid stdbool.h and compound literals, for C++ > reasons.
You might make a separate C++ header: It turned out too complicated for Bison to maintain the compile as C++ generated C parser. > In Guile 3.0 (master branch), the types "scm_t_uint8" and so on are now > deprecated. My recommendation is that all users switch to use > e.g. "uint8_t", "ptrdiff_t", etc from <stdint.h> instead of the > scm_t_uint8, etc definitions that they are now using. The definitions > are compatible on all systems, AFAIU, and on GNU, scm_t_uint8 has long > been a simple typedef for uint8_t. For C++, these are only optional, cf. [1], as they require no padding. So an alternative is to typedef the obligatory int_fast<2^k>_t types, perhaps leaving the API unchanged. 1. https://en.cppreference.com/w/cpp/types/integer
