Depending on how far you want you go you could use LLVM as a library and write a little program to spit out the data you need, if your on Linux you should be able to install it from the package manager.
I thought about that, but the documentation I saw was incomprehensible.
As far as the types, the only type information you need is sizeof(var)
It's actually even more complicated than that. So, the little program I showed verifies some integer macro values and
typedefs. Ada has a package Interfaces.C which exposes types like Unsigned, Long, and Size_T for their corresponding types, but not types like ssize_t and the gay little shit like socklen_t. What I've shown isn't even the entire problem, however.
The sockaddr structure has a consistent size of sixteen octets across UNIXen, but an annoying little deviation between them. Here's the GNU implementation, or close enough:
C:
struct sockaddr
{
sa_family_t sa_family; /* Address family */
char sa_data[]; /* Socket address */
};
C:
struct sockaddr_in
{
sa_family_t sin_family;
unsigned short int sin_port;
struct in_addr sin_addr;
unsigned char sin_zero[8];
};
This looks simple, albeit retarded, enough. For reference, here's the FreeBSD implementation of the structure:
C:
struct sockaddr {
unsigned char sa_len; /* total length */
sa_family_t sa_family; /* address family */
char sa_data[14]; /* actually longer; address value */
};
Notice that sa_family_t is a short in GNU, and a char in others. That worthless sa_len field is always set to zero, even though its very name calls it a length. Amusingly, a big endian system would hide this difference when treating the two as one, but little endian is the UNIX hacker's common choice.
At least something like the linger structure is simple and consistent across systems. The sockaddr structure actually violates aliasing rules, and basically requires an exception just to work:
C:
struct linger
{
int l_onoff; /* Nonzero to linger on close. */
int l_linger; /* Time to linger. */
};
It's impossible to fuck this up, at least.
Sorry I'm not too familiar with lisp so haven't tried using c with it
This is for an Ada library I've already written, but want to make easier to port and test. Common Lisp has variable interaction with other languages, due to its variety of implementations. ECL, as an example, provides a special form that allows for the direct execution of C language code,
FFI:CLINES and FFI:C-INLINE.
:
