Mooch a regex

Hi All, Would yo all terribly mind if I ask how to do this Perl 5 regex in Perl 6? (I learn best by example.) if ( $ClickLine =~ /aes256/ and /${BaseTag}/ ) { push ( @WebClickHere, $ClickLine ); if ( $Line =~ m{select id=\"(.*?)[-]} ) { my

Re: perl 6 for rhel?

Red Hat is quite conservative. Usually what happens in situations like this when you want more up to date stuff you get it from alternate repositories that make Red Hat compatible packages. See also repositories for Fedora or Cent OS. -- Darren Duncan On 2016-01-10 11:16 PM, ToddAndMargo

[perl #127243] DESTROY is not called on interpreter exit

# New Ticket Created by Dave Rolsky # Please include the string: [perl #127243] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127243 > Here's an example which might demonstrate why this is important: class C { has

Re: Mooch a regex

hi, what's in ${BaseTag}? Is it a regex rule or just a plain string? (Because that matters in Perl 6) Am 12.01.2016 um 01:55 schrieb ToddAndMargo: Hi All, Would yo all terribly mind if I ask how to do this Perl 5 regex in Perl 6? (I learn best by example.) if ( $ClickLine =~ /aes256/ and

Re: [perl #127238] Undefined loop variable inside sub [BUG]

> On 11 Jan 2016, at 17:30, Iskander Sharipov (via RT) > wrote: > > # New Ticket Created by Iskander Sharipov > # Please include the string: [perl #127238] > # in the subject line of all future correspondence about this issue. > #

[perl #127236] Attribute.package is wrong for attributes declared inside roles

# New Ticket Created by Lloyd Fournier # Please include the string: [perl #127236] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127236 > role Foo { has $.foo; }; Foo.^attributes[0].package.^name.say #->$?CLASS

[perl #127235] Function "one" may not be called without arguments

# New Ticket Created by Manuel Cerón # Please include the string: [perl #127235] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127235 > The following error seems to be a bug: $ perl6 -e 'sub one { 1 }; say one;'

[perl #127224] Itemized slip has invalid .perl stringification

# New Ticket Created by Lucas Buchala # Please include the string: [perl #127224] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127224 > The ".perl"-stringification of an itemized slip has a strange dollar sign in the

[perl #127222] Itemized empty list has wrong .perl stringification

# New Ticket Created by Lucas Buchala # Please include the string: [perl #127222] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127222 > An itemized empty list is getting ".perl"-stringified as "$()", which I think is wrong

[perl #127223] Error when smartmatching an empty signature

# New Ticket Created by Lucas Buchala # Please include the string: [perl #127223] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127223 > > :() ~~ :(Int) Cannot call 'shift' on an immutable 'List' in block at - line 1 >

[perl #127227] `<{...}>` in regex leaks memory

# New Ticket Created by Siavash # Please include the string: [perl #127227] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127227 > I experienced this problem in this code: $_ = "abcdefgh"; say ++$_ until

Re: order of input using Capture

You're passing `a` as a named arg, and `e` as a positional arg. .list only returns the positional args, and .elems only counts those. You can use .hash to get the named args. Alternatively, if you replace `a=>1` with `(a=>1)` or `'a'=>1`, it should show up in the .list and .elems counts. See:

Re: order of input using Capture

Sorry, that first sentence was imprecise: `a` is a named arg, as compared to the pair `(e=>2)`, which is a positional arg by virtue of the parens. On Mon, Jan 11, 2016 at 5:01 PM Philip Hazelden wrote: > You're passing `a` as a named arg, and `e` as a positional arg.

Re: [perl #127236] Attribute.package is wrong for attributes declared inside roles

Since timtimo++ saw this ticket and tried to ping me on IRC I'm going to explain why I wanted this to work. See: https://github.com/LLFourn/p6-AttrX-InitArg/ And in particular this commit. https://github.com/LLFourn/p6-AttrX-InitArg/commit/ffd5e962020d85595b2c2edd08f390044899 I was using

Re: [perl #127236] Attribute.package is wrong for attributes declared inside roles

To add to the confusion: role Foo { method meth { } }; class Bar does Foo { }; Bar.^find_method("meth").package.say (Foo) so methods behave as I expect but attributes don't. On Tue, Jan 12, 2016 at 2:00 AM Lloyd Fournier wrote: > Since timtimo++ saw this ticket and

order of input using Capture

L.s. I've seen that the order of input to a Capture is not kept. Is this a bug? REPL interaction; > my Capture $c = \(a=>1,10,{w=>2},[2,3],(e=>2),(b=>3,),Buf.new(^3)) \(10, {:w(2)}, [2, 3], :e(2), (:b(3),), Buf.new(0, 1, 2), :a(1)) > for $c.list -> $item { $item.WHAT.say;} (Int) (Hash)

[perl #127236] Attribute.package is wrong for attributes declared inside roles

On Mon Jan 11 05:46:19 2016, lloyd.fo...@gmail.com wrote: > role Foo { has $.foo; }; Foo.^attributes[0].package.^name.say #->$?CLASS Just to note that this behavior is intentional rather than accidental (or at least, *I* intended it :-)). Roles undergo generic instantiation at the point of

[perl #127238] Undefined loop variable inside sub [BUG]

# New Ticket Created by Iskander Sharipov # Please include the string: [perl #127238] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127238 > VERSION: $ perl6 --version This is Rakudo version 2015.12-44-g477830a built on

Re: order of input using Capture

On 01/11/2016 06:58 PM, mt1957 wrote: Thanks for the information I didn't know about this detail. What about the order of input, when a call is made and a Capture created the order is preserved otherwise the arguments would be bound to the wrong values isn't it? But the example shows

[perl #127167] .^add_method does not work for Role anymore

On Tue Jan 05 03:20:59 2016, moritz wrote: > On Tue Jan 05 02:54:22 2016, gfldex wrote: > > role R {}; R.^add_method('foo', method (){}) > > > > # OUTPUT«Method 'add_method' not found for invocant of class > > 'Perl6::Metamodel::ParametricRoleGroupHOW'␤ in block at > > /tmp/ORnhrivIvq line 1␤» >

panda and documentation

L.s. I have written my documentation in separate pod files. How do I mention this in the META.info file and where will panda install the documentation Greetings Marcel

[perl #127237] missing encoded trait for Str attributes (CStruct, NativeCall)

# New Ticket Created by Felix Bytow # Please include the string: [perl #127237] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127237 > The following should apply the same marshalling as passing a Str to a native function.

Re: order of input using Capture

Thanks for the information I didn't know about this detail. What about the order of input, when a call is made and a Capture created the order is preserved otherwise the arguments would be bound to the wrong values isn't it? But the example shows otherwise.

[perl #127241] [BUG] $*BASETIME is not defined

# New Ticket Created by Zoffix Znet # Please include the string: [perl #127241] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127241 > The Perl 5's variable $^T contains the time when the program was started. Attempting to

Re: [perl #127167] .^add_method does not work for Role anymore

You are both wrong :P perl6 -e 'my $R = my role R {}; $R.^add_method("foo",method {}) #works!' I'm guessing that puns it. Though it's still useful. On Tue, Jan 12, 2016 at 5:32 AM jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > On Tue Jan 05 03:20:59 2016, moritz wrote: > > On

Re: [perl #127241] [BUG] $*BASETIME is not defined

> On 11 Jan 2016, at 18:57, Zoffix Znet (via RT) > wrote: > > # New Ticket Created by Zoffix Znet > # Please include the string: [perl #127241] > # in the subject line of all future correspondence about this issue. > #

[perl #127242] [LTA ERROR] No space between a class traight and {

# New Ticket Created by Zoffix Znet # Please include the string: [perl #127242] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127242 > This produces a confusing error: m: class Foo is Int{} rakudo-moar 42a583: