Re: Naming debate- what's the location for it?

On Thu, Feb 8, 2018 at 2:15 PM, Aaron Sherman wrote: > ... > IMHO, 6 has always been the personal name, but it could be changed to > something that's "sixish" without being an explicit number. Normally, I'd > recommend Latin, but Perl Sex is probably not where anyone wants to go...

Re: Naming debate- what's the location for it?

I think this is a fine place, personally. Past discussions have included these high points as I recall them: 1. Perl is definitely the family name 2. Rakudo started out as the name of an implementation, but started to wander into being the name of the specific leaf in the family tree

Naming debate- what's the location for it?

I recall coming across a post saying the Perl6 name is up for discussion - searched & found this post now https://6lang.party/post/The-Hot-New-Language-Named-Rakudo describes it. Is there a forum where the name's being discussed that I can read? Woke up this morning with a name proposal that

Announce: Rakudo Star Release 2018.01

On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the January 2018 release of "Rakudo Star", a useful and usable production distribution of Rakudo Perl 6. The tarball for this release is available from https://rakudo.perl6.org/downloads/star/. Binaries for macOS and

[perl6/specs] 5e5a0c: Center

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 5e5a0c5dbabac0ab3171608e2af56d25c1c973db https://github.com/perl6/specs/commit/5e5a0c5dbabac0ab3171608e2af56d25c1c973db Author: Zoffix Znet Date: 2018-01-13 (Sat, 13

[perl6/specs] 1c979a: changes for Texas => ASCII

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 1c979ab5a5c85adda27e01c22258e9217219df98 https://github.com/perl6/specs/commit/1c979ab5a5c85adda27e01c22258e9217219df98 Author: Tom Browder Date: 2017-09-29 (Fri, 29 Sep 2017)

[perl6/specs] baec19: Update S27-perl-culture-draft.pod6

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: baec197a059726524d2071062cb29176778a2ae9 https://github.com/perl6/specs/commit/baec197a059726524d2071062cb29176778a2ae9 Author: Xliff Date: 2017-08-24 (Thu, 24 Aug 2017) Changed

RE: Announce: Rakudo Star Release 2017.07

Perl6 Developers, Thank you for your efforts. I'm having a great time working with this language. As a systems person, I'm getting the feeling that this might actually be the "last language I ever have to learn" (cite: Wall). My cantankerous `command` outputs are now very manageable.

Announce: Rakudo Star Release 2017.07

A useful and usable production distribution of Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the July 2017 release of "Rakudo Star", a useful and usable production distribution of Perl 6. The tarball for the July 2017 release is available from

[perl6/specs] 6f12b3: Move doc

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 6f12b30660e8e47afcd76152d18f142a764b3ac2 https://github.com/perl6/specs/commit/6f12b30660e8e47afcd76152d18f142a764b3ac2 Author: Zoffix Znet Date: 2017-07-09 (Sun, 09

[perl6/specs] c2d66a: Try to fix pod

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: c2d66a5cb73506230130ba4d99374bfafe8942b5 https://github.com/perl6/specs/commit/c2d66a5cb73506230130ba4d99374bfafe8942b5 Author: Zoffix Znet Date: 2017-07-09 (Sun, 09

[perl6/specs] 82d2ac: Fix typo

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 82d2acd528c49ec5ff071152c54963485ddb13eb https://github.com/perl6/specs/commit/82d2acd528c49ec5ff071152c54963485ddb13eb Author: Zoffix Znet Date: 2017-07-06 (Thu, 06

[perl6/specs] ef72ef: List De-magicalize '-' in IO::Handle.open

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: ef72ef9f0a71a7b93435704c3c38fc722c264bdb https://github.com/perl6/specs/commit/ef72ef9f0a71a7b93435704c3c38fc722c264bdb Author: Zoffix Znet Date: 2017-07-06 (Thu, 06

[perl6/specs] 658d1e: Propose change to $*ARGFILES inside MAIN

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 658d1e5c35bd36671ea09c13a4cbbfbe4af8460f https://github.com/perl6/specs/commit/658d1e5c35bd36671ea09c13a4cbbfbe4af8460f Author: Zoffix Znet Date: 2017-07-05 (Wed, 05

[perl6/specs] 4ea8b1: Split features into sections

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 4ea8b154253fa80c68e88e23bb100d95cf10b796 https://github.com/perl6/specs/commit/4ea8b154253fa80c68e88e23bb100d95cf10b796 Author: Zoffix Znet Date: 2017-07-05 (Wed, 05

