Hi everybody,  I just wanted to ask if anyone can tell me why certain functions aren't defined in the phobos libraries.  They are Windows specific functions and they work correctly in C, but fail in D.  I have also been told to use std.Socket, but they do not have similar functions that I can just replace with.  Anything I can do at this point?  I could really use the help with this.  I am looking forward to the success of D and I see a lot of potential in it. :D

Just some of the functions that are undefined:

WSAEventSelect
BindIoCompletionCallback
AcceptEx
GetAcceptExSockaddrs


Thanks,
V

"V" <v@pathlink.com> wrote in message news:d58oi6$74s$1@digitaldaemon.com...
> Hi everybody,  I just wanted to ask if anyone can tell me why certain functions aren't defined in the phobos libraries.  They are Windows specific functions and they work correctly in C, but fail in D.  I have also been told to use std.Socket, but they do not have similar functions that I can just replace with.  Anything I can do at this point?  I could really use the help with this.  I am looking forward to the success of D and I see a lot of potential in it. :D
>
> Just some of the functions that are undefined:
>
> WSAEventSelect
> BindIoCompletionCallback
> AcceptEx
> GetAcceptExSockaddrs
>
>
> Thanks,
> V

I think there are many Windows functions that aren't defined in std.c.windows.windows. Check out www.dsource.org where I recall a project or two about a more complete set of headers.

Sorry, I meant to say that when I do the link step with ws2_32.lib, kernel32.lib, etc, those functions are not found within and are undefined in said libs.  I have declared them all as extern(Windows) and it compiles without error, but will not link.  Thanks for the help :)



Ben Hinkle wrote:
> "V" <v@pathlink.com> wrote in message news:d58oi6$74s$1@digitaldaemon.com...
> 
>>Hi everybody,  I just wanted to ask if anyone can tell me why certain functions aren't defined in the phobos libraries.  They are Windows specific functions and they work correctly in C, but fail in D.  I have also been told to use std.Socket, but they do not have similar functions that I can just replace with.  Anything I can do at this point?  I could really use the help with this.  I am looking forward to the success of D and I see a lot of potential in it. :D
>>
>>Just some of the functions that are undefined:
>>
>>WSAEventSelect
>>BindIoCompletionCallback
>>AcceptEx
>>GetAcceptExSockaddrs
>>
>>
>>Thanks,
>>V
> 
> 
> I think there are many Windows functions that aren't defined in std.c.windows.windows. Check out www.dsource.org where I recall a project or two about a more complete set of headers. 
> 
> 

Guess I'm the only one with this problem.  Wonder what I could be doing wrong here.  Thanks for the help though.


V wrote:
> Sorry, I meant to say that when I do the link step with ws2_32.lib, kernel32.lib, etc, those functions are not found within and are undefined in said libs.  I have declared them all as extern(Windows) and it compiles without error, but will not link.  Thanks for the help :)
> 
> 
> 
> Ben Hinkle wrote:
> 
>> "V" <v@pathlink.com> wrote in message news:d58oi6$74s$1@digitaldaemon.com...
>>
>>> Hi everybody,  I just wanted to ask if anyone can tell me why certain functions aren't defined in the phobos libraries.  They are Windows specific functions and they work correctly in C, but fail in D.  I have also been told to use std.Socket, but they do not have similar functions that I can just replace with.  Anything I can do at this point?  I could really use the help with this.  I am looking forward to the success of D and I see a lot of potential in it. :D
>>>
>>> Just some of the functions that are undefined:
>>>
>>> WSAEventSelect
>>> BindIoCompletionCallback
>>> AcceptEx
>>> GetAcceptExSockaddrs
>>>
>>>
>>> Thanks,
>>> V
>>
>>
>>
>> I think there are many Windows functions that aren't defined in std.c.windows.windows. Check out www.dsource.org where I recall a project or two about a more complete set of headers.
>>