Re: Justification for the "reversed" instruction format

2016-09-08 Thread Aaron Sherman
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 signatures can be added *after* you define the flip). For example: $ cat foo.p6 sub flip() { -> $b, $a, |c { f($a, $b, |c) }

The use of $!attr vs self.attr in core libraries

2016-09-08 Thread Aaron Sherman
In working with Range a while back, I was frustrated to find that writing a subclass that wanted to override an accessor (e.g. for $.min and $.max) was quite difficult because most methods ignored the accessors and called $!min and $!max or wrote to them directly. If I really wanted to change the

Re: Justification for the "reversed" instruction format

2016-09-08 Thread Aaron Sherman
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 Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer,

Re: Justification for the "reversed" instruction format

2016-09-07 Thread Brandon Allbery
On Wed, Sep 7, 2016 at 6:08 PM, Parrot Raiser <1parr...@gmail.com> wrote: > There is a "flip" in P6, to reverse the characters in a string, and a > "reverse", to return the elements of a list. Would either of those be > an equivalent? > Not without an "apply" mechanism used for function / method

Re: Justification for the "reversed" instruction format

2016-09-07 Thread Parrot Raiser
There is a "flip" in P6, to reverse the characters in a string, and a "reverse", to return the elements of a list. Would either of those be an equivalent? On 9/6/16, Trey Harris wrote: > There’s a very common functional programming pattern, usually called flip; > its

Help mechanism in REPL?

2016-09-07 Thread Parrot Raiser
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 mechanism within the REPL to select either documentation or an example,

Re: Justification for the "reversed" instruction format

2016-09-07 Thread Trey Harris
There’s a very common functional programming pattern, usually called flip; its implementation in Haskell is simply: flip :: (a -> b -> c) -> b -> a -> cflip f x y = f y x Getting the same behavior out of a bespoke function in Perl 6 would be easy for any particular case, but writing a

Re: Justification for the "reversed" instruction format

2016-09-06 Thread Aaron Sherman
Oh, and note that you can pass R'd reductions as if they were normal prefix ops: $ perl6 -e 'sub dueet(, *@list) { op @list }; say dueet :<[R-]>, 1..100' -4850 On Tue, Sep 6, 2016 at 12:51 PM, Aaron Sherman wrote: > > > $ perl6 -e 'my @numbers = 1..100; say [-]

Re: Justification for the "reversed" instruction format

2016-09-06 Thread Aaron Sherman
$ perl6 -e 'my @numbers = 1..100; say [-] @numbers; say [R-] @numbers' -5048 -4850 In general, it's kind of pointless with bare infix ops, as you can just reverse the arguments, but when reducing or the like, it becomes much more valuable. On Tue, Sep 6, 2016 at 12:43 PM, Parrot Raiser

Justification for the "reversed" instruction format

2016-09-06 Thread Parrot Raiser
I've just stumbled across "reversed operators", e.g. say 4 R/ 12; # 3 in the documentation. I'm curious to know why the language includes them? I'm having trouble understanding where they would be useful.

Persuasive Business Writing Workshop, SZ & SH,Oct 2016 (by John Sturtevant, Former Harvard Business School Lecturer)

2016-08-30 Thread Chris Wang
Hi There, Good Afternoon! SIS Conference is delighted to invite Mr. John Sturtevant, experienced business writer and trainer, who taught business writing courses at Harvard Business School (HBS) to address the below persuasive writing skills workshop in China. This workshop is an advanced

[perl6/specs] 151d79: Revert "Forbid Bare C<\b> in Regexes"

2016-08-26 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 151d791563ce474709ed38984f883a05ad73dc0b https://github.com/perl6/specs/commit/151d791563ce474709ed38984f883a05ad73dc0b Author: Zoffix Znet Date: 2016-08-25 (Thu, 25 Aug 2016) Changed

[perl6/specs] b14828: Forbid Bare C<\b> in Regexes

2016-08-25 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: b14828bb01abb7e659b9f1a4d43ba572d3a4f173 https://github.com/perl6/specs/commit/b14828bb01abb7e659b9f1a4d43ba572d3a4f173 Author: Zoffix Znet Date: 2016-08-24 (Wed, 24 Aug 2016) Changed

[perl6/specs] 2e72b5: Display historical message based on and not...

2016-08-09 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 2e72b5d1d8f06674b14fef0ba818079eb9189436 https://github.com/perl6/specs/commit/2e72b5d1d8f06674b14fef0ba818079eb9189436 Author: Zoffix Znet Date: 2016-08-09 (Tue, 09

[perl6/specs] ce2925: Add: Signature/Attribute Defaults Based on Defined...

2016-08-09 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: ce29255b71b1a29334ab0028a678f83c3fc51ceb https://github.com/perl6/specs/commit/ce29255b71b1a29334ab0028a678f83c3fc51ceb Author: Zoffix Znet Date: 2016-08-09 (Tue, 09

[perl6/specs] 899560: Add v6d.pod, a place to track proposed language ch...

2016-08-09 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 899560e86ad0279925dd8beb80f108d319aa40fc https://github.com/perl6/specs/commit/899560e86ad0279925dd8beb80f108d319aa40fc Author: Moritz Lenz Date: 2016-08-09 (Tue, 09 Aug 2016)

Announce: Rakudo Star Release 2016.07

2016-07-22 Thread Steve Mynott
On behalf of the Rakudo and Perl 6 development teams, I’m pleased to announce the July 2016 release of “Rakudo Star”, a useful and usable production distribution of Perl 6. The tarball for the July 2016 release is available from http://rakudo.org/downloads/star/. This is the third post-Christmas

[perl6/specs] be783f: prohibit mixing visible and non-visible column sep...

2016-07-12 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: be783f75c4a0e58ce5588e304f8163cb32fca8e8 https://github.com/perl6/specs/commit/be783f75c4a0e58ce5588e304f8163cb32fca8e8 Author: Tom Browder Date: 2016-07-11 (Mon, 11 Jul 2016)

[perl6/specs] f8a00d: further amplify table row and cell requirments and...

2016-07-07 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: f8a00d19534d03ffb3cfb49fc4eee58d79ec1417 https://github.com/perl6/specs/commit/f8a00d19534d03ffb3cfb49fc4eee58d79ec1417 Author: Tom Browder Date: 2016-07-04 (Mon, 04 Jul 2016)

[perl6/specs] fc36bc: clarify use of column separators

2016-07-04 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: fc36bc28f97b792e5668b73e5be8c5ede870f9c3 https://github.com/perl6/specs/commit/fc36bc28f97b792e5668b73e5be8c5ede870f9c3 Author: Tom Browder Date: 2016-07-04 (Mon, 04 Jul 2016)

[perl6/specs] 6c5859: Change nbsp to space in "Perl Hacker".

2016-06-28 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 6c585954460888c3526b5dacf269847117d30850 https://github.com/perl6/specs/commit/6c585954460888c3526b5dacf269847117d30850 Author: Bruce Gray Date: 2016-06-27 (Mon, 27 Jun 2016) Changed

Re: Intalling Perl6

2016-06-26 Thread Brandon Allbery
On Sun, Jun 26, 2016 at 1:51 PM, Julian Brown wrote: > I search for packages on Debian Jessie for Perl 6 and found Rakudo and > Parrot. > > Does everyone install per user and not system-wide? > Does anyone use Parrot instead of Moar? > Debian is, as always, way behind. The

Intalling Perl6

2016-06-26 Thread Julian Brown
I am on Debian Jessie. I went to the Rakudo.org and looked at "how to get it" page and it only offers ways to install it for a particular user, there does not seem to be instructions on how to make it system wide. I was under the impression I wanted Rakudo and Moar. I search for packages on

doc.perl6.org cert expired on 6/25/2016

2016-06-26 Thread Julian Brown

[perl6/specs] 340c68: Change @*INC to @?INC , which was missed in commit...

2016-06-22 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 340c686f87e1597627507d8fd6fddd699f82c2e7 https://github.com/perl6/specs/commit/340c686f87e1597627507d8fd6fddd699f82c2e7 Author: Bruce Gray Date: 2016-06-22 (Wed, 22 Jun 2016) Changed

[perl6/specs] 55ef20: Add a note about used on multiple sites.

2016-06-11 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 55ef20a63b1e6920292acf85e9c44a88682f9ec3 https://github.com/perl6/specs/commit/55ef20a63b1e6920292acf85e9c44a88682f9ec3 Author: Zoffix Znet Date: 2016-06-10 (Fri, 10

[perl6/specs] f9061b: Clarify note

2016-06-11 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: f9061b3ee7a777e77e89f04fba47a0ec5a8954e0 https://github.com/perl6/specs/commit/f9061b3ee7a777e77e89f04fba47a0ec5a8954e0 Author: Zoffix Znet Date: 2016-06-10 (Fri, 10

[perl6/specs] fd990b: Use less of an eye-bleed color and better position...

2016-05-31 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: fd990bf57d6429e21c37b01eae9036f8c1391fcb https://github.com/perl6/specs/commit/fd990bf57d6429e21c37b01eae9036f8c1391fcb Author: Zoffix Znet Date: 2016-05-30 (Mon, 30

[perl6/specs] 9a8149: Match historical message style with that of auto-g...

2016-05-31 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 9a8149f939580523d3fb25d0611d0d03d17e9886 https://github.com/perl6/specs/commit/9a8149f939580523d3fb25d0611d0d03d17e9886 Author: Zoffix Znet Date: 2016-05-31 (Tue, 31

[perl6/specs] 479182: Add note that specs may be outdated on each page (...

2016-05-24 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 479182221597c209a95c0ddb2456afb535fd646d https://github.com/perl6/specs/commit/479182221597c209a95c0ddb2456afb535fd646d Author: Zoffix Znet Date: 2016-05-23 (Mon, 23 May 2016) Changed

[perl6/specs] 04b3cc: Work around the issue of multiple sites using perl...

2016-05-24 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 04b3cc68498256c0a52bbbd0d72f8b6ee451c696 https://github.com/perl6/specs/commit/04b3cc68498256c0a52bbbd0d72f8b6ee451c696 Author: Zoffix Znet Date: 2016-05-23 (Mon, 23 May 2016) Changed

Re: can a method name contain a funny character?

2016-05-21 Thread yary
Thanks for the in-depth analysis. My misunderstanding was about what an identifier considers a number; I have no well-thought-out ideas on the subject of what an identifier ought to be. Having the docs mention that "number" means only characters with a Unicode Property GeneralCategory of Nd might

Re: can a method name contain a funny character?

2016-05-21 Thread Larry Wall
On Fri, May 20, 2016 at 09:39:30AM -0400, yary wrote: : On Tue, Apr 12, 2016 at 6:12 PM, Brandon Allbery : wrote: : > I was explaining why some "symbols" are acceptable to the parser. Which : one : > is more appropriate is not my call, : : I was thinking about what exactly

Re: can a method name contain a funny character?

2016-05-20 Thread yary
To be clear, I expect that "number" in "followed by zero or more word characters (alphabetic, underscore or number)" means "if Unicode thinks it's numeric, you can use it in an identifier after the first character." I don't expect that every numeric codepoint in Unicode must evaluate to number in

Re: can a method name contain a funny character?

2016-05-20 Thread yary
On Tue, Apr 12, 2016 at 6:12 PM, Brandon Allbery wrote: > I was explaining why some "symbols" are acceptable to the parser. Which one > is more appropriate is not my call, I was thinking about what exactly are valid identifiers in Perl6/rakudo's implementation. The docs

Re: Unwanted failure and FAILGOAL

2016-05-11 Thread Moritz Lenz
Hi, On 05/11/2016 07:45 AM, Richard Hainsworth wrote: I have the following in a grammar rule TOP{ ^ + $ }; rule statement { '=' | { { self.panic($/, "Declaration syntax incorrect") } } }; rule endvalue { '(' ~ ')'

Re: Unwanted failure and FAILGOAL

2016-05-11 Thread Damian Conway
Hi Richard, Not a complete answer to your question; just an observation about your grammar: > rule TOP{ ^ + $ }; > > rule statement { '=' > | { { self.panic($/, "Declaration syntax incorrect") } } > }; > > rule endvalue { '(' ~ ')' >

Unwanted failure and FAILGOAL

2016-05-10 Thread Richard Hainsworth
I have the following in a grammar rule TOP{ ^ + $ }; rule statement { '=' | { { self.panic($/, "Declaration syntax incorrect") } } }; rule endvalue { '(' ~ ')' | { self.panic($/, "Invalid declaration.")

[perl6/specs] 5ce9ca: Fix a site search function

2016-05-03 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 5ce9cab30d605de628588a3d0559fe32164bd2d1 https://github.com/perl6/specs/commit/5ce9cab30d605de628588a3d0559fe32164bd2d1 Author: titsuki Date: 2016-05-04 (Wed, 04 May 2016) Changed

[perl6/specs] e094a6: Bring META format closer to reality

2016-05-02 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: e094a61055fc3d597b9870328fe598687bd49c03 https://github.com/perl6/specs/commit/e094a61055fc3d597b9870328fe598687bd49c03 Author: Jonathan Stowe Date: 2016-05-02 (Mon, 02 May 2016)

[perl6/specs] 7bc794: [S07] change .push example (which doesn't follow o...

2016-04-26 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 7bc794550740055287da15c81460c9d8eaabb51a https://github.com/perl6/specs/commit/7bc794550740055287da15c81460c9d8eaabb51a Author: David Warring Date: 2016-04-26 (Tue, 26 Apr 2016)

Announce: Rakudo Star Release 2016.04

2016-04-25 Thread Steve Mynott
# Announce: Rakudo Star Release 2016.04 ## A useful and usable production distribution of Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm honored to announce the April 2016 release of "Rakudo Star", a useful and usable production distribution of Perl 6. The tarball for the April

[perl6/specs] 73f566: [S11] Typo fix

2016-04-22 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 73f566e8f65381f3d324c85dd0a79b9961bf8ed4 https://github.com/perl6/specs/commit/73f566e8f65381f3d324c85dd0a79b9961bf8ed4 Author: Tadeusz Sośnierz Date: 2016-04-21 (Thu, 21 Apr

Announce: [SixFix] A weekly dose of Perl 6 delivered to your inbox

2016-04-18 Thread Nigel Hamilton
SixFix is a weekly email with something new to learn about Perl 6. But there's a catch! Each email includes a coding challenge and a question about Perl 6 you must answer to receive your next SixFix. SixFix helps you learn Perl 6 with practical coding exercises (approx 1/2 an hour each week). You

Re: A practical benchmark shows speed challenges for Perl 6

2016-03-30 Thread yary
On Wed, Mar 30, 2016 at 3:20 PM, Elizabeth Mattijsen wrote: > Thanks for your thoughts! > > I’ve implemented $*DEFAULT-READ-ELEMS in > https://github.com/rakudo/rakudo/commit/5bd1e . > > Of course, all of this is provisional, and open for debate and bikeshedding. Thanks! And

Re: A practical benchmark shows speed challenges for Perl 6

2016-03-30 Thread Elizabeth Mattijsen
> On 30 Mar 2016, at 16:06, yary wrote: > > Cross-posting to the compiler group- > > On Wed, Mar 30, 2016 at 8:10 AM, Elizabeth Mattijsen wrote: >> If you know the line endings of the file, using >> IO::Handle.split($line-ending) (note the actual character,

Re: A practical benchmark shows speed challenges for Perl 6

2016-03-30 Thread yary
Cross-posting to the compiler group- On Wed, Mar 30, 2016 at 8:10 AM, Elizabeth Mattijsen wrote: > If you know the line endings of the file, using > IO::Handle.split($line-ending) (note the actual character, rather than a > regular expression) might help. That will read in

[perl6/specs] e441a2: Pass 2 at react/supply blocks, clarify some gramma...

2016-02-28 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: e441a27c70bba7f4d531c2c7a713ac15f1ae1298 https://github.com/perl6/specs/commit/e441a27c70bba7f4d531c2c7a713ac15f1ae1298 Author: skids Date: 2016-02-26 (Fri, 26 Feb 2016) Changed paths:

[perl6/specs] 33eaff: Update Supply introduction and method docs for ser...

2016-02-26 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 33eaffeb784e1f2b61511b727ef614615df6bca8 https://github.com/perl6/specs/commit/33eaffeb784e1f2b61511b727ef614615df6bca8 Author: skids Date: 2016-02-25 (Thu, 25 Feb 2016) Changed paths:

Re: Perl 6 mentions on Wikipedia

2016-02-26 Thread Dan Stephenson
I want in. I'm working on a production project for cloud computing that fuses 5 and 6 together. It's proving very useful... Sent from my iPhone > On Feb 25, 2016, at 4:26 PM, Damian Conway wrote: > > Dear fellow revellers in the dawning Golden Age of Perl 6, > > I just

Perl 6 mentions on Wikipedia

2016-02-25 Thread Damian Conway
Dear fellow revellers in the dawning Golden Age of Perl 6, I just had a colleague contact me, to express their surprise that Perl 6 does not rate a mention in: https://en.wikipedia.org/wiki/Functional_programming. The Perl 6 community (and Larry in particular) has already done an incredible

Re: Blogging on Perl6 anonymous proto/multi

2016-02-15 Thread Lloyd Fournier
I made a comment on your blog which is awaiting moderation. Anyways here it is for people on the mailing list: I agree that being able to compose dispatchers and candidates procedurally is very useful. And you can sorta do it. Check out:

Blogging on Perl6 anonymous proto/multi

2016-02-14 Thread yary
Back in June of last year some discussion about multi-subs got me thinking and posting about anonymous proto/multi routines here. It's been bubbling in the back of my mind since then, and as my Valentine to the language, I've posted my thoughts at

Announce: Mac OS X Installer for release 2016.01

2016-02-12 Thread Tobias Leich
Thanks to Steve Mynott a Mac OS X installer is now available. This installer has the ".dmg" file extension and is available from http://rakudo.org/downloads/star/.

Re: It's time to use "use 6.c"

2016-02-09 Thread Peter Pentchev
On Sat, Feb 06, 2016 at 08:20:14PM -0500, yary wrote: > Thanks all... I expect hiccups... just venting to help (future coders > and current self)... while we're on this topic > > a) lwp-download.pl doesn't have a "use 6". Since Windows ignores the > shebang, it invokes perl5 which is registered

Re: It's time to use "use 6.c"

2016-02-09 Thread Brandon Allbery
On Tue, Feb 9, 2016 at 5:38 AM, Peter Pentchev wrote: > For the record, just to clear up some possible confusion, "use 6.c" > doesn't work in source files; you need "use v6.c". > Clarifying: yary seems to have been confused by the fact that META6.json (only) needs to use

Re: It's time to use "use v6.c"

2016-02-07 Thread Steve Mynott
The windows p6doc fix at http://perl6.org/downloads/ has been updated. On 6 February 2016 at 21:17, Steve Mynott wrote: > Are you using windows? > > From the recently updated http://perl6.org/downloads/ > > "p6doc was broken on Windows. Fix is to, with Git in the %PATH%,

Re: It's time to use "use v6.c"

2016-02-07 Thread yary
"panda --force install p6doc" fixed it for me!

Re: It's time to use "use v6.c"

2016-02-06 Thread Darren Duncan
On 2016-02-06 11:35 AM, Brandon Allbery wrote: On Sat, Feb 6, 2016 at 2:30 PM, yary wrote: this morning I installed the 2016.01 R*. Now I'm at the NYC perl6 study group, and a helpful neighbor asked me to start up p6doc. This is something of an edge case. It is

It's time to use "use v6.c"

2016-02-06 Thread yary
this morning I installed the 2016.01 R*. Now I'm at the NYC perl6 study group, and a helpful neighbor asked me to start up p6doc. It gave me an error about EVAL being dangerous, and after opening a ticket & adding "use MONKEY-SEE-NO-EVAL" to my source, I got "Undeclared name:CompUnitRepo used

Re: It's time to use "use v6.c"

2016-02-06 Thread Brandon Allbery
On Sat, Feb 6, 2016 at 2:30 PM, yary wrote: > this morning I installed the 2016.01 R*. Now I'm at the NYC perl6 > study group, and a helpful neighbor asked me to start up p6doc. > This is something of an edge case. It is reasonable for stuff that is supposed to ship *with*

Re: It's time to use "use v6.c"

2016-02-06 Thread Steve Mynott
Are you using windows? >From the recently updated http://perl6.org/downloads/ "p6doc was broken on Windows. Fix is to, with Git in the %PATH%, "panda --force install p6doc" and delete C:\rakudo\bin\p6doc.bat." S On 6 February 2016 at 19:30, yary wrote: > this morning I

[perl6/specs] b10af0: point out ".ast" is an alternative to ".made".

2016-02-06 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: b10af0c107266bd625e2de7ee61d1e75e87a3c88 https://github.com/perl6/specs/commit/b10af0c107266bd625e2de7ee61d1e75e87a3c88 Author: Timo Paulssen Date: 2016-02-06 (Sat, 06 Feb

Re: It's time to use "use 6.c"

2016-02-06 Thread yary
Thanks all... I expect hiccups... just venting to help (future coders and current self)... while we're on this topic a) lwp-download.pl doesn't have a "use 6". Since Windows ignores the shebang, it invokes perl5 which is registered to handle "pl" files, and gives a bunch of syntax errors. If it

Announce: Windows MSI Installers for release 2016.01

2016-02-04 Thread Tobias Leich
The Windows MSI installers are now available, coming again in two versions. One installer targets x86 (32bit) platforms, and the other installer targets x86_64 (64bit) platforms (probably Windows 7 or better). Only the version for x86_64 comes with JIT enabled. The two MSIs are available from

[perl6/specs] 983eaa: Fix example of "perl" META key

2016-02-04 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 983eaa76cee0ff46a35859a7f0c8ec4ef77f12b8 https://github.com/perl6/specs/commit/983eaa76cee0ff46a35859a7f0c8ec4ef77f12b8 Author: Zoffix Znet Date: 2016-02-04 (Thu, 04

Announce: Rakudo Star Release 2016.01

2016-02-03 Thread Tobias Leich
# Announce: Rakudo Star Release 2016.01 ## A useful and usable production distribution of Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm happy to announce the January 2016 release of "Rakudo Star", a useful and usable production distribution of Perl 6. The tarball for the

Re: Are proposals for new language methods considered?

2016-01-31 Thread Will Coleda
The language is intended to evolve; the specification will change as we go. If you have a proposal, go ahead and make it, see what traction it gets on the list. On Sun, Jan 31, 2016 at 8:27 AM, Tom Browder wrote: > I would like to propose some new Str and IO::Path methods

Re: Are proposals for new language methods considered?

2016-01-31 Thread Tom Browder
On Sun, Jan 31, 2016 at 5:01 PM, Will Coleda wrote: > The language is intended to evolve; the specification will change as we go. > > If you have a proposal, go ahead and make it, see what traction it > gets on the list. Is there any specific format for a proposal? If not, is

Re: Are proposals for new language methods considered?

2016-01-31 Thread Will Coleda
Nope. Most people just show up on #perl6 and chat, or make a pull request or open an RT. On Sun, Jan 31, 2016 at 6:10 PM, Tom Browder wrote: > On Sun, Jan 31, 2016 at 5:01 PM, Will Coleda wrote: >> The language is intended to evolve; the specification

Re: Are proposals for new language methods considered?

2016-01-31 Thread Tom Browder
On Sun, Jan 31, 2016 at 5:20 PM, Will Coleda wrote: > Nope. Most people just show up on #perl6 and chat, or make a pull > request or open an RT. Gotcha, thanks. -Tom

Are proposals for new language methods considered?

2016-01-31 Thread Tom Browder
I would like to propose some new Str and IO::Path methods if such would be considered. Best regards, -Tom

Re: Rationale for $!

2016-01-28 Thread Moritz Lenz
Hi, On 01/28/2016 04:06 PM, Todd C. Olson wrote: > Is there a way to make the exception be thrown eagerly, at the devision > statement rather than waiting until use, at the say statement? Yes, 'use fatal;' Cheers, Moritz

Re: Rationale for $!

2016-01-28 Thread Brandon Allbery
On Wed, Jan 27, 2016 at 11:00 AM, Felipe Gasper wrote: > Unrelated, but, does open() not throw on failures anyway? (Noodling with > the perl6 REPL just now seems inconclusive.) There have been issues with failures in sink context not throwing, IIRC? So how you were

Re: Rationale for $!

2016-01-28 Thread Brandon Allbery
On Wed, Jan 27, 2016 at 11:06 AM, Felipe Gasper wrote: > On 27 Jan 2016 11:03 AM, Brandon Allbery wrote: >> >> On Wed, Jan 27, 2016 at 11:00 AM, Felipe Gasper > > wrote: >> >> Unrelated, but, does open() not

Re: Rationale for $!

2016-01-28 Thread Todd C. Olson
Slight change in focus of question ... > On We 2016-01-27, at 09:15, Felipe Gasper wrote: > --- > use v6; > > my $x = 10; > my $y = 0; > > my $z = $x / $y; > > my $exception; > { >{ >say $z; >CATCH { >default { >

Re: Rationale for $!

2016-01-27 Thread Peter Pentchev
On Wed, Jan 27, 2016 at 10:32:46AM -0500, Felipe Gasper wrote: [snip] > But, what is the point of $! at all? The exception is given to the CATCH > block as $_. If I want access to it outside CATCH, isn’t the expected > workflow to save CATCH{$_} to a variable, the way my example does it? Well, it

Re: Rationale for $!

2016-01-27 Thread Moritz Lenz
On 01/27/2016 04:32 PM, Felipe Gasper wrote: On 27 Jan 2016 10:15 AM, Moritz Lenz wrote: On 01/27/2016 03:15 PM, Felipe Gasper wrote: So, what *is* the scoping of $!? Scoped to a routine, iirc (sub, method, regex) Interesting. JavaScript programmers that I’ve known bemoan that their

Re: Rationale for $!

2016-01-27 Thread Felipe Gasper
On 27 Jan 2016 10:56 AM, Moritz Lenz wrote: But, what is the point of $! at all? Convenience. It makes it easy to write commonly-used constructs much faster. My mostly unscientific approach to gather usage of try vs. CATCH in the ecosystem: moritz@hack:~/p6/perl6-all-modules$ git grep --word

Re: Rationale for $!

2016-01-27 Thread Felipe Gasper
On 27 Jan 2016 11:03 AM, Brandon Allbery wrote: On Wed, Jan 27, 2016 at 11:00 AM, Felipe Gasper > wrote: Unrelated, but, does open() not throw on failures anyway? (Noodling with the perl6 REPL just now seems inconclusive.)

Re: Rationale for $!

2016-01-27 Thread Felipe Gasper
On 27 Jan 2016 10:44 AM, Peter Pentchev wrote: On Wed, Jan 27, 2016 at 10:32:46AM -0500, Felipe Gasper wrote: [snip] But, what is the point of $! at all? The exception is given to the CATCH block as $_. If I want access to it outside CATCH, isn’t the expected workflow to save CATCH{$_} to a

Re: Rationale for $!

2016-01-27 Thread Felipe Gasper
On 27 Jan 2016 10:15 AM, Moritz Lenz wrote: On 01/27/2016 03:15 PM, Felipe Gasper wrote: So, what *is* the scoping of $!? Scoped to a routine, iirc (sub, method, regex) Interesting. JavaScript programmers that I’ve known bemoan that their language uses function scoping rather than block

Re: Rationale for $!

2016-01-27 Thread yary
On Wed, Jan 27, 2016 at 11:00 AM, Felipe Gasper wrote: > Could it not be: > > try my $f = open(...) or die … > Don't need a "try" there to make it work. An exception object/failure is false, so "my $f = open(...) or die" will assign the exception to $f, which is false,

Re: Rationale for $!

2016-01-27 Thread Moritz Lenz
Hi, On 01/27/2016 07:17 AM, Felipe Gasper wrote: Hello, What is the purpose of having $! in Perl 6? The global variables in Perl 5 are a constant headache, prompting us to need to local()ize variables like $@, $!, and $? to avoid unforeseen consequences like RT #127386 and those

Re: Rationale for $!

2016-01-27 Thread Felipe Gasper
On 27 Jan 2016 7:15 AM, Moritz Lenz wrote: On 01/27/2016 07:17 AM, Felipe Gasper wrote: Hello, What is the purpose of having $! in Perl 6? The global variables in Perl 5 are a constant headache, prompting us to need to local()ize variables like $@, $!, and $? to avoid unforeseen

Re: Rationale for $!

2016-01-27 Thread Moritz Lenz
On 01/27/2016 03:15 PM, Felipe Gasper wrote: So, what *is* the scoping of $!? Scoped to a routine, iirc (sub, method, regex)

Rationale for $!

2016-01-26 Thread Felipe Gasper
Hello, What is the purpose of having $! in Perl 6? The global variables in Perl 5 are a constant headache, prompting us to need to local()ize variables like $@, $!, and $? to avoid unforeseen consequences like RT #127386 and those documented in Try::Tiny’s POD. Perl 6 seems to

[perl6/specs] cbb897: remove leading v in version example

2016-01-25 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: cbb8978d60889be271a721c5b83152fa7cb97ba7 https://github.com/perl6/specs/commit/cbb8978d60889be271a721c5b83152fa7cb97ba7 Author: Steve Mynott Date: 2016-01-23 (Sat, 23 Jan 2016)

[perl6/specs] db4354: update perl version example to use 6.c type vers

2016-01-25 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: db43544188b774d1fe51d85a9293b1190503bb2b https://github.com/perl6/specs/commit/db43544188b774d1fe51d85a9293b1190503bb2b Author: Steve Mynott Date: 2016-01-23 (Sat, 23 Jan 2016)

[perl6/specs] 771304: c

2016-01-25 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/perl6/specs
  Commit: 7713048d6e00b77cf583ff8b7f064cb98a143aa6

[perl6/specs] ca0a0b: delete file accidentally checked

2016-01-25 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: ca0a0bc610201ef3bbe75b0dce998b8f27f0f5fa https://github.com/perl6/specs/commit/ca0a0bc610201ef3bbe75b0dce998b8f27f0f5fa Author: Stéphane Payrard Date: 2016-01-23 (Sat, 23 Jan 2016)

[perl6/specs] 73ff49: META doesn't need an entire glossary to itself

2016-01-18 Thread GitHub
Branch: refs/heads/meta-v1 Home: https://github.com/perl6/specs Commit: 73ff494a2b3c051a9cabd97a0a7ebc874aa7aa29 https://github.com/perl6/specs/commit/73ff494a2b3c051a9cabd97a0a7ebc874aa7aa29 Author: Anthony Parsons Date: 2016-01-17 (Sun, 17 Jan 2016)

[perl6/specs] 216855: [S04] Add missing parenthesis in zip() example

2016-01-18 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 2168554941a2c85b7c3a1512382a965aa3139258 https://github.com/perl6/specs/commit/2168554941a2c85b7c3a1512382a965aa3139258 Author: Sterling Hanenkamp Date: 2016-01-16 (Sat, 16 Jan

[perl6/specs] 71d0c0: [S32::Containers] Change duplicate =item of `pairs...

2016-01-02 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 71d0c0c1fa672054f0da3409b742653b5bd92b3a https://github.com/perl6/specs/commit/71d0c0c1fa672054f0da3409b742653b5bd92b3a Author: Bruce Gray Date: 2016-01-02 (Sat, 02 Jan 2016) Changed

[perl6/specs] fd1245: Speculatively make versions agree on a format

2016-01-01 Thread GitHub
Branch: refs/heads/meta-v1 Home: https://github.com/perl6/specs Commit: fd1245cc0e5a14fadfba17dfa1116598bacbfa9d https://github.com/perl6/specs/commit/fd1245cc0e5a14fadfba17dfa1116598bacbfa9d Author: Anthony Parsons Date: 2015-12-31 (Thu, 31 Dec 2015)

[perl6/specs] 73ea63: S99: Correct heading level

2016-01-01 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 73ea63dc52bf0d3610128b5215828952b28ed5c4 https://github.com/perl6/specs/commit/73ea63dc52bf0d3610128b5215828952b28ed5c4 Author: Moritz Lenz Date: 2016-01-01 (Fri, 01 Jan 2016)

[perl6/specs] 325f7b: fix syntax in the advent calendar entry

2015-12-31 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 325f7b27620e46bef87553c11cf943be8e0c72e1 https://github.com/perl6/specs/commit/325f7b27620e46bef87553c11cf943be8e0c72e1 Author: Lucien Grondin Date: 2015-12-30 (Wed, 30 Dec 2015)

[perl6/specs] 6c54ce: fix title of S08

2015-12-31 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 6c54ce5133f9b3afe2755b489feda58debf9bd66 https://github.com/perl6/specs/commit/6c54ce5133f9b3afe2755b489feda58debf9bd66 Author: John Gabriele Date: 2015-12-30 (Wed, 30 Dec 2015)

[perl6/specs] 7a0988: Make an allowance for future META6 versioning

2015-12-31 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 7a09880494d5a26b75023904a55dd5dd1df7e96c https://github.com/perl6/specs/commit/7a09880494d5a26b75023904a55dd5dd1df7e96c Author: Anthony Parsons Date: 2015-12-31 (Thu, 31 Dec 2015)

[perl6/specs] 60cf34: Stringy versions shouldn't be /^v/, jdv79++

2015-12-31 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 60cf346f640a2ca50cd8712315f3b4df453fe48b https://github.com/perl6/specs/commit/60cf346f640a2ca50cd8712315f3b4df453fe48b Author: Anthony Parsons Date: 2015-12-31 (Thu, 31 Dec 2015)

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