Re: Your posting is a bit unfortunate

2017-09-20 Thread R0b0t1 
My apologies, I missed this message. The list volume is a bit high so
I had to subscribe to the digest and that has limited my involvement.

On Thu, Jul 27, 2017 at 3:36 AM, Joachim Durchholz  wrote:
> Hi Robot,
>
> Understanding your points, correlating them to past decisions, calling up
> what the decisions actually were and their reasons, finding out which of
> these reasons were good and which were bad - that's already a pretty taxing
> task.
>

I was trying to ask questions about work that, I hope, had aIready
been done. If not, then to me that says decisions were made without
clear forethought.

> Now if you start out with a dismissive attitude such as "The Build System is
> Ridiculous" and continuing with a rant in the message is going to make it
> attractive to answer in a likewise fashion.
> Such an answer wouldn't be constructive, so most community members will
> simply ignore your posting. (Some will ignore you just because they're
> annoyed. We're just humans after all.)
> The result is that you probably already lost a lot of help in fixing the
> issues you'd like to see fixed.
>

A developer has already questioned the validity of modern
cryptography. I no longer have high hopes for Perl 6. Others do not
either, mostly due to concerns about why Perl 6 is so divorced from
Perl 5 and general misgivings about the development lifecycle of the
project so far.

It's unfortunate the message was seen as a rant. I intended it to be
coherent and fairly concise. Sadly from my point of view no one was
able to answer what I hoped to be simple questions about why things
were the way they were.

I wasn't even going to dispute anything offered, for the most part, I
simply wanted some kind of context.

> Disclaimer: I'm more a bystander than an active Perl6 community member.
> This has the advantage of being somewhat impartial (in a limited fashion, I
> found to my own surprise - I was annoyed myself and had to reign that in);
> it has the disadvantage of not really knowing how other community members
> will react, I'm just going out on assumptions there.
>
> I hope I'm helping; please assume I didn't write anything if I'm not.
>

I think you are. I did not mean to be unfriendly, but I was kind of
annoyed after failing, repeatedly, to get Rakudo Star to build. This
is the fourth or fifth project I have encountered that is extremely
hard to bootstrap.

Cheers,
 R0b0t1

Re: Any "note" without the "say"?

2017-09-20 Thread ToddAndMargo 

On 09/18/2017 10:23 AM, Andy Bach wrote:

Er, I was referring more to the P5 behaviour of warn() - w/o a newline, 
its output, to stderr, included more info:

$  perl -e 'warn("hi mom")'  > /dev/null
hi mom at -e line 1.

$  perl -e 'warn("hi mom\n")' > /dev/null
hi mom

"note" appears to append a new line and p6 warn appears to always add 
the extra info.  Looking at

https://docs.perl6.org/routine/warn

I see warn is doing even more that.

Thanks.


Very interesting!  It throws an "exception".

Hm. I wonder how that might be used ...

[perl #132135] IO::Socket::Async's socket-port and peer-port are incorrect

2017-09-20 Thread via RT 
# New Ticket Created by  Justin DeVuyst 
# Please include the string:  [perl #132135]
# in the subject line of all future correspondence about this issue. 
# https://rt.perl.org/Ticket/Display.html?id=132135 >


[jdv@new-host-2 ~]$ perl6 -e 'start react whenever 
IO::Socket::Async.listen(<0.0.0.0>,8889) {say $_.socket-port; say 
$_.peer-port;}; sleep 1;IO::Socket::Async.connect(<0.0.0.0>,8889);sleep 
1;say qx{netstat -tan | grep 8889}'
47394
52436
tcp0  0 0.0.0.0:88890.0.0.0:*   
LISTEN
tcp0  0 127.0.0.1:8889  127.0.0.1:54476 
ESTABLISHED
tcp0  0 127.0.0.1:54476 127.0.0.1:8889  
ESTABLISHED

[jdv@new-host-2 ~]$

Re: can't adverb and infix

2017-09-20 Thread Elizabeth Mattijsen 

> On 19 Sep 2017, at 13:04, Brandon Allbery  wrote:
> 
> On Tue, Sep 19, 2017 at 3:44 AM, Luca Ferrari  wrote:
> this will sound trivial, but the following piece of code that in my
> mind should work does not:
> 
> $mode = 'csv' if ( ! $mode.defined || %available_modes{ $mode }:!exists );
> 
> and the compiler says:
> 
> You can't adverb :<||>
> 
> You want the adverb to be on the postcircumfix; parenthesize the expression. 
> IIRC this was considered the least bad alternative out of an ambiguous parse 
> (i.e. which operation does the adverb apply to?).
> 
> $mode = 'csv' if ( ! $mode.defined || (%available_modes{ $mode }:!exists) 
> );

Or use the lower precedence “or” instead of “||”:

  $mode = 'csv' if ( ! $mode.defined or %available_modes{ $mode }:!exists );


Liz

[perl #132073] [BUG] isa method errors when called on a subset type object

2017-09-20 Thread David Warring via RT 
Final issues resolved with 
https://github.com/rakudo/rakudo/commit/cee1be22cff6153506e31df2916f8a0be27b5fc8

On Sat, 16 Sep 2017 12:12:35 -0700, david.warring wrote:
> Tests added with roast commit
> https://github.com/perl6/roast/commit/d776a06e52c35d6cbb7b7bbade7b7a15b97ecff8
> 
> One remaining todo test for the subset of a subset case, ie:
> 
> subset S of Int; subset S2 of S; say S2.isa(S)
> 
> On Sun, Sep 17, 2017 at 6:34 AM, David Warring
> 
> wrote:
> 
> > After that commit: subset S of Int; S.isa(True) returns true as
> > expected.
> >
> > I've noticed a quibble with subset of a subset:
> >
> > perl6 -e'subset S of Int; subset S2 of S; say S2.isa(S)'
> > False
> >
> > Should be True.
> >
> > On Sun, Sep 17, 2017 at 3:17 AM, Aleks-Daniel Jakimenko-Aleksejev via
> > RT <
> > perl6-bugs-follo...@perl.org> wrote:
> >
> >> What about this commit?
> >> https://github.com/rakudo/rakudo/commit/0704cd97226e63001943
> >> 42c88cef1c5fe711
> >>
> >> On 2017-09-12 13:55:51, david.warring wrote:
> >> > current behavior of isa method on a subset:
> >> >
> >> > % perl6 -v
> >> > This is Rakudo version 2017.08-110-g5f3350656 built on MoarVM
> >> > version
> >> > 2017.08.1-156-g4
> >> > 9b90b99
> >> > implementing Perl 6.c.
> >> > % perl6 -e'subset S of Int; say S.isa(Int)'
> >> > Cannot resolve caller isa(Perl6::Metamodel::SubsetHOW: S, Int);
> >> > none of
> >> > these signatur
> >> > es match:
> >> > (Mu \SELF: Mu $type, *%_)
> >> > (Mu \SELF: Str:D $name, *%_)
> >> > in block  at -e line 1
> >> >
> >> > The documentation https://docs.perl6.org/routine/isa implies this
> >> should
> >> > return True.
> >>
> >>
> >