What's the skinny on reconciling GDC's std.c.unix.unix and DMD's std.c.linux.linux?

I looked in the archives but am not clear on what needs to be done, etc.

Thanks,

- Dave

In article <dstj9f$2ijb$1@digitaldaemon.com>, Dave says...
>
>
>What's the skinny on reconciling GDC's std.c.unix.unix and DMD's std.c.linux.linux?
>
>I looked in the archives but am not clear on what needs to be done, etc.
>
>Thanks,
>
>- Dave
>

Sorry, this was just discussed but hadn't made it into the archives yet: http://www.digitalmars.com/drn-bin/wwwnews?D.gnu/1610

I think this situation stinks and could and should be taken care of right away. IMHO, this can do nothing but hinder D no matter which compiler.

I'd be willing to do the legwork.

How about moving everything linux in DMD to unix and wrap the linux specific stuff with 'version(linux)'?

It really isn't all that much - what I'd need help with (David/Thomas/Anders) is a list of linux specific stuff that you are aware of in std/c/linux/linux.d and std/c/linux/socket.d.

Below is a list of files that need to be modified (may not be totally complete). Most/all of the mods. to each should be trivial.

Thanks,

- Dave

;---

internal/gc/gclinux.d -> internal/gc/gcunix.d
- internal/gc/gcstub.d
- internal/gc/gcx.d
- internal/gc/linux.mak
- internal/gc/win32.mak
- linux.mak
- win32.mak

std/c/linux -> std/c/unix

std/c/linux/linux.d -> std/c/unix/unix.d
- internal/gc/gclinux.d
- linux.mak
- std/c/linux/linux.d
- std/date.d
- std/file.d
- std/mmfile.d
- std/path.d
- std/process.d
- std/random.d
- std/recls.d
- std/socket.d
- std/stream.d
- std/thread.d
- win32.mak

std/c/linux/linuxextern.d -> std/c/unix/unixextern.d
- internal/deh2.d
- internal/gc/gclinux.d
- linux.mak
- std/c/linux/linux.d
- std/c/linux/linuxextern.d
- std/thread.d
- win32.mak

std/c/linux/socket.d -> std/c/unix/socket.d
- linux.mak
- std/c/linux/socket.d
- std/c/windows/winsock.d
- std/socket.d
- std/socketstream.d
- std.ddoc
- win32.mak