[perl6/specs] 6eff18: Add reasoning for IO::*.chdir/.slurp-rest deprecat...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 6eff18021ff7252ea4c1d0d06be1ea3a709c9e09 https://github.com/perl6/specs/commit/6eff18021ff7252ea4c1d0d06be1ea3a709c9e09 Author: Zoffix Znet Date: 2017-07-05 (Wed, 05

[perl6/specs] 0aa72a: Clarify a bit the $*ARGFILES in MAIN

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 0aa72aa1d9be4dfed15bcedf759907fa83c0d6a6 https://github.com/perl6/specs/commit/0aa72aa1d9be4dfed15bcedf759907fa83c0d6a6 Author: Zoffix Znet Date: 2017-07-05 (Wed, 05

[perl6/specs] 030df4: Fix POD error

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 030df46f1254c88878a51f12e44314155f779a6a https://github.com/perl6/specs/commit/030df46f1254c88878a51f12e44314155f779a6a Author: Zoffix Znet Date: 2017-07-05 (Wed, 05

[perl6/specs] 2eb5cd: Add reminder to toss $*MAIN-ALLOW-NAMED-ANYWHERE

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 2eb5cd1e7a974422b10cb664515bed7de40877ed https://github.com/perl6/specs/commit/2eb5cd1e7a974422b10cb664515bed7de40877ed Author: Zoffix Znet Date: 2017-06-30 (Fri, 30

[perl6/specs] 9c2105: Remove as an alias for \s

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 9c2105171ef8b9a5b0a1970ad3ebd21490d5aefb https://github.com/perl6/specs/commit/9c2105171ef8b9a5b0a1970ad3ebd21490d5aefb Author: Moritz Lenz Date: 2017-06-06 (Tue, 06 Jun 2017)

[perl6/specs] 4b8352: Propose tossing %(), @(), and $() magic shortcuts

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 4b83524181105f88c02127da010e016a690be685 https://github.com/perl6/specs/commit/4b83524181105f88c02127da010e016a690be685 Author: Zoffix Znet Date: 2017-05-29 (Mon, 29

[perl6/specs] 5c9262: Uniquify headlines in S22 to work around a renderi...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 5c9262e200a74d5f553684532143568ceda89ba8 https://github.com/perl6/specs/commit/5c9262e200a74d5f553684532143568ceda89ba8 Author: Stefan Seifert Date: 2017-05-26 (Fri, 26 May 2017)

[perl6/specs] edb5c5: Propose removal of Str.lines: $count param

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: edb5c57af6e75770e095117002c99778347b289a https://github.com/perl6/specs/commit/edb5c57af6e75770e095117002c99778347b289a Author: Zoffix Znet Date: 2017-05-17 (Wed, 17

[perl6/specs] 8638e7: Propose fatalization of all redeclaration warnings

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 8638e717e576daaed6d70dc03613dc28fab7a1d6 https://github.com/perl6/specs/commit/8638e717e576daaed6d70dc03613dc28fab7a1d6 Author: Zoffix Znet Date: 2017-05-16 (Tue, 16

[perl6/specs] 7000e0: Introduce versioning of the META6.json spec for re...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 7000e04e42e3bb31994e5202b52c269457d18dab https://github.com/perl6/specs/commit/7000e04e42e3bb31994e5202b52c269457d18dab Author: Stefan Seifert Date: 2017-05-14 (Sun, 14 May 2017)

[perl6/specs] 93cc00: Update S22 with our current thoughts about depende...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 93cc00c89c8ef4ca90ea109db57f1ece77dce2ec https://github.com/perl6/specs/commit/93cc00c89c8ef4ca90ea109db57f1ece77dce2ec Author: Stefan Seifert Date: 2017-05-14 (Sun, 14 May 2017)

[perl6/specs] dfbaac: Deconfuse auth in the META data.

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: dfbaac8a53a404df8883478062480dbb0eb777fb https://github.com/perl6/specs/commit/dfbaac8a53a404df8883478062480dbb0eb777fb Author: Stefan Seifert Date: 2017-05-14 (Sun, 14 May 2017)

Announce: Rakudo Star Release 2017.04

A useful and usable production distribution of Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the April 2017 release of "Rakudo Star", a useful and usable production distribution of Perl 6. The tarball for the April 2017 release is available from

