[sean]

I've written complete C99 bindings for D, they're available here:

http://home.f4.ca/sean/d/stdc.zip

I've left out the headers that don't make sense, and carried over DMC/DMD stuff when necessary/appropriate (copyrights preserved in headers that borrow stuff from DigitalMars, even if it's just a line of code). The files should include pretty much all the standard C99 stuff (some of it tested) and do not include basically any nonstandard functions (alloca being a notable exception).

I am going to write unit tests for these and would like to do some platform-specific headers as well, such as process.h on Win32 and unistd.h for Unix. I would certainly appreciate feedback if folks can spot problems, etc. I am hoping that these files can become a part of Ares and should ultimately not be tied to any specific compiler (so more versioning will be needed in the future).

I imagine any standard library will probably conceal most of this stuff behind D functions, much like std.math wraps std.c.math in Phobos, but it seemed a good idea to have all the C stuff available.

If people bang on this and all seems kosher I may send them off to Walter and see if he's keen on ddropping them into Phobos as well.

[sean]

Just a quick note. I edited signal.d to separate out the standard C signals from the POSIX signals, and the POSIX signals are now in a version(POSIX) block. This should probably become another standard version identifier, unless it makes sense to split it further for different subsets of POSIX support.

[sean]

I decided to do away with the use of aliases in the header files, so now anything that expects wchar_t or wint_t is declared to accept wchar. The alises just got too confusing and weren't particularly useful. wchar_t and NULL are still defined in stddef, but I don't expect anyone to actually use them. Also, the stuff in wchar.h has been spread out among the other headers (since wchar is a keyword and a module can't have that name). So the i/o stuff is in stdio, the string stuff is in string, etc. I'm just getting started on unistd and such, but I don't know how far I'll get as my only resource for this info is a BSD machine (plus web searches) and I may not be able to figure out some of the required constants and types. If there are any linux folks out there willing to help, please let me know.

(edit)

I reinstated the whcar_t and wint_t aliases on friday--I'd forgotten that Unix uses 32-bit wide chars and Windows uses 16-bit wide chars. Darn vague C spec.

[qbert]

I have a linux box here Ill check it out.

Carlos

[kris]

Hey ... that's useful!

[sean]

Thanks a bunch. If you have a copy of sys/types.h that you can post the relevant lines of that would be very helpful as well. I think unistd.h is pretty well sorted, but I still don't have some of the aliases it relies on.

By the way, I updated the lib stuff on friday to use wchar_t aliases. If the version you've got doesn't use them you may want to re-download.

[qbert]

Ok cool,

A couple of problems using .105 with 'long int' s and 'long double's also functions named creal, i just changed to D types using http://www.digitalmars.com/d/ctod.html as a guide. Not sure how to handle the creal function in complex.d:79 ?

Also GCC doesn't fully suport C99 yet ( http://gcc.gnu.org/gcc-3.4/c99status.html ) , getting link once linker errors about functions with the same name ( I guess function overloading is part of C99 ? ). Working on types.h now.

Charlie

[sean]

[larsivi]

[sean]

Thanks.

FYI, I put up a small fix to the headers today. math.d had a few references to "long double" and complex.d had a function called "creal," which I commented out.

[BenHinkle]

[sean]

That's pretty much what I've already done in my C headers. It may mean a bit more work to integrate them with Phobos, but I'll deal with that when it happens--I've considered offering my C headers to Walter, perhaps that would make life easier for all of us