[perl #132349] [REGRESSION] $*IN.getc not blocking on macOS

2017-10-23 Thread Zoffix Znet via RT
On Mon, 23 Oct 2017 09:28:47 -0700, b...@post.pl wrote: > > And some C++ stackoverflow post claimed this was a bug in standard > > library on macos that was fixed in some version already. > > I'll try to get you Sierra (10.12) and High Sierra (10.13) results tomorrow. Added a test (in a branch)

[perl #132349] [REGRESSION] $*IN.getc not blocking on macOS

2017-10-23 Thread Zoffix Znet via RT
On Mon, 23 Oct 2017 09:28:47 -0700, b...@post.pl wrote: > > And some C++ stackoverflow post claimed this was a bug in standard > > library on macos that was fixed in some version already. > > I'll try to get you Sierra (10.12) and High Sierra (10.13) results tomorrow. Added a test (in a branch)

Re: Perl 6: Protecting Intellectual Property for Commercial Code

2017-10-23 Thread Shlomi Fish
Hi James, On Mon, 23 Oct 2017 07:19:34 -0700 James Ellis Osborne III wrote: > Is compilation to bytecode still a todo feature? I managed to get a > solution supporting compilation, serial-based locking, & license expiration > delivered in Python last month for the nuclear industry.. Bytecode >

[perl #132349] [REGRESSION] $*IN.getc not blocking on macOS

2017-10-23 Thread Pawel Pabian via RT
> And some C++ stackoverflow post claimed this was a bug in standard > library on macos that was fixed in some version already. I'll try to get you Sierra (10.12) and High Sierra (10.13) results tomorrow.

[perl #132352] Set operators unfriendly to mutable types

2017-10-23 Thread Sam S. via RT
On Mon, 23 Oct 2017 05:23:55 -0700, c...@zoffix.com wrote: > Set operators are a lot less useful with mutable types, like SetHash, > because > even when one of the operands is a SetHash, they still return a Set, > making > constructs like `∖=` or `∪=` entirely unusable: > > my $days = SetHash.new:

[perl #132349] [REGRESSION] $*IN.getc not blocking on macOS

2017-10-23 Thread Zoffix Znet via RT
On Mon, 23 Oct 2017 07:15:56 -0700, coke wrote: > On Sun, 22 Oct 2017 12:25:07 -0700, b...@post.pl wrote: > > There is no strace on macOS, I used dtruss (dtrace): > > > > $ dtruss -p 1827 > > SYSCALL(args) = return > > fstat64(0x0, 0x7FFF5B18B2F0, 0x1) = 0 0 > > lseek(

[perl #132349] [REGRESSION] $*IN.getc not blocking on macOS

2017-10-23 Thread Zoffix Znet via RT
On Mon, 23 Oct 2017 07:15:56 -0700, coke wrote: > On Sun, 22 Oct 2017 12:25:07 -0700, b...@post.pl wrote: > > There is no strace on macOS, I used dtruss (dtrace): > > > > $ dtruss -p 1827 > > SYSCALL(args) = return > > fstat64(0x0, 0x7FFF5B18B2F0, 0x1) = 0 0 > > lseek(

[perl #132349] [REGRESSION] $*IN.getc not blocking on macOS

2017-10-23 Thread Will Coleda via RT
On Sun, 22 Oct 2017 12:25:07 -0700, b...@post.pl wrote: > There is no strace on macOS, I used dtruss (dtrace): > > $ dtruss -p 1827 > SYSCALL(args) = return > fstat64(0x0, 0x7FFF5B18B2F0, 0x1) = 0 0 > lseek(0x0, 0x0, 0x1) = 54132 0 > write(0x1, "Nil\n\0", 0x

[perl #132349] [REGRESSION] $*IN.getc not blocking on macOS

2017-10-23 Thread Will Coleda via RT
On Sun, 22 Oct 2017 12:25:07 -0700, b...@post.pl wrote: > There is no strace on macOS, I used dtruss (dtrace): > > $ dtruss -p 1827 > SYSCALL(args) = return > fstat64(0x0, 0x7FFF5B18B2F0, 0x1) = 0 0 > lseek(0x0, 0x0, 0x1) = 54132 0 > write(0x1, "Nil\n\0", 0x

[perl #132349] [REGRESSION] $*IN.getc not blocking on macOS

2017-10-23 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
[Coke]++ bisected it to https://github.com/rakudo/rakudo/commit/80bbfcdd47bcb27c21352a53a5156a6ecdd41e65 On 2017-10-22 12:25:07, b...@post.pl wrote: > There is no strace on macOS, I used dtruss (dtrace): > > $ dtruss -p 1827 > SYSCALL(args) = return > fstat64(0x0, 0x7FFF5B18B2F0, 0x1) = 0 0 > lsee

Re: Perl 6: Protecting Intellectual Property for Commercial Code

2017-10-23 Thread Parrot Raiser
Frankly, if you're worried about this sort of thing, you have too much faith in "secret sauces", and not enough in understanding situations thoroughly. Code is trivial, implementation isn't. Back in the days of dBase II, I was a contractor for one ministry of the local government. They asked me to

Re: who own my code?

2017-10-23 Thread Brandon Allbery
On Mon, Oct 23, 2017 at 1:47 AM, Jan Ingvoldstad wrote: > On Sun, Oct 22, 2017 at 10:32 PM, Brandon Allbery > wrote: > > This is still best discussed elsewhere... isn't there a stackexchange for > > this kind of stuff? > > Ah, Stack Exchange, the quality site where the _first_ answer is the > mo

Re: who own my code?

2017-10-23 Thread Parrot Raiser
I agree that this is really not the appropriate forum for this. Type a question like "if I write the same code for several clients, who owns it?" into a search engine, and you'll get a plethora of links. In this case, I would say the fairest thing is to write the sharable portion once on your own

[perl #132353] [LTA] error with using meta assign ops with bound SetHash

2017-10-23 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #132353] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132353 > This code produces an LTA error: my %days := SetHash.new: Date.today … Date.new: '203

[perl #132352] Set operators unfriendly to mutable types

2017-10-23 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #132352] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132352 > Set operators are a lot less useful with mutable types, like SetHash, because even when on

[perl #132287] [REGRESSION][CONC] stall/block in async heavy code

2017-10-23 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
OK, first of all, thank you for the report. The issue is indeed there, and in my opinion it's a significant problem. Secondly, ♥👍 for trying to bisect it manually. Nowadays I only do it with a bot unless I have to trisect rakudo+nqp+moar. However, the result of bisection is wrong (as far as I can

Re: Perl 6: Protecting Intellectual Property for Commercial Code

2017-10-23 Thread Shlomi Fish
Hi Mark, On Sun, 22 Oct 2017 22:37:31 + Mark Devine wrote: > Perl 6 Users, > > [[ Bouncing off Re: who own my code? ]] > > This is the first of several possible spin-off questions, but here goes… > > Perl 6 has its public ecosystem, which will drive growth and adoption. Then > there’s th