[perl6/specs] dce35d: META6.json describe how to denote no license or no...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: dce35d18d5cecfe165805635458dfb4f8934080e https://github.com/perl6/specs/commit/dce35d18d5cecfe165805635458dfb4f8934080e Author: Samantha McVey Date: 2017-04-19 (Wed, 19 Apr 2017)

[perl6/specs] 63686a: Update META info for the license section

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 63686a00420cddcf7372f011cdc2a7af7d431c8f https://github.com/perl6/specs/commit/63686a00420cddcf7372f011cdc2a7af7d431c8f Author: Samantha McVey Date: 2017-04-19 (Wed, 19 Apr 2017)

[perl6/specs] 84f5da: Swap IO::Path.child to use .child-secure's code

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 84f5da58d69990eec7102c272657ca0e71783e84 https://github.com/perl6/specs/commit/84f5da58d69990eec7102c272657ca0e71783e84 Author: Zoffix Znet Date: 2017-04-17 (Mon, 17

[perl6/specs] bc769f: Add removed docs commit

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: bc769f1c99c649beb72a04f1530c48b938253f4f https://github.com/perl6/specs/commit/bc769f1c99c649beb72a04f1530c48b938253f4f Author: Zoffix Znet Date: 2017-04-17 (Mon, 17

[perl6/specs]

Branch: refs/heads/open-createonly Home: https://github.com/perl6/specs

[perl6/specs] 9d446a: Add reminder to deprecate IO::Handle.slurp-rest in...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 9d446a48afcc4b32d1288a01c4c941c3566c263f https://github.com/perl6/specs/commit/9d446a48afcc4b32d1288a01c4c941c3566c263f Author: Zoffix Znet Date: 2017-04-11 (Tue, 11

[perl6/specs] 5a7a5a: Add reminder to deprecate IO::Path.chdir in 6.d

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 5a7a5aab8569f903800767bee07beb1c2c07c1b5 https://github.com/perl6/specs/commit/5a7a5aab8569f903800767bee07beb1c2c07c1b5 Author: Zoffix Znet Date: 2017-04-03 (Mon, 03

[perl6/specs] eccde7: Reword requirem,ents for idea submitions

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: eccde7873add6afbe6892a8ee9fadd85db3e6538 https://github.com/perl6/specs/commit/eccde7873add6afbe6892a8ee9fadd85db3e6538 Author: Zoffix Znet Date: 2017-02-28 (Tue, 28

[perl6/specs] 2253c2: Add Int to .Rat/.FatRat tossage proposal too

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 2253c29713f442565e4e7b3f13d4e25adbd6d813 https://github.com/perl6/specs/commit/2253c29713f442565e4e7b3f13d4e25adbd6d813 Author: Zoffix Znet Date: 2017-02-25 (Sat, 25

[perl6/specs] a4cead: Remove dummy precision parameters from...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: a4ceadef10995ad844501cac0c5ad54415a6fd8d https://github.com/perl6/specs/commit/a4ceadef10995ad844501cac0c5ad54415a6fd8d Author: Zoffix Znet Date: 2017-02-25 (Sat, 25

[perl6/specs] c112fa: )

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: c112fa54a8c5118c77da2ea0204b2460aa9d9493 https://github.com/perl6/specs/commit/c112fa54a8c5118c77da2ea0204b2460aa9d9493 Author: Zoffix Znet Date: 2017-02-09 (Thu, 09

[perl6/specs] c6cdaf: Add reminder to un-LTA log(42, 1) error

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: c6cdaff34df0aba6d5bdc8522526ccf20e21836c https://github.com/perl6/specs/commit/c6cdaff34df0aba6d5bdc8522526ccf20e21836c Author: Zoffix Znet Date: 2017-02-09 (Thu, 09

[perl6/specs] 2c8786: Add 6.d for IEEE num division

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 2c8786a52edb1970df7bb600968771aa03ed37f4 https://github.com/perl6/specs/commit/2c8786a52edb1970df7bb600968771aa03ed37f4 Author: Zoffix Znet Date: 2017-02-09 (Thu, 09

Announce: Rakudo Star Release 2017.01

A useful and usable production distribution of Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the November 2016 release of "Rakudo Star", a useful and usable production distribution of Perl 6. The tarball for the January 2017 release is available from

