develooper Front page | perl.perl5.porters | Postings from October 2021

Re: review of perlexperiment, 2021-10

Thread Previous | Thread Next
From:
Dan Book
Date:
October 3, 2021 22:13
Subject:
Re: review of perlexperiment, 2021-10
Message ID:
CABMkAVWF8r=MiFT+pRXo1apf9LkXXjLU9HV2gMGA533-Wz-D_A@mail.gmail.com
On Sun, Oct 3, 2021 at 5:50 PM Paul "LeoNerd" Evans <leonerd@leonerd.org.uk>
wrote:

> > *pluggable keyword API* — Calling this experimental is also weird.
> > We have had a number of PSC (and other) conversations about changing
> > how pluggable keywords work so that their implementation could be
> > less exposed, and certain hooks could be made experimental so they'd
> > warn when being hooked into.  *I would love to see an email about
> > this from Nicholas or Paul.*  #13199
> > <https://github.com/Perl/perl5/issues/13199>
>
> In summary: I'd love to basically say that PL_keyword_plugin and all
> the associated machinery, including *all* of the lexer and parser API,
> are no longer for public use, and they are simply the internal
> mechanism used to make XS::Parse::Keyword work, and that
> XS::Parse::Keyword will now be the "public" API used by XS authors to
> provide extension keywords.
>
> Already I've rewritten all of mine on CPAN to use it, and honestly I'm
> not really aware of any other "production-grade" syntax modules on CPAN
> not written by me. There's a few bits and pieces out there, but to my
> knowledge nothing large or with much following.
>

Off the top of my head, some decently used ones are: Function::Parameters,
Switch::Plain (which is rather trivial), Kavorka (which uses the deprecated
Parse::Keyword), Moops (which uses various problematic keyword modules),
and less-used: Zydeco, Quote::Code, Dios

-Dan

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About