More automated interfacing of D with C codebases

[Jacob Carlborg]

On 2012-10-23 21:43, Brad Lanam wrote:

> Oh, maybe were you thinking that bash is the bourne shell?  It's the
> bourne-again shell, a rewrite of the bourne shell.  Solaris sh is
> probably the closest to the original bourne shell.

I thought I said bash somewhere, but perhaps you didn't.

> My tool runs with any bourne shell compatible shell.  It works
> with bash2, bash3, bash4, ksh, ksh88, ksh93, Solaris sh, Tru64 sh,
> ash, dash, mksh, pdksh. HP-UX sh.

I see.

> You put directives in the "interface file" (to use the SWIG term) to
> test which capabilities the system has.  It creates an output file (.sh,
> .c, .d). Depending on those capabilities, the code can use #if or static
> if statements to provide code that works for the system you are building
> on.
>
> In the case of the C/D language interface, the directives will extract
> typedefs, structures, C function declarations, macros, #defines.

Ok, I see.

-- 
/Jacob Carlborg