[perl6/specs] d98ee5: Add reminder for 6.d

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: d98ee5412cbde7d220f0bc0a36155d5f9ba60e54 https://github.com/perl6/specs/commit/d98ee5412cbde7d220f0bc0a36155d5f9ba60e54 Author: Zoffix Znet Date: 2017-01-27 (Fri, 27

[perl6/specs] 660070: S15-unicode, change .chars to .codes where this wa...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 660070af5a819dbbca51fc78e7707dee5e69e44c https://github.com/perl6/specs/commit/660070af5a819dbbca51fc78e7707dee5e69e44c Author: Samantha McVey Date: 2017-01-08 (Sun, 08 Jan 2017)

[perl6/specs] fb4024: Synopses no longer primary

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: fb4024c460250cdd8685e3f243cde9290dfcbffe https://github.com/perl6/specs/commit/fb4024c460250cdd8685e3f243cde9290dfcbffe Author: Steve Mynott Date: 2017-01-05 (Thu, 05 Jan 2017)

[perl6/specs] 78c421: S05-regex.pod: clairify that trailing whitespace i...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 78c4211e940306f896086f6304b470a4cdcb954c https://github.com/perl6/specs/commit/78c4211e940306f896086f6304b470a4cdcb954c Author: Samantha McVey Date: 2017-01-01 (Sun, 01 Jan 2017)

[perl6/specs] 61e3e6: Add proposal to codify rules on matching brackets

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 61e3e6c6fa44f4702ccdc91e43aca20996912f47 https://github.com/perl6/specs/commit/61e3e6c6fa44f4702ccdc91e43aca20996912f47 Author: Samantha McVey Date: 2016-12-16 (Fri, 16 Dec 2016)

[perl6/specs] 701141: A few visual formatting changes for the last commi...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 70114176707be219903144530296345bdbbac497 https://github.com/perl6/specs/commit/70114176707be219903144530296345bdbbac497 Author: Samantha McVey Date: 2016-12-16 (Fri, 16 Dec 2016)

[perl6/specs] 37f0ed: Update S15 so as not to include references to a un...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 37f0ed60628b27f800302530cb82672bc0df101c https://github.com/perl6/specs/commit/37f0ed60628b27f800302530cb82672bc0df101c Author: Samantha McVey Date: 2016-12-13 (Tue, 13 Dec 2016)

Re: fixing infinities and ranges etc

On 2016-10-30 4:11 PM, Darren Duncan wrote: On 2016-10-30 5:45 AM, yary wrote: Before/AfterEverything are also easy to understand, and would be as natural to use for sorting strings, eg. for saying if a database NULL should go before the empty string or after everything else. On the other hand,

Re: [PATCH] multiple heredoc beginning in the same line

it's not so difficult, really. you just gotta know the trick: - cd into the repository you want, then run "git am". - Use your mail client's "view source" function (ctrl-u in thunderbird for example). - copy the complete mail source including headers - paste it into the terminal that's running

Re: [PATCH] multiple heredoc beginning in the same line

On Thu, Dec 01, 2016 at 10:15:03AM -0500, Will Coleda wrote: > This will be much more likely to be applied if you provide a pull > request to the repo at https://github.com/perl6/doc I agree but it was a lot simpler for me to send it by e-mail at the moment. I will perhaps try to make a

Re: [PATCH] multiple heredoc beginning in the same line

On Thu, Dec 01, 2016 at 10:46:17AM -0600, andy_b...@wiwb.uscourts.gov wrote: > Hmm: > $ cat /tmp/here.pl6 > my ($first, $second) = qq:to/END1/, qq:to/END2/; > FIRST > MULTILINE > STRING > END1 >SECOND >MULTILINE >STRING >END2 > say "f: $first, s: $second"; > > $ perl6

Re: [PATCH] multiple heredoc beginning in the same line

This will be much more likely to be applied if you provide a pull request to the repo at https://github.com/perl6/doc On Wed, Nov 30, 2016 at 10:31 AM, wrote: > This is to document the fact that, as in POSIX shell, you can use > multiple HEREDOC strings in the same line. >

[PATCH] multiple heredoc beginning in the same line

This is to document the fact that, as in POSIX shell, you can use multiple HEREDOC strings in the same line. --- doc/Language/quoting.pod6 | 14 ++ 1 file changed, 14 insertions(+) diff --git a/doc/Language/quoting.pod6 b/doc/Language/quoting.pod6 index f7fe658..393807b 100644 ---

