who own my code?

2017-10-21 Thread ToddAndMargo
Dear List, If I write a program for a customer who pays my labor to write it, who own the program? Me or the customer? Many thanks, -T

Re: who own my code?

2017-10-21 Thread ToddAndMargo
On 10/21/2017 12:40 AM, ToddAndMargo wrote: If I write a program for a customer who pays my labor to write it, who own the program?  Me or the customer? I am a private contractor. What they payed me for fixing a/the problem. They don't care how. I was wondering if they owned any of the code

Re: who own my code?

2017-10-21 Thread Brent Laabs
This depends on the contract you signed with the customer, and laws in your local jurisdiction. As such, it's probably a question more appropriate to ask a lawyer than this list. On Sat, Oct 21, 2017 at 12:57 AM, ToddAndMargo wrote: > On 10/21/2017 12:40 AM, ToddAndMargo wrote: > >> If I write

Re: [perl #132330] Sets can be equal even though their elements aren’t

2017-10-21 Thread Elizabeth Mattijsen
The problem is that both these values have the same .WHICH: $ 6 'say 1e0.WHICH; say (1e0 + 4e-15).WHICH' Num|1 Num|1 Nothing to do with Sets/Bags/Mixes/object hashes. > On 20 Oct 2017, at 17:02, Victor ADAM (via RT) > wrote: > > # New Ticket Created by Victor ADAM > # Please include the str

Re: who own my code?

2017-10-21 Thread ToddAndMargo
On Sat, Oct 21, 2017 at 12:57 AM, ToddAndMargo > wrote: On 10/21/2017 12:40 AM, ToddAndMargo wrote: If I write a program for a customer who pays my labor to write it, who own the program? Me or the customer? I am a private contractor. Wha

Re: who own my code?

2017-10-21 Thread Andrew Kirkpatrick
You'll need to read up on the laws in your area, but generally contracts have IP ownership clauses to ensure the employer ends up with it. Without a contract, it's seems likely there was no such transfer and you remain the owner. On 21 Oct 2017 8:26 PM, "ToddAndMargo" wrote: > On Sat, Oct 21, 20

Re: who own my code?

2017-10-21 Thread ToddAndMargo
On 21 Oct 2017 8:26 PM, "ToddAndMargo" > wrote: On Sat, Oct 21, 2017 at 12:57 AM, ToddAndMargo mailto:toddandma...@zoho.com> >> wrote: On 10/

[perl #132335] [LTA] pure numeric values of address families are not useful enough ( IO::Socket::INET.new(:host, :port(42)) )

2017-10-21 Thread via RT
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132335] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132335 > Code: IO::Socket::INET.new(:host, :port(42)) ¦«2017.

Re: who own my code?

2017-10-21 Thread Theo van den Heuvel
Hi Todd, please discuss this in an appropriate forum. This discussion has absolutely nothing to do with Perl6. Thanks, Theo van den Heuvel

[perl #132337] [BUG] Code block inside `andthen`/`orelse` doesn't close over lexical variables correctly

2017-10-21 Thread via RT
# New Ticket Created by Sam S. # Please include the string: [perl #132337] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132337 > Golfed example: sub foo ($str) { { say $str }() orelse Nil } foo "aa"

[perl #124527] [BOGUSTEST] [REGEX] S05-metasyntax/interpolating-closure.t line:28 reason: 'dunno'

2017-10-21 Thread Sam S. via RT
This look like a bogus test to me. On the RHS of the ~~ operator, `$_` is bound to the LHS string "aaabccc". `$var ??` evaluates the regex $var in boolean context, which causes it to match against this string. Since there is no match, this causes the ternary operator to return the `rx{abc}` br

[perl #126479] [IO] IO::Handle Supply is never done

2017-10-21 Thread Zoffix Znet via RT
On Wed, 28 Oct 2015 17:41:39 -0700, hanenkamp wrote: > Turning a socket or file into a Supply using .Supply works, but the > reactor listening to those events cannot detect a close condition > without using something like an interval to monitor for connection > closure. > > IO::Handle's Supply met

[perl #126479] [IO] IO::Handle Supply is never done

2017-10-21 Thread Zoffix Znet via RT
On Wed, 28 Oct 2015 17:41:39 -0700, hanenkamp wrote: > Turning a socket or file into a Supply using .Supply works, but the > reactor listening to those events cannot detect a close condition > without using something like an interval to monitor for connection > closure. > > IO::Handle's Supply met

[perl #122789] [BUG] `.subst` does not work inside BEGIN block ($/ is set too late)

2017-10-21 Thread Zoffix Znet via RT
Fix: https://github.com/rakudo/rakudo/commit/a62b221a8048238edaa1f6e62070b42ed8bd5cd3 Test: https://github.com/perl6/roast/commit/9585230c26

[perl #122789] [BUG] `.subst` does not work inside BEGIN block ($/ is set too late)

2017-10-21 Thread Zoffix Znet via RT
Fix: https://github.com/rakudo/rakudo/commit/a62b221a8048238edaa1f6e62070b42ed8bd5cd3 Test: https://github.com/perl6/roast/commit/9585230c26

[perl #132283] [REGRESSION] BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods)

2017-10-21 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
https://irclog.perlgeek.de/perl6-dev/2017-10-21#i_15334639 I' think we should test that both are listed, and we can close the ticket. On 2017-10-13 04:50:32, elizabeth wrote: > > On 13 Oct 2017, at 07:52, Aleks-Daniel Jakimenko-Aleksejev (via RT) > > wrote: > > > > # New Ticket Created by Aleks-

[perl #126721] $/ in closure arg of subst

2017-10-21 Thread Zoffix Znet via RT
On Mon, 23 Nov 2015 19:40:36 -0800, raiph wrote: > What I did > == > > $/ := "Uhoh"; > put "Foo".subst: /Foo/, -> $/ {$/}; > put "Foo".subst: /Foo/, -> $/ {$/} for 1; > put "Foo".subst: /Foo/, {$/}; > put "Foo".subst: /Foo/, {$/} for 1; > > What I expected > === >

[perl #126721] $/ in closure arg of subst

2017-10-21 Thread Zoffix Znet via RT
On Mon, 23 Nov 2015 19:40:36 -0800, raiph wrote: > What I did > == > > $/ := "Uhoh"; > put "Foo".subst: /Foo/, -> $/ {$/}; > put "Foo".subst: /Foo/, -> $/ {$/} for 1; > put "Foo".subst: /Foo/, {$/}; > put "Foo".subst: /Foo/, {$/} for 1; > > What I expected > === >

[perl #132339] [REGRESSION] =SEE-ALSO pod comment can no longer be parsed (=SEE-ALSO foo)

2017-10-21 Thread via RT
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132339] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132339 > Code: =SEE-ALSO foo ¦«2017.09,963a0f0657^»: ¦«963a0f0,HEAD(312cac

[perl #132283] [REGRESSION] BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods)

2017-10-21 Thread Brad Gilbert via RT
On Sat, 21 Oct 2017 08:18:46 -0700, alex.jakime...@gmail.com wrote: > https://irclog.perlgeek.de/perl6-dev/2017-10-21#i_15334639 > > I' think we should test that both are listed, and we can close the > ticket. > I don't think we should force all future implementations to add BUILDALL. Especially

Re: [perl #132330] Sets can be equal even though their elements aren’t

2017-10-21 Thread Elizabeth Mattijsen
Which goes back to the behaviour of nqp::unbox_n(): $ 6 'use nqp; say nqp::unbox_n(1e0); say nqp::unbox_n(1e0 + 4e-15)' 1 1 > On 21 Oct 2017, at 11:30, Elizabeth Mattijsen wrote: > > The problem is that both these values have the same .WHICH: > > $ 6 'say 1e0.WHICH; say (1e0 + 4e-15).WHICH' >

[perl #132339] [REGRESSION] =SEE-ALSO pod comment can no longer be parsed (=SEE-ALSO foo)

2017-10-21 Thread Zoffix Znet via RT
On Sat, 21 Oct 2017 09:06:24 -0700, alex.jakime...@gmail.com wrote: > Code: > =SEE-ALSO foo > > > ¦«2017.09,963a0f0657^»: > > > ¦«963a0f0,HEAD(312cac7)»: > ===SORRY!=== Error while compiling /tmp/8cNEnQJfmq > Preceding context expects a term, but found infix = instead > at /tmp/8cNEnQJfmq:1 > -

[perl #132339] [REGRESSION] =SEE-ALSO pod comment can no longer be parsed (=SEE-ALSO foo)

2017-10-21 Thread Zoffix Znet via RT
On Sat, 21 Oct 2017 09:06:24 -0700, alex.jakime...@gmail.com wrote: > Code: > =SEE-ALSO foo > > > ¦«2017.09,963a0f0657^»: > > > ¦«963a0f0,HEAD(312cac7)»: > ===SORRY!=== Error while compiling /tmp/8cNEnQJfmq > Preceding context expects a term, but found infix = instead > at /tmp/8cNEnQJfmq:1 > -

[perl #132341] [BUG] Pod 6 table handling should ensure table rows have the same number of cells even if they are empty

2017-10-21 Thread via RT
# New Ticket Created by Tom Browder # Please include the string: [perl #132341] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132341 > Consider the following pod 6 tables: =begin table a | b | c m | n | o x | y =end table m

[perl #132339] [REGRESSION] =SEE-ALSO pod comment can no longer be parsed (=SEE-ALSO foo)

2017-10-21 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
Just for the record, there was another module affected by this: https://github.com/nkh/P6-Text-Template/blob/5e1752c08ddb064e366be862fd500c4de0c4b833/lib/Text/Template.pm#L142 On 2017-10-21 10:44:51, c...@zoffix.com wrote: > On Sat, 21 Oct 2017 09:06:24 -0700, alex.jakime...@gmail.com wrote: > > C

[perl #132339] [REGRESSION] =SEE-ALSO pod comment can no longer be parsed (=SEE-ALSO foo)

2017-10-21 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
And also: https://github.com/tadzik/perl6-Acme-Meow/blob/35286b14447d22516fbf68767c4d7e18b7396971/lib/Acme/Meow.pm#L65-L69 https://github.com/skids/perl6-Control-Bail/blob/3e6ab6c3bab9176a44476bd0883ba99205306400/lib/Control/Bail.pm6#L81 https://github.com/tadzik/Grammar-BNF/blob/14f51ca5882f00f0ac

[perl #132283] [REGRESSION] BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods)

2017-10-21 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
“I don't think we should force all future implementations to add BUILDALL.” Not sure what this remark is for. Can be rakudo tests. On 2017-10-21 09:12:32, brad wrote: > On Sat, 21 Oct 2017 08:18:46 -0700, alex.jakime...@gmail.com wrote: > > https://irclog.perlgeek.de/perl6-dev/2017-10-21#i_153346

Re: [perl #132283] [REGRESSION] BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods)

2017-10-21 Thread Brandon Allbery
On Sat, Oct 21, 2017 at 12:12 PM, Brad Gilbert via RT < perl6-bugs-follo...@perl.org> wrote: > On Sat, 21 Oct 2017 08:18:46 -0700, alex.jakime...@gmail.com wrote: > > https://irclog.perlgeek.de/perl6-dev/2017-10-21#i_15334639 > > > > I' think we should test that both are listed, and we can close t

Re: [perl #132283] [REGRESSION] BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods)

2017-10-21 Thread Brandon Allbery via RT
On Sat, Oct 21, 2017 at 12:12 PM, Brad Gilbert via RT < perl6-bugs-follo...@perl.org> wrote: > On Sat, 21 Oct 2017 08:18:46 -0700, alex.jakime...@gmail.com wrote: > > https://irclog.perlgeek.de/perl6-dev/2017-10-21#i_15334639 > > > > I' think we should test that both are listed, and we can close t

Re: who own my code?

2017-10-21 Thread Brandon Allbery
On Sat, Oct 21, 2017 at 5:56 AM, ToddAndMargo wrote: > On Sat, Oct 21, 2017 at 12:57 AM, ToddAndMargo >> > wrote: >>> On 10/21/2017 12:40 AM, ToddAndMargo wrote: >>> >>> If I write a program for a customer who pays my labor to >>> write it, who ow

[perl #132283] [REGRESSION] BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods)

2017-10-21 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
You're right, sorry, I should've been more clear. Tickets are not closed without tests, but as you pointed out not everything should be spec-ed. That's correct. Therefore, some tests go to https://github.com/rakudo/rakudo/tree/nom/t (these tests can be changed at any moment and don't serve as a gu