I would like to point out that regexes in Perl6 are treated as code.
(They can even have parameters and lexical variables.)
It uses the same compiler intrinsics as the rest of Perl6.
It uses the same VM opcodes as regular Perl6 code.
Regexes, string literals, and signatures are just domain
> use v6;
> 'abcd' ~~ / . <.before( /c/ )> . / # "bc"
> 'abcd' ~~ / . <.before c > . / # "bc" # (exactly identical)
>
> A person could change the code in the `before` method to have it do
> something different
At least at the moment, that's not 100% accurate (only by virtue
On 13/08/2019 16:32, Brad Gilbert wrote:
> Perhaps the biggest one may be the one about passing around “fates”.
> (I barely understand the basics of this.)
The optimization opportunity Brad is refering to here is relevant mostly
to grammars with deeply nested multi-tokens:
FWIW, at one time there was discussion that "" and ""
are actually keywords and not typical method calls that can be overridden,
precisely so optimizations can be made. They're that important to
efficient running of the regexes.
I'm not sure that a formal decision was ever made on this,
Here's some stuff that anybody who wants to work on regex optimization
in perl6 will want to know:
You can get a print-out of rakudo's internal AST that is generated for
the regex by passing --target=ast or --target=optimize to the perl6
commandline. I recommend grep -C5 Regex to skip some of the
I've put up two name suggestions for Perl 6:
NUPERL:
www.nuperl.orgwww.nuperl.comwww.nuperl.net
NEUPERL:
www.neuperl.orgwww.neuperl.comwww.neuperl.net
Specifics:
https://github.com/perl6/problem-solving/issues/81#issuecomment-520960546
I'm not sure why this decision has to be
I don't think the decision has been made so far. At this point, it is a
proposal by one (or possibly several) individual(s) whom I very much
respect.
And it is definitely not going to hapopen this week (and quite probably not
this month).
Even though my opinion on the subject is probably
Hi,
on 2019/8/14 5:19, Laurent Rosenfeld via perl6-users wrote:
Having said that, I should add that if the name should really change, I
think Camelia is probably the least bad idea that I can think of.
Following the link:
This is Rakudo version 2019.07.1 built on MoarVM version 2019.07.1 implementing
Perl 6.d.
Is there a type “name” size limit in Perl 6/Rakudo/Moar?
I’ve been making a hierarchy of classes to take in a > 4MB XML file, and I
found it organized & convenient to use the names of the elements for
On 8/11/19 11:14 PM, Eliza wrote:
Hello perl6 world,
I saw the perl6 github issue, just was confused will perl6 change its name?
https://github.com/perl6/problem-solving/issues/81
I don't know whether to take this is troll bait or a real issue. Lots
of people seem to be responding; so
I'm cheating here - I'm using an e-mail message as a way to publish some notes
for Jonathan (or *anyone else interested*):
Jonathan did a talk in Riga, Perl 6 performance update,
https://perlcon.eu/talk/80
The (re-uploaded) live stream is at
https://www.youtube.com/watch?v=S5iVBlk7pdg#t=4h39m
It's been said before, but I do think that the "Perl6" name is holding back
adoption. Too many people think of the old Perl, and have no interest in
looking at what's changed in a new version of the "same" language.
Whatever the new name ultimately becomes, changing it (perhaps timed with a
new
12 matches
Mail list logo