Announce: Rakudo Star Release 2016.11

On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the November 2016 release of "Rakudo Star", a useful and usable production distribution of Perl 6. The tarball for the November 2016 release is available from . This is the fifth

[perl6/specs] a9f852: suppress mention of dormant or defunct projects

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: a9f8526c5fb8b99c4039fde80d3eb81ead232387 https://github.com/perl6/specs/commit/a9f8526c5fb8b99c4039fde80d3eb81ead232387 Author: Stéphane Payrard Date: 2016-11-15 (Tue, 15 Nov 2016)

[perl6/specs] acc747: Be more specific about coercion being a convention

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: acc747f10f3bb6322d2d8369d273b869df3a49a5 https://github.com/perl6/specs/commit/acc747f10f3bb6322d2d8369d273b869df3a49a5 Author: Stéphane Payrard Date: 2016-11-16 (Wed, 16 Nov 2016)

Re: CALL-ME vs. Callable

I feel like you're focusing on the wrong thing somehow. The issue is not that what nqp is doing is somehow wrong. The issue is that the thing it is doing is necessarily an implementation detail, and as such should be isolated from the language level and any failures/errors exposed as language

Re: CALL-ME vs. Callable

I guess I wasn't clear in what I was asking: What, exactly, was it that NQP was doing? What were the inputs and what was the behavior that you observed? So far, all I have to go on is one example that you feel is not illustrating the broken behavior of NQP that you want to work around with a

Re: CALL-ME vs. Callable

On Mon, Nov 14, 2016 at 5:00 PM, Jon Lang wrote: > So what is the assuming method, and why is it in a callable role? What was > the logic behind that decision? It's perfectly sensible: it's how you implement partial application (which as sadly usual is mis-called

Re: CALL-ME vs. Callable

So what is the assuming method, and why is it in a callable role? What was the logic behind that decision? On Nov 14, 2016 1:38 PM, "Brandon Allbery" wrote: > This should probably have been cc-d to the list. > > Callable claims to be the thing we want. What it actually is,

Re: CALL-ME vs. Callable

This should probably have been cc-d to the list. Callable claims to be the thing we want. What it actually is, is a mix-in that adds the assuming method. I am not sure these can be conflated. Note that the current docs actually do claim it is what I want. This is because I first brought this up

Re: CALL-ME vs. Callable

On Mon, Nov 14, 2016 at 4:28 PM, Aaron Sherman wrote: > So, you said that the problem arises because NQP does something > non-obvious that results in this error. Can you be clear on what that > non-obvious behavior is? It sounds to me like you're addressing a symptom > of a

Re: CALL-ME vs. Callable

So, you said that the problem arises because NQP does something non-obvious that results in this error. Can you be clear on what that non-obvious behavior is? It sounds to me like you're addressing a symptom of a systemic issue. Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google

Re: CALL-ME vs. Callable

Fair points, all. I do think, though that if the concern is really with "the 4 cases when nqp hauls a CALL-ME out of its bowels" then that's what should be addressed... Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and life-long

Re: CALL-ME vs. Callable

Also... On Mon, Nov 14, 2016 at 3:06 PM, Aaron Sherman wrote: > Role-based testing seems very perl6ish. I'd suggest the role name be > "Invocable" with much the sort of signature as you've described. If it's Invokable then the method should probably be INVOKE. It still leaves

Re: fixing infinities and ranges etc

On 2016-10-30 5:45 AM, yary wrote: I'm not sure I entirely understand the proposal- does it change Inf aka ∞ ? Part of the issue I think is that the existing "Inf" aka "∞" don't seem to be very clearly defined. What I could find so far, at least with respect to Ranges, is that they are just

Re: fixing infinities and ranges etc

I'm not sure I entirely understand the proposal- does it change Inf aka ∞ ? Otherwise I like it, and prefer the X::NegInf and X::PosInf,spellings as being easy-to-understand & a good Huffman-encoding. Before/AfterEverything are also easy to understand, and would be as natural to use for sorting

fixing infinities and ranges etc

I have observed that the current Perl 6 spec and implementations seem deficient in regards to representing some special values or conditions, in particular the concept of the two linear directional infinities or otherwise special values that naturally sort before and after everything else.

Re: Documentation for error messages

On Mon, 24 Oct 2016, Parrot Raiser wrote: Where's the best current description of error messages from file "open" commands, and how to control them? `git grep 'does X::IO'` is your best bet right now because some X::IO-exceptions are not documented yet.

Documentation for error messages

Where's the best current description of error messages from file "open" commands, and how to control them? (I'm thinking of things like the effect of adding "\n" to "die" messages in P5.)

