Skip Menu |

This queue is for tickets about the IO CPAN distribution.

Report information
The Basics
Id: 55615
Status: rejected
Priority: 0/
Queue: IO

People
Owner: Nobody in particular
Requestors: MACKENNA [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 1.25
Fixed in: (no value)



Subject: Timeout documented but removed
IO::Socket::INET documents a Timeout feature but it's commented out in the source. 1. Shouldn't someone take it out of the POD? 2. Can someone please point me at how to make my own timeout? 3. Idle curiosity: why was it commented out? cmac
Subject: Re: [rt.cpan.org #55615] Timeout documented but removed
Date: Tue, 16 Mar 2010 08:11:21 -0500
To: bug-IO [...] rt.cpan.org
From: Graham Barr <gbarr [...] pobox.com>
On Mar 15, 2010, at 9:46 PM, Craig MacKenna via RT wrote: Show quoted text
> IO::Socket::INET documents a Timeout feature but it's commented out in the source.
Timeout is used by connect, which is inherited from IO::Socket Show quoted text
> 1. Shouldn't someone take it out of the POD?
No, because it is used. Show quoted text
> 2. Can someone please point me at how to make my own timeout?
Show quoted text
> 3. Idle curiosity: why was it commented out?
It was commented out in configure, because it was moved into connect, if anything those comment should be removed Graham.
Subject: Re: [rt.cpan.org #55615] Timeout documented but removed
Date: Tue, 16 Mar 2010 18:20:08 -0700
To: bug-IO [...] rt.cpan.org
From: mackenna [...] animalhead.com
Thank you, I learned all that last night, in addition to how to use IO::Select to time out the subsequent recv. OTOH, you might put in the docs that the Timeout is only used for connect and the other thing. cmac On Mar 16, 2010, at 6:12 AM, Graham Barr via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=55615 > > > > On Mar 15, 2010, at 9:46 PM, Craig MacKenna via RT wrote:
>> IO::Socket::INET documents a Timeout feature but it's commented >> out in the source.
> > Timeout is used by connect, which is inherited from IO::Socket >
>> 1. Shouldn't someone take it out of the POD?
> > No, because it is used. >
>> 2. Can someone please point me at how to make my own timeout?
>
>> 3. Idle curiosity: why was it commented out?
> > It was commented out in configure, because it was moved into > connect, if anything those comment should be removed > > Graham. >
Graham, This ticket caused a little bit of confusion when scanning the RT queue. Can it be closed with a won't fix? Thanks,