Re: Is there sn ETA for the next Rakudo* ?

ople will wait for that. So I would guess the next release of Rakudo* won't be for another 2 weeks or so.

Is there sn ETA for the next Rakudo* ?

I'm setting up a new machine, and I don't want to install something I'm going to have to update in a week.

[perl #132885] .next-handle seems to change handles but doesn't

On Mon, 19 Feb 2018 19:48:30 -0800, c...@zoffix.com wrote: > On Mon, 19 Feb 2018 16:15:37 -0800, comdog wrote: > > #!/Users/brian/bin/perl6s/perl6-latest > > > > I'm playing with .next-handle from IO::CatHandle. I'm > > trying to create a situation where I c

[perl #132885] .next-handle seems to change handles but doesn't

On Mon, 19 Feb 2018 19:48:30 -0800, c...@zoffix.com wrote: > On Mon, 19 Feb 2018 16:15:37 -0800, comdog wrote: > > #!/Users/brian/bin/perl6s/perl6-latest > > > > I'm playing with .next-handle from IO::CatHandle. I'm > > trying to create a situation where I c

[perl #132885] .next-handle seems to change handles but doesn't

On Mon, 19 Feb 2018 16:15:37 -0800, comdog wrote: > #!/Users/brian/bin/perl6s/perl6-latest > > I'm playing with .next-handle from IO::CatHandle. I'm > trying to create a situation where I can read just the first five > lines from each command line argument: > >

[perl #132885] .next-handle seems to change handles but doesn't

On Mon, 19 Feb 2018 16:15:37 -0800, comdog wrote: > #!/Users/brian/bin/perl6s/perl6-latest > > I'm playing with .next-handle from IO::CatHandle. I'm > trying to create a situation where I can read just the first five > lines from each command line argument: > >

Re: [perl #132885] AutoReply: .next-handle seems to change handles but doesn't

$lines = 1 } } if $lines > $limit { $*ARGFILES.next-handle.close; last unless $*ARGFILES.opened; next; } put "{$*ARGFILES.path}:{$lines++} $_"; } }

Re: [perl #132885] AutoReply: .next-handle seems to change handles but doesn't

$lines = 1 } } if $lines > $limit { $*ARGFILES.next-handle.close; last unless $*ARGFILES.opened; next; } put "{$*ARGFILES.path}:{$lines++} $_"; } }

[perl #132885] .next-handle seems to change handles but doesn't

# New Ticket Created by "brian d foy" # Please include the string: [perl #132885] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132885 > #!/Users/brian/bin/perl6s/perl6-latest I'm playing with .n

Re: how do I match the next two characters?

On Fri, Jan 19, 2018 at 12:29 AM, Todd Chester > wrote: On 01/18/2018 05:17 PM, mimosinnet wrote: The '?' is not necessary Indeed! I use `.*?` when I do not want the wild card to be "greedy" When I have a choice of using either, I a

Re: how do I match the next two characters?

On 01/18/2018 05:17 PM, mimosinnet wrote: The '?' is not necessary Indeed! I use `.*?` when I do not want the wild card to be "greedy" When I have a choice of using either, I always use `.*?` so I remember the difference and as a kind of comment that tells me not to be greedy. Thank you!

Re: how do I match the next two characters?

>The '?' is not necessary ;-) perl6 -e 'my $x="abcsdd1efg1234xyz"; $x ~~ m/(sd..).*(12..)/; say "$0, $1"' sdd1, 1234 The "?" is to modify the "*" to be "non-greedy" - that is, it will match the first chunk of stuff that is followed by whatever is after it (so, "/*?/" the "?" is certainly unne

Re: how do I match the next two characters?

Thanks for this thread El Tuesday, 16 de January del 2018 a les 19:28, Todd Chester va escriure: But I do have to use `.*?` in the middle when matching two things $ perl6 -e 'my $x="abcsdd1efg1234xyz"; $x ~~ m/(sd..).*?(12..)/; say "$0, $1"' sdd1, 1234 The '?' is not necessary ;-) perl6 -