Announce: Rakudo Star Release 2016.10

On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the October 2016 release of "Rakudo Star", a useful and usable production distribution of Perl 6. The tarball for the October 2016 release is available from http://rakudo.org/downloads/star/. This is the fourth

[perl6/specs] 5627bd: Remove Signature/Attribute Defaults Based on Defin...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 5627bda79b60f2dd3134ac93c5f58327696add9c https://github.com/perl6/specs/commit/5627bda79b60f2dd3134ac93c5f58327696add9c Author: Zoffix Znet Date: 2016-10-14 (Fri, 14

Re: Is this a bug?

Thank you. Silly me, thinking "this is so simple I don't need to run it through the command-line to test it." :-) Anway, yeah, say $_ for reverse lines Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and life-long student.

Re: Is this a bug?

It may make it clearer if I explain the broader objective. I'm trying to learn P6 thoroughly by developing training courses to teach it from scratch. (Fans of Gerald Weinberg may recognise the idea.) Obviously, while doing so, I want to explore pathological cases, both to clarify the concepts and

Re: Is this a bug?

On 19/09/16 16:02, Aaron Sherman wrote: > I'm guessing that what you meant was "say as a function was what I > meant to > use there." In which case: > > say for reverse lines > > or > > for reverse lines { say } > > These are both valid ways of asking for each element of the iterable > thing

Re: This seems to be wrong

On 19/09/16 15:56, Aaron Sherman wrote:> You can also use map, but it's slightly clunkier: > > "for @inputs.map: .Int -> $i { ... }" This also needs to have "*.Int" or "{ .Int }" otherwise you'll pass $_.Int as the argument to map rather than telling map to call .Int on things.

Re: Is this a bug?

I'm guessing that what you meant was "say as a function was what I meant to use there." In which case: say for reverse lines or for reverse lines { say } These are both valid ways of asking for each element of the iterable thing returned from lines to be printed with a newline. But remember

Re: This seems to be wrong

"for @inputs.map( .prefix:<+> ) {...}" That's spelled: "for @inputs>>.Int -> $i { ... }" You can also use map, but it's slightly clunkier: "for @inputs.map: .Int -> $i { ... }" Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer

Re: This seems to be wrong

