On Friday, February 27, 2004, at 12:26 , Andrew Dougherty wrote:
On Fri, 27 Feb 2004, Gordon Henriksen wrote:
inet_pton is preferrable, as it supports IPv6.
That is, inet_pton should trump inet_aton if both are available.
Probably, but that would require testing to see if inet_pton is
available
Andrew Dougherty <[EMAIL PROTECTED]> wrote:
> On Fri, 27 Feb 2004, Leopold Toetsch wrote:
[ inet_aton vs inet_pton ]
>> We need a config test here.
> Something like this ought to do the trick for now. Longer term, we need
> to build up some infrastructure for testing for functions on our own. W
Andrew Dougherty wrote:
> On Fri, 27 Feb 2004, Gordon Henriksen wrote:
>
> > On Mac OS X, the preferred technique would be to weak link with
> > inet_pton and test for its availability at run-time. (inet_pton is
> > not available on 10.1, but is available on 10.3.) This would be
> > another cas
On Fri, 27 Feb 2004, Gordon Henriksen wrote:
> inet_pton is preferrable, as it supports IPv6.
> That is, inet_pton should trump inet_aton if both are available.
Probably, but that would require testing to see if inet_pton is available.
That information is not available from perl5's Configure, an
another case
entirely.
--
Gordon Henriksen
IT Manager
ICLUBcentral Inc.
[EMAIL PROTECTED]
> -Original Message-
> From: Andrew Dougherty [mailto:[EMAIL PROTECTED]
> Sent: Friday February 27, 2004 11:52
> To: Perl6 Internals
> Subject: [PATCH] Configure test for inet_aton
On Fri, 27 Feb 2004, Leopold Toetsch wrote:
> Peter Sinnott wrote:
>
> > I have downloaded the snapshot dated 27-Feb-2004 00:01 from
> > http://cvs.perl.org/snapshots/parrot/ and tested it on hpux.
> >
> > I order to get it to compile I have to revert to using inet_aton
> > at line 623 of io_unix