Re: how do I match the next two characters?

On 01/16/2018 12:57 AM, Elizabeth Mattijsen wrote: On 16 Jan 2018, at 09:46, ToddAndMargo wrote: I want to match the next two character (don't care what they are) in the following I will use ?? for the next two character, but that doesn't work $x ~~ m/.*?(sd??).*/; I want $0

Re: how do I match the next two characters?

On 01/16/2018 12:57 AM, Elizabeth Mattijsen wrote: On 16 Jan 2018, at 09:46, ToddAndMargo wrote: I want to match the next two character (don't care what they are) in the following I will use ?? for the next two character, but that doesn't work $x ~~ m/.*?(sd??).*/; I want $0 to i

Re: how do I match the next two characters?

> On 16 Jan 2018, at 09:46, ToddAndMargo wrote: > I want to match the next two character (don't care what > they are) in the following > > I will use ?? for the next two character, but that doesn't work > $x ~~ m/.*?(sd??).*/; > > I want $0 to include th

how do I match the next two characters?

Hi All, I want to match the next two character (don't care what they are) in the following I will use ?? for the next two character, but that doesn't work $x ~~ m/.*?(sd??).*/; I want $0 to include the "sd" and the next two characters, whatever they are. Many thanks, -T

[perl #132076] next/last controls loop from exception stack instead of lexical loop

# New Ticket Created by Vovan-VE # Please include the string: [perl #132076] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132076 > Hello. I'm using rakudo release 2017.07. I'm sure I hit a bug. I could not find something sim

[perl #132034] Presence of NEXT phasers interferes with labeled `next`

r 1 { next FOO } 13:17 camelia rakudo-moar 4b02b8: ( no output ) 13:17 Zoffix m: FOO: for 1 { NEXT {}; next FOO } 13:17 camelia rakudo-moar 4b02b8: OUTPUT: «labeled next without loop construct? in block at line 1??»

Re: next

On Mon, Jun 19, 2017 at 11:35 AM, Brad Gilbert wrote: > Instead of a `continue` block after the loop, there is a `NEXT` phaser > inside the block > ah, thanks (though the term "phaser" (outside of "set on stun", of course) is new) and that can be block too: https:/

Re: next

On Mon, Jun 19, 2017 at 11:15 AM, Andy Bach wrote: > > On Fri, Jun 16, 2017 at 11:11 PM, Gabor Szabo wrote: >> >> If the loop has some action and a condition it will jump to execute >> the action again (increment $i) and check the condition and act >> according

Re: next

On Fri, Jun 16, 2017 at 11:11 PM, Gabor Szabo wrote: > If the loop has some action and a condition it will jump to execute > the action again (increment $i) and check the condition and act > accordingly doing the next iteration or quitting the loop. > Just checking but there are

Re: next

On Sun, Jun 18, 2017 at 11:41 PM, ToddAndMargo > wrote: On 06/17/2017 12:22 AM, yary wrote: last if ++$true_count == 6; Hi Yary, ++$true_count Is that the same as `$true_count + 1` ? And does it alter the value of $true_count? -

Re: next

On Mon, Jun 19, 2017 at 12:41 AM, ToddAndMargo wrote: > On 06/17/2017 12:22 AM, yary wrote: > >> last if ++$true_count == 6; >> > > ++$true_count > > Is that the same as `$true_count + 1` ? > > And does it alter the value of $true_count > Yes and yes, just like in C and Perl 5; note that being p

Re: next

In this instance, it is the same as "$true_count = $true_count + 1". ++$var and $var++ differ if they are used in an assignment or other operation. For instance: my $x = 1; my $y = ++$x; # $x is incremented before assignment my $z = $x++; # $x is incremented after assignment At the end, $x = 3

Re: next

On 06/17/2017 12:22 AM, yary wrote: last if ++$true_count == 6; Hi Yary, ++$true_count Is that the same as `$true_count + 1` ? And does it alter the value of $true_count? -T

Re: next

On 06/16/2017 09:11 PM, Gabor Szabo wrote: I probably would not say "restart" the loop. It goes to the*next* iteration of the loop: I used "restart" because I wanted myself to think it went back to the top, ignoring everything else in the {} and proceeded to the next item

Re: next

On Fri, Jun 16, 2017 at 11:11 PM, Gabor Szabo wrote: > I probably would not say "restart" the loop. > > There is a statement for that, "redo" restarts the loop without updating the value. my $true_count = 0; loop (my $i = 1; $i < 10; $i++) { last if ++$true_count == 6; say "\$true_count==$true

Re: next

On Sat, Jun 17, 2017 at 4:19 AM, ToddAndMargo wrote: > On 06/16/2017 06:08 PM, Brandon Allbery wrote: >> >> On Fri, Jun 16, 2017 at 9:02 PM, ToddAndMargo > <mailto:toddandma...@zoho.com>> wrote: >> >> I am afraid I am not understanding "next"

Re: next

On 06/16/2017 06:08 PM, Brandon Allbery wrote: On Fri, Jun 16, 2017 at 9:02 PM, ToddAndMargo <mailto:toddandma...@zoho.com>> wrote: I am afraid I am not understanding "next" again. When you invoke it, does it pop you back at the start of the loop or just coug

Re: next

On Fri, Jun 16, 2017 at 9:02 PM, ToddAndMargo wrote: > I am afraid I am not understanding "next" again. > > When you invoke it, does it pop you back at the start of > the loop or just cough up the next value? > The former. Or you can think of it as jumping past everyth

next

Hi All, I am afraid I am not understanding "next" again. When you invoke it, does it pop you back at the start of the loop or just cough up the next value? Many thanks, -T -- ~~~ Serious error. All shortcuts have disappeared. Screen. Mind. Both are blank. ~~~

[perl #131567] [REGRESSION] `do LABEL: for 1 { next LABEL }` doesn't see the label since 2016.07 commit

On Tue, 13 Jun 2017 07:26:15 -0700, c...@zoffix.com wrote: > m: do LABEL: for 1 { next LABEL } > rakudo-moar 4aa60a: OUTPUT: «labeled next without loop construct␤ in > block at line 1␤␤» > > Bisectable points to > https://github.com/rakudo/rakudo/commit/5581b24111589683dcd503

[perl #131567] [REGRESSION] `do LABEL: for 1 { next LABEL }` doesn't see the label since 2016.07 commit

On Tue, 13 Jun 2017 07:26:15 -0700, c...@zoffix.com wrote: > m: do LABEL: for 1 { next LABEL } > rakudo-moar 4aa60a: OUTPUT: «labeled next without loop construct␤ in > block at line 1␤␤» > > Bisectable points to > https://github.com/rakudo/rakudo/commit/5581b24111589683dcd503

[perl #131567] [REGRESSION] `do LABEL: for 1 { next LABEL }` doesn't see the label since 2016.07 commit

# New Ticket Created by Zoffix Znet # Please include the string: [perl #131567] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131567 > m: do LABEL: for 1 { next LABEL } rakudo-moar 4aa60a: OUTPUT: «labeled n

Re: need help with "next"

On 05/24/2017 01:04 AM, Richard Hainsworth wrote: see https://docs.perl6.org/language/regexes#Subrules Fascinating and way over my head. Give me a year or two to catch up.

Re: need help with "next"

gt; ; > > SAMPLE > > for @Data { > next unless m/ 'NAME' .*? '>' $=( .*? ) '<' /; > say $; # say implicitly stringifies $ > } > > > Hi Richard. The idea is that the names can not be extracted unless they are embedded ins

Re: need help with "next"

On 05/23/2017 10:31 PM, Richard Hainsworth wrote: > The code below seems unnecessarily complex. > > How about: > > my @Data = q:to/SAMPLE/; > > Mission D', > Sol Wheat, > Ted Moon, > ; > > SAMPLE &g

Re: need help with "next"

On 05/24/2017 12:02 AM, Norman Gaywood wrote: On 24 May 2017 at 16:40, Norman Gaywood > wrote: However, your code does not look like it will do what you want if you have multiple TASKs Yes it does. Sorry ignore me :-) Oh it had issues. They showe

Re: need help with "next"

On 05/23/2017 11:40 PM, Norman Gaywood wrote: I'm a rank beginner p6 programmer so You are further along than me!

Re: need help with "next"

On 05/23/2017 11:40 PM, Norman Gaywood wrote: However, your code does not look like it will do what you want if you have multiple TASKs I improved it. See my other follow post #3

Re: need help with "next"

Oh, you know what, I thought it might be a good idea to throw some negative case data into the mix. This is what I came up with: #!/usr/bin/env perl6 use strict; my @Data = 'Mission A', ' Peter Meter', ' John Deer', ' Sam Horse', '',

Re: need help with "next"

On 24 May 2017 at 16:40, Norman Gaywood wrote: > > However, your code does not look like it will do what you want if you have >> multiple TASKs >> > > Yes it does. Sorry ignore me :-) -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidal

Re: need help with "next"

On 24 May 2017 at 15:20, ToddAndMargo wrote: > > > This is what I came up with. I found that `next` did not serve me > well, so i just used a tag. > > Thank you all for the help. I had a bit of a time wrapping > my head around `next` there for a while. > > -T > >

Re: need help with "next"

On Wednesday, May 24, 2017 01:20 PM, ToddAndMargo wrote: On 05/23/2017 09:30 PM, ToddAndMargo wrote: Hi All, I have a test code in progress and I haven't figured out how to get 'next' to work the way I want. next if $Line.contains( "TASK type" ); works, bu

Re: need help with "next"

The code below seems unnecessarily complex. How about: my @Data = q:to/SAMPLE/; Mission D', Sol Wheat, Ted Moon, ; SAMPLE for @Data { next unless m/ 'NAME' .*? '>' $=( .*? ) '<' /; say $; # say implicitly stringifies $

Re: need help with "next"

On 05/23/2017 09:30 PM, ToddAndMargo wrote: Hi All, I have a test code in progress and I haven't figured out how to get 'next' to work the way I want. next if $Line.contains( "TASK type" ); works, but if $Line.contains( "TASK type" ) {

Re: need help with "next"

Any data fulfilling the 'if' condition, and thus entering this block will be 'next'ed. Nothing will pass the 'next'. But no data not fulfilling the condition will 'see' the code below, which is not what you intend. Perhaps you omitted an 'else

Re: need help with "next"

On Wednesday, May 24, 2017 12:46 PM, ToddAndMargo wrote: On Tue, May 23, 2017 at 11:30 PM, ToddAndMargo wrote: Hi All, I have a test code in progress and I haven't figured out how to get 'next' to work the way I want. next if $Line.contains( "TASK type"

Re: need help with "next"

On Tue, May 23, 2017 at 11:30 PM, ToddAndMargo wrote: Hi All, I have a test code in progress and I haven't figured out how to get 'next' to work the way I want. next if $Line.contains( "TASK type" ); works, but if $Line.contains( "TASK type" )

Re: need help with "next"

You do realize that `next` immediately stops the current iteration and goes onto the *next* one right? That is, there is no point putting any code after it because it will never be run. On Tue, May 23, 2017 at 11:30 PM, ToddAndMargo wrote: > Hi All, > > I have a test code in progr

need help with "next"

Hi All, I have a test code in progress and I haven't figured out how to get 'next' to work the way I want. next if $Line.contains( "TASK type" ); works, but if $Line.contains( "TASK type" ) { next; does not. What am I missing? Many than

[perl #131281] next on last iteration of loop injects Mu into return value and fouls termination test

On Tue, 09 May 2017 11:17:23 -0700, b...@abrij.org wrote: > > There are some misbehaviors when a next clause is encountered on what > would be the last iteration of a loop construct. An extra Mu is > injected into the return value for that iteration, and the termination > test

[perl #131281] next on last iteration of loop injects Mu into return value and fouls termination test

# New Ticket Created by "Brian S. Julin" # Please include the string: [perl #131281] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131281 > There are some misbehaviors when a next clause is encountered on what

[perl #131060] .grep does not fire FIRST / LAST / NEXT phasers

# New Ticket Created by Elizabeth Mattijsen # Please include the string: [perl #131060] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131060 > $ 6 'dd .grep: { FIRST say "first"; LAST say "last";

[perl #130601] [REGRESSION] “next” inside whenever no longer works (react { whenever foo() { next if $_ > 3 } })

ver foo() { next if $_ > 3; say $_; }; }; Result (2015.12): 1 2 3 Result (2016.08.1): 1 2 3 Access denied to keep/break this Promise; already vowed in any at /tmp/whateverable/rakudo-moar/a07a2e173cfc24f1bec549d2d5b79ef978e46b58/share/perl6/runtime/CORE.setting.moarvm line 1 Result (HEAD

Re: [perl #121722] for 42 {NEXT (state $val) = $_} # fails on MOAR

This test now passes, can be closed. > On 17 Oct 2014, at 23:57, Christian Bartolomaeus via RT > wrote: > > Hmm, it looks like that was not all -- or there is a new problem. > > $ perl6-m -e 'for 42 {NEXT (state $val) = $_}; say "alive"' > alive &g

[perl #128003] [LTA ERROR] forgetting "token" next to a rule with a dot in it gives confusing error

# New Ticket Created by Zoffix Znet # Please include the string: [perl #128003] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128003 > Not sure if there's any way to improve this, but I've spent some time on this error, look

[perl #123731] [BUG] `last` inside a `NEXT` phaser in a loop does not abort the loop

On Wed Feb 04 17:58:57 2015, masak wrote: > m: for ^5 { .say; NEXT { last } } > rakudo-moar 613c0b: OUTPUT«0␤1␤2␤3␤4␤» > bug? > * masak submits rakudobug for `last` in a `NEXT` not exiting the for loop > m: my $c = 3; while $c { say $c--; NEXT { last } }; > rakudo-moar 61

[perl #123732] [BUG] `return` in a NEXT phaser in a loop outside of any routine aborts the iteration in Rakudo

On Wed Feb 04 18:18:09 2015, masak wrote: > m: for ^5 { .say; NEXT { return } } > rakudo-moar 613c0b: OUTPUT«0␤1␤2␤3␤4␤» > that last one, besides wrongly compiling (IMO), did not have > the wrong runtime semantics I expected it to. > m: say "A"; return; say "B&qu

[perl #124952] Roast rakudo skip/todo test:./S04-phasers/next.t line:105 reason: 'NEXT/LEAVE ordering'

There are failing tests (fudged 'todo') in S04-phasers/in-loop.t and S04-phasers/next.t, because LEAVE is called before NEXT. S04 states that it should be the other way around: "NEXT {...} at loop continuation time, before any LEAVE" (http://design.perl6.org/S04.html#Phasers).

[perl #124255] SEGV with rakudo.moar when executing 'next; CONTROL { }'

The segfault with MoarVM is fixed. The new error message seems LTA, though. $ perl6-m -e 'next; CONTROL { }' flatten requires a concrete string, but got null in regex at ././CORE.setting.moarvm:1 in block at -e:1

[perl #124255] SEGV with rakudo.moar when executing 'next; CONTROL { }'

, I stumbled upon a segfault with rakudo.moar. The golfed version is: $ perl6-m -e 'next; CONTROL { }' Segmentation fault I tried to generate a gdb backtrace: $ cat control.p6 next; CONTROL {}; $ gdb --args /home/christian/my_files/computer/Perl6/tmp/rakudo_work_1/install/bin/moar -

[perl #123894] [BUG] `NEXT` phaser doesn't fire from inside an `ENTER` phaser in a loop in Rakudo

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #123894] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=123894 > m: for 1..2 { ENTER { my $t = (^1000).roll; say "Setting up $t";

[perl #123732] [BUG] `return` in a NEXT phaser in a loop outside of any routine aborts the iteration in Rakudo

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #123732] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=123732 > m: for ^5 { .say; NEXT { return } } rakudo-moar 613c0b: OUTPUT«0␤1␤2␤3␤4

[perl #123731] [BUG] `last` inside a `NEXT` phaser in a loop does not abort the loop

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #123731] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=123731 > m: for ^5 { .say; NEXT { last } } rakudo-moar 613c0b: OUTPUT«0␤1␤2␤3␤4␤»

[perl #113950] [BUG] 'next' or 'last' don't trigger LEAVE phaser in loop in Rakudo

As noted in April 'next' triggers LEAVE phaser as expected. With 'last' there is no longer an error, but the LEAVE phaser is still not triggered (same output on Moar, Parrot and JVM): $ perl6 -e 'loop { last; LEAVE say "bye!" }; say "outside"'

Re: The next 100 Years

Hi Sayth, On 17.11.2014 12:51, Sayth Renshaw wrote: As a person new and looking at Perl 6 as I have done over the time I am interested to know from Perl 6 Language advocates what exactly the strength and benefit of Perl 6 is and will likely be? * Perl 6's built-in grammars make parsing really

The next 100 Years

As a person new and looking at Perl 6 as I have done over the time I am interested to know from Perl 6 Language advocates what exactly the strength and benefit of Perl 6 is and will likely be? Is there a particular domain it is going to be especially useful for ? Is it going to be able to design

[perl #121722] for 42 {NEXT (state $val) = $_} # fails on MOAR

Hmm, it looks like that was not all -- or there is a new problem. $ perl6-m -e 'for 42 {NEXT (state $val) = $_}; say "alive"' alive This does not fail any longer. But the tests in integration/advent2012-day15.t don't pass. I'd say the following command shows mor

[perl #117957] free(): invalid next size (fast) in S02-types/bool.t

I just completed a git bisect on nom for this issue. 5838e933b362d33c8a0854a7c410c347a4911bde is the first bad commit $ git show 5838e933b362d33c8a0854a7c410c347a4911bde commit 5838e933b362d33c8a0854a7c410c347a4911bde Merge: 4741028 02c7fbb Author: Moritz Lenz Date: Sat May 4 21:09:08 2013 +020

[perl #113950] [BUG] 'next' or 'last' don't trigger LEAVE phaser in loop in Rakudo

On Mon Jul 02 07:02:11 2012, masak wrote: > r: loop { last; LEAVE say "bye!" }; say "outside" > rakudo 16db64: OUTPUT«outside␤» > do we have this one on file? > closest I find is > https://rt.perl.org/rt3/Ticket/Display.html?id=113548 > * masak submits rak

[perl #115998] [BUG] LEAVE phaser doesn't trigger on 'next' in Rakudo

On Sat Mar 16 10:03:56 2013, jn...@jnthn.net wrote: > On Wed Dec 05 02:44:42 2012, masak wrote: > > nr: for 1..10 { LEAVE { say "x" }; next } > > niecza v24-5-g599cbcb: OUTPUT«x␤x␤x␤x␤x␤x␤x␤x␤x␤x␤» > > ..rakudo e2f2dc: ( no output ) > > * masak submits r

[perl #115998] [BUG] LEAVE phaser doesn't trigger on 'next' in Rakudo

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #115998] # in the subject line of all future correspondence about this issue. # https://rt.perl.org:443/rt3/Ticket/Display.html?id=115998 > nr: for 1..10 { LEAVE { say "x" }; next } niecza v24-5

[perl #113950] [BUG] 'next' or 'last' don't trigger LEAVE phaser in loop in Rakudo

side" rakudo 16db64: OUTPUT«outside␤» do we have this one on file? closest I find is https://rt.perl.org/rt3/Ticket/Display.html?id=113548 * masak submits rakudobug r: for ^10 { next; LEAVE say "yay!" }; say "outside" rakudo 16db64: OUTPUT«outside␤» that, too. n: loop {

Re: Estimate for next Rakudo Star release?

Hi, On 04/28/2011 12:48 AM, Brian Wisti wrote: > Is it close? Any pressing issues? Did I miss an announcement? Very close: http://rakudoperl.org/2011/04/28/rakudo-star-2011-04-released/ (rakudo.org will soon also point to the new location). Cheers, Moritz

Re: Estimate for next Rakudo Star release?

Hi, On Wed, Apr 27, 2011 at 7:36 PM, Bruce Gray wrote: > > [ snippage of useful information ] > Thanks for the update! I wanted to make sure I hadn't missed anything. Kind Regards, Brian Wisti http://coolnamehere.com

Re: Estimate for next Rakudo Star release?

On Apr 27, 2011, at 5:48 PM, Brian Wisti wrote: --snip-- Is it close? Yes; I was looking for it today. There may be a short additional delay :) Any pressing issues? Not really; just "last minute" adjustments and additions that are expected when a release has not been cut for 3 months. Fo

Estimate for next Rakudo Star release?

Hey all, By my admittedly limited math, it's been almost three months since Rakudo Star 2011.01 was released. The announcement at mentioned the shift was to a three month schedule. So ... Is it close? Any pressing issues? Did I miss an announcemen

Re: S26 - The Next Generation

Jon Lang asked: > Not actually S26; but closely related: should $=POD and .WHY be > read-only? I had assumed so. > Also, should there be other Pod variables besides $=POD? > If so, which ones? The original idea was that every Pod block with any kind of TYPENAME would be available as $=TYPENAME

Re: S26 - The Next Generation

Not actually S26; but closely related: should $=POD and .WHY be read-only? Also, should there be other Pod variables besides $=POD? If so, which ones? Back on the subject of S26: should declarator blocks and aliases be able to introspect the object with which they're associated? That is, should

Re: S26 - The Next Generation

yary asked: > Can some concept/implementation of $=POD lazyness only incur the > memory and performance hit on access? IANAImplementor, but I suspect that virtually all of the performance hit could be incurred at run-time, if it happened to be implemented that way. The memory hit too, if necessar

Re: S26 - The Next Generation

On Thu, 2009-09-17 at 11:12 -0700, yary wrote: > On Thu, Sep 17, 2009 at 1:05 AM, Damian Conway wrote: > > Aaron Sherman asked: > ... > >> I'd very much like to establish that at default optimization levels for > >> execution, this information is not guaranteed to be maintained past the > >> creat

Re: S26 - The Next Generation

On Thu, Sep 17, 2009 at 1:05 AM, Damian Conway wrote: > Aaron Sherman asked: ... >> I'd very much like to establish that at default optimization levels for >> execution, this information is not guaranteed to be maintained past the >> creation of the AST. > > Unfortunately, it is. Perl 6 defines th

Re: S26 - The Next Generation

Aaron Sherman asked: > Should there be an explicit way to step this down to just parsing the bits > that are called out as pod? The original conception allowed for Pod to be independent of the interleaved language. That has now been supplanted by a model that views Pod as an integral part of Perl

Re: S26 - The Next Generation

the bits that are called out as pod? For example: #!/bin/sh #=notperl :leading<#> :trailing<\n> cd $1 #=head1 ... # ... #=cut Obviously causing leading #s to be stripped when evaluating the podishness of a section of the program, up to the next newline. Similarly a CDATA

Re: S26 - The Next Generation

Jon Lang elaborated: > I don't think that there will be a problem.  First, #=> is easy enough > to distinguish from #=; I don't foresee any confusion. I'm not so sure. #=> is a lot more like #= that =alias is. And the one character of difference is on the non-significant (right-hand) side. Need t

Re: S26 - The Next Generation

Jon Lang huh'd: > Huh.  Would you be able to do something like: > >    =begin pod >    Welcome to $?FILE. > > ...and have it interpolate the file's name?  Or would you need some > special markup for this, such as: > >    =begin pod >    Welcome to A<$?FILE>. The latter. Variables are just too com

Re: S26 - The Next Generation

Jon Lang wrote: An unrelated possibility would be to allow empty A<> tags in a declarator block, with 'A<>' being replaced with the name of the declarator to which the block is attached: And then I think: A<_> -- Ruud (indoctrinated)

Re: S26 - The Next Generation

f the line available for other uses (such as declarator blocks): class Database::Handle { #=> has IO $!handle; #=> my Bool method open ($filename) {...} #=>[m1] #= Here's a block for A. my Bool method close () {...} #=>m2 And given that brief names are going to be preferred, this could result in very compact, yet still readable, combinations of declarator aliases and blocks. >> An unrelated possibility would be to allow empty A<> tags in a >> declarator block, with 'A<>' being replaced with the name of the >> declarator to which the block is attached: > > These are both very useful ideas. > I'll ponder them carefully in preparation for the next revision. > > Thanks, Jon! No; thank you. -- Jonathan "Dataweaver" Lang

Re: S26 - The Next Generation

Damian Conway wrote: > Raiph elucidated: >> I was thinking it would be possible to reference (compiler) variables >> representing eg. the name and sig of a block being parsed, or a block >> or declaration which has just been parsed, or which is just about to be >> parsed, and that simply referencin

Re: S26 - The Next Generation

bility would be to allow empty A<> tags in a > declarator block, with 'A<>' being replaced with the name of the > declarator to which the block is attached: These are both very useful ideas. I'll ponder them carefully in preparation for the next revision. Thanks, Jon! Damian

Re: S26 - The Next Generation

Raiph elucidated: > Hmm. I was thinking Pod would be parsed by a P6/PGE grammar, one that > could be relatively easily edited/extended to suit another context, because, > I thought, it could then be made available as a stock --doc subsystem that > all PCT based languages get more or less for free.

Re: S26 - The Next Generation

Damian: > While I'm all in favour of other languages using Pod as a documentation > format, > I think that's unlikely. Pod says that anything of the form: > >                       =identfiier > > *anywhere* as the first non-whitespace of a line, is considered a Pod > directive. > I can't see man

Re: S26 - The Next Generation

I promised some further thoughts; here they are: As written, declarator aliasing attaches the alias to a piece of code, and draws both the name and the alias from that.  What about using a special case of the declarator block for this?  That is:    class Database::Handle { #=alias        has IO $

Re: S26 - The Next Generation

Smylers pointed out: >>    * Hence it must always parsed using full Perl 6 grammar: perl6 -doc > > Having a multi-character option preceded by a single hyphen doesn't play > well with bundling of single-character options... You make many good points. Changed to: perl --doc Thanks, Damian

Re: S26 - The Next Generation

you need to add some braces around it. > But those braces are unlikely to harm the program. > > The exception is if you want to quote an 'unbalanced' portion of code, > for example the start of a loop but not the entire loop.  Do you > consider that to be likely? Actually, yes

Re: S26 - The Next Generation

t to quote an 'unbalanced' portion of code, for example the start of a loop but not the entire loop. Do you consider that to be likely? > how about saying that an ambient code alias is normally > terminated by the next blank line or Pod directive (as per =for) Braces are more robu

Re: S26 - The Next Generation

Damian Conway writes: > It's Sunday evening and, as promised, here's the new draft of S26. Wow, thanks for that -- it's most impressive and I'm already excited about what it will allow and how it permits improved documentation. >* Hence it must always parsed using full Perl 6 grammar: perl6

Re: S26 - The Next Generation

e been redundant with '=alias' (although I don't think that redundancy hurts). And again, the Pod coder would be able to think in the same terms that he does for ordinary blocks. But assuming for the moment that the "pseudo-block" idea is off the table, how about saying that

  1   2   3   4   >