D’oh! I’m blind. But I see there’s a multi method Str defined on Any, and you can’t do @inputs.map( .Str ), either (Use of uninitialized value $_ of type Any in string context). Why not? (There’s no multi method Num on Any, even though the docs about Cool seem

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:30 PM Brandon Allbery allber...@gmail.com wrote: > On Sun, Sep 18, 2016 at 6:29 PM, Trey Harris wrote: > >> But I see there’s a multi method Str defined on Any, and you can’t do >> @inputs.map( .Str ), either (Use of

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:36 PM, Trey Harris wrote: > Does not being defined on Any explain why the error for @input.map( .Str ) > is different (Use of uninitialized value $_ of type Any in string context) > than the error for @input.map( .Num ) (Method 'Num' not found for >

Re: Is this a bug?

On Sun, Sep 18, 2016 at 16:49 Parrot Raiser <1parr...@gmail.com> wrote: say { $_ } was the correct thing to use there. (I'm trying to avoid > any mention of O-O for the moment.) > “Trying to avoid any mention of O-O” seems like a Perl 6 obfuscation or golf constraint, not a desirable development

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:29 PM, Trey Harris wrote: > But I see there’s a multi method Str defined on Any, and you can’t do > @inputs.map( .Str ), either (Use of uninitialized value $_ of type Any in > string context). Why not? (There’s no multi method Num on Any, even > though

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:15 PM, Brandon Allbery wrote: > for @inputs.map({ .:<+> }) { ... } Which means the shorter way is: for @inputs.map(+*) { ... } -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:06 PM, Trey Harris wrote: > Not work? It results inMethod 'prefix:<+>' not found for invocant of > class 'Any', but the docs > > > say it is defined as a multi on Any…. > > No, they say it's a multi

Re: Is this a bug?

On Sun, Sep 18, 2016 at 4:49 PM, Parrot Raiser <1parr...@gmail.com> wrote: > What is this -> ;; $_? is raw { #`(Block|170303864) … } output? It's the gist of a Block, which is what you asked for when you did a `say` on an executable block. Why do you believe `say { $_ }` is the right thing

Re: Is this a bug?

It is the .perl representation of a Block. > On 18 Sep 2016, at 22:49, Parrot Raiser <1parr...@gmail.com> wrote: > > say { $_ } was the correct thing to use there. (I'm trying to avoid > any mention of O-O for the moment.) > say {} was a "what happens if I do this" exercise. > > What is this

Re: Is this a bug?

Remember you can call a block with parentheses: > say { 11 + 31 }; -> ;; $_? is raw { #`(Block|140268472711224) ... } > say { 11 + 31 }(); 42 On Sun, Sep 18, 2016 at 12:58 PM, Elizabeth Mattijsen wrote: > I think you want: > > .say for reverse lines; > > not sure what you

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 4:31 PM, Parrot Raiser <1parr...@gmail.com> wrote: > but seems to have a problem with larger numbers: > > 7 > 3 > 21 <- This > 2 > 1 > 0 > 4 > bamm-bamm > barney > (Any) <--- Produces this > betty > fred > 0

This seems to be wrong

This code: #! /home/guru/bin/perl6 # Ask for some numbers from 1 - 7 # and verify that they are in range my @names = < fred betty barney dino wilma pebbles bamm-bamm >; my @inputs = lines(); for @inputs { if $_ ~~ 1..7 { say @names[$_-1]; } else { say "$_ out of

Re: Is this a bug?

I think you want: .say for reverse lines; not sure what you are trying to achieve otherwise, but: say { } producing something like -> ;; $_? is raw { #`(Block|170303864) … } feels entirely correct to me. :-) Liz > On 18 Sep 2016, at 21:52, Parrot Raiser <1parr...@gmail.com>

Is this a bug?

This code: 1 #! /home/guru/bin/perl6 2 3 # Ask for some lines and output them in reverse 4 # Work out the appropriate EOF symbol for the OS 5 6 my $EOF = "CTRL-" ~ ($*DISTRO.is-win ?? "Z" !! "D"); 7 8 say "Please enter some lines and end them with $EOF"; 9 10 say { for reverse lines() {} }; 11 12

Re: Help mechanism in REPL?

FWIW, the .WHY is a method just like any other. What would need to be changed, is the behaviour of Mu.WHY (around line 60 in Mu.pm). > On 10 Sep 2016, at 16:41, Brad Gilbert wrote: > > There was some talk in the past about having `.WHY` look up the > descriptions in the

Re: Help mechanism in REPL?

There was some talk in the past about having `.WHY` look up the descriptions in the POD6 doc ( so that we don't have to bloat Rakudo with that information ) On Fri, Sep 9, 2016 at 6:30 PM, Alex Elsayed wrote: > On Wednesday, 7 September 2016 17:57:32 PDT Parrot Raiser

Re: Help mechanism in REPL?

On Fri, 09 Sep 2016 16:30:28 -0700 Alex Elsayed wrote: > On Wednesday, 7 September 2016 17:57:32 PDT Parrot Raiser wrote: > > This isn't a request for a feature, merely a thought experiment. > > We're still in the phase where it's more important to ensure that > > existing

Re: Help mechanism in REPL?

On Wednesday, 7 September 2016 17:57:32 PDT Parrot Raiser wrote: > This isn't a request for a feature, merely a thought experiment. We're > still in the phase where it's more important to ensure that existing > features work properly than add new ones. > > How difficult would it be to include a

Re: Justification for the "reversed" instruction format

Ah, nice, good to know my concern was unwarranted. On Thu, Sep 8, 2016 at 3:04 PM Aaron Sherman wrote: > In Perl 6, we apply those constraints when you pass off the call to the > ultimate recipient, and that's important because that recipient can have > multiple signatures (and

Re: Justification for the "reversed" instruction format

On Thu, Sep 8, 2016 at 9:23 AM Aaron Sherman a...@ajs.com wrote: I don't know Haskell, but isn't flip just: > > sub flip() { -> $b, $a, |c { f($a, $b, |c) } } > > And then: > > perl6 -e 'sub flip() { -> $a, $b, |c { f($b, $a, |c) } }; my = flip > yas(1,2,3)' > 213 >

<    1   2   3   4   5   6   7   8   9   10   >