We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrated from rt.perl.org#54796 (status was 'resolved')
Searchable as RT54796$
The text was updated successfully, but these errors were encountered:
The following run shows how the fact that a list of captured positionals barfs on an .elems call:
$ parrot perl6.pbc > rule Foo { (\d+) } > "1234 x" ~~ Foo; say $/; 1234 > "1234 x" ~~ Foo; say @($/); 1234 > "1234 x" ~~ Foo; say @($/).WHAT; List > "1234 x" ~~ Foo; say @($/).elems; Method 'elems' not found for invocant of class 'ResizablePMCArray' > # wtf?! > say [1,2,3,4].elems 4 > say <1 2 3 4>.elems 4 $
// Carl
Sorry, something went wrong.
On Sun, May 25, 2008 at 09:37:18AM -0700, Carl Mäsak wrote:
The following run shows how the fact that a list of captured positionals barfs on an .elems call: $ parrot perl6\.pbc > rule Foo \{ \(\\d\+\) \} > "1234 x" ~~ Foo; say $/; 1234 > "1234 x" ~~ Foo; say @​\($/\); 1234 > "1234 x" ~~ Foo; say @​\($/\)\.WHAT; List > "1234 x" ~~ Foo; say @​\($/\)\.elems; Method 'elems' not found for invocant of class 'ResizablePMCArray' > \# wtf?\!
$ parrot perl6\.pbc > rule Foo \{ \(\\d\+\) \} > "1234 x" ~~ Foo; say $/; 1234 > "1234 x" ~~ Foo; say @​\($/\); 1234 > "1234 x" ~~ Foo; say @​\($/\)\.WHAT; List > "1234 x" ~~ Foo; say @​\($/\)\.elems; Method 'elems' not found for invocant of class 'ResizablePMCArray' > \# wtf?\!
Now fixed in r27818:
$ ./parrot perl6.pbc > rule Foo { (\d+) } > "1234 x" ~~ Foo; say @($/).elems; 1 >
Pm
The RT System itself - Status changed from 'new' to 'open'
@pmichaud - Status changed from 'open' to 'resolved'
No branches or pull requests
Migrated from rt.perl.org#54796 (status was 'resolved')
Searchable as RT54796$
The text was updated successfully, but these errors were encountered: