On Thu, Mar 13, 2008 at 11:57 PM, Patrick Mahan <[EMAIL PROTECTED]> wrote:
>
>
>
> inet_pton() clobbered the fields you pointed out. In fact the sin_family
> field was being set to 0x01 which caused your initial EADDRNOTSUPPORT error
> you were seeing. You quick change fixed that problem. How
Andrew Falanga presented these words - circa 3/13/08 11:11 AM->
On Thu, Mar 13, 2008 at 11:45 AM, Patrick Mahan <[EMAIL PROTECTED]> wrote:
Andrew Falanga presented these words - circa 3/13/08 9:10 AM->
Hi,
See man inet_pton . . . for details.
Briefly, inet_pton() doesn't understand soc
On Thu, Mar 13, 2008 at 11:45 AM, Patrick Mahan <[EMAIL PROTECTED]> wrote:
>
>
> Andrew Falanga presented these words - circa 3/13/08 9:10 AM->
>
> > Hi,
>
> See man inet_pton . . . for details.
>
> Briefly, inet_pton() doesn't understand sockaddr structures. Instead,
> it only understands in_
Andrew Falanga presented these words - circa 3/13/08 9:10 AM->
Hi,
I'd like to know why the inet_pton(3) doesn't fill in the address
family of the proper structure passed into it. I'm at a complete loss
for why. Here's the prototype:
int inet_pton(int af, const char * restrict src, void * r
Hi,
I'd like to know why the inet_pton(3) doesn't fill in the address
family of the proper structure passed into it. I'm at a complete loss
for why. Here's the prototype:
int inet_pton(int af, const char * restrict src, void * restrict dst);
Three arguments only. The address family, hm, I'm
