[perl #126754] wrong "self" inside class definition inside EVAL inside class

2015-11-27 Thread Brian S. Julin
# New Ticket Created by "Brian S. Julin" # Please include the string: [perl #126754] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126754 > Relatively recent regression: (01:22:01 AM) skids: m: class A { method foo { EVAL "

[perl #123949] Inconsistent APIs for IO::Socket::Async and Proc::Async

2015-11-27 Thread jn...@jnthn.net via RT
Hi, I wrote these issues up in a gist: https://gist.github.com/jnthn/9d8b2e22882d7f7a871e They got some discussion on channel, and the decisions implemented. On Wed Mar 04 01:08:29 2015, moritz wrote: > On 27.02.2015 23:57, Elizabeth Mattijsen wrote: > >> On 27 Feb 2015, at 17:24, Moritz Lenz (

[perl #126315] IO::Socket::INET: a way to read 1 packet

2015-11-27 Thread jn...@jnthn.net via RT
On Fri Oct 09 16:51:39 2015, tokuhirom wrote: > When I'm implementing a http client, I need to read 1 packet data > without expecting size. In socket programming context, this case is > generic requirement. > This is what recv does. > In rakudo's src/core/IO/Socket.pm. It calls nqp::readfh. > >

[perl #116288] Socket read does not "returns $bytes bytes".

2015-11-27 Thread jn...@jnthn.net via RT
On Thu Jan 10 04:43:32 2013, moritz wrote: > On Sat Jan 05 01:10:17 2013, FROGGS.de wrote: > > So if somebody doesnt know the chunk size, (s)he will be unable to use > > read() at all. _If_ you know the chunk size you can say: > > > > last if $data < $chunk-size > > If one doesn't know how much

[perl #126752] [BUG] $/ vs .hyper gets confused

2015-11-27 Thread via RT
# New Ticket Created by zengargoyle # Please include the string: [perl #126752] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126752 > autarch noticed an oddness in File::Temp when used with .hyper: https://gist.github.com/au

Re: [perl #126664] .roll on a Range of Num ain't random

2015-11-27 Thread Elizabeth Mattijsen
So implemented with 61ea661d8dfc04acabf1eb46c Liz > On 27 Nov 2015, at 17:17, Patrick R. Michaud wrote: > > The standard meaning of ".roll" is to randomly select elements > from a list. So I'd expect .roll on a Range to first convert the > Range to a list of values and then select from thos

Re: [perl #126664] .roll on a Range of Num ain't random

2015-11-27 Thread Patrick R. Michaud
The standard meaning of ".roll" is to randomly select elements from a list. So I'd expect .roll on a Range to first convert the Range to a list of values and then select from those. If the intent is to select from the values 0.1, 0.2, 0.3, I'd expect the programmer to write: (0.1, 0.2, 0.3).

Re: [perl #126664] .roll on a Range of Num ain't random

2015-11-27 Thread Moritz Lenz
On 11/26/2015 03:36 PM, Wenzel P. P. Peppmeyer wrote: On Thu, 26 Nov 2015, Elizabeth Mattijsen via RT wrote: (0.1 .. 0.3).roll(10).say; What did you expect? a selection of 0.1, 0.2, 0.3 ?? or 10 random values between 0.1 and 0.3 inclusive? I would (naive) expect 10x a value between 0.1

Re: [perl #126664] .roll on a Range of Num ain't random

2015-11-27 Thread Wenzel P. P. Peppmeyer
On Thu, 26 Nov 2015, Elizabeth Mattijsen via RT wrote: (0.1 .. 0.3).roll(10).say; What did you expect? a selection of 0.1, 0.2, 0.3 ?? or 10 random values between 0.1 and 0.3 inclusive? I would (naive) expect 10x a value between 0.1 and 0.3 . Analog to: (0.1, 0.2, 0.3).roll(10).say; #

[perl #122318] IO::Socket::Async spectest fails sometimes

2015-11-27 Thread jn...@jnthn.net via RT
On Mon Aug 04 02:02:35 2014, elizabeth wrote: > On 04 Aug 2014, at 01:58, Will Coleda via RT follo...@perl.org> wrote: > > On Thu Jul 17 11:06:20 2014, FROGGS.de wrote: > >> perl6-m t/spec/S32-io/IO-Socket-Async.t > >> 1..6 > >> ok 1 - Async listen on bogus hostname > >> ok 2 - Async connect to un

[perl #125515] [BUG] Proc::Async stdout does not tap output in its entirety.

2015-11-27 Thread jn...@jnthn.net via RT
On Tue Jun 30 01:02:15 2015, liu...@360.cn wrote: > https://gist.github.com/anonymous/79a7e59cf3160f6ac09e > > 07:31 kanlrepeating a previous question, is it by design or a > bug that Proc::Async stdout does not tap output in its entirety? ( i > thought it's neither ) > 07:32 moritz kanl: