Download as PDF, PPTX
![package My::Keyword;!
use Keyword::Simple;!
!
sub import { !
Keyword::Simple::define( !
class => sub { !
munge_code( $$_[0] );!
}!
);!
a real custom keyword](https://image.slidesharecdn.com/moops-141117003824-conversion-gate02/85/Make-Your-Own-Perl-with-Moops-38-320.jpg)
![package MyApp::Setup;!
use parent 'Moops';!
sub import { !
my $pkg = shift;!
my @imports = (!
'List::Util' => ['any'],!
'Scalar::Util' => ['blessed'],!
'experimental' => ['postderef']!
...!
);!
}
Moops-based setup class](https://image.slidesharecdn.com/moops-141117003824-conversion-gate02/85/Make-Your-Own-Perl-with-Moops-57-320.jpg)
Uploaded byMike Friedman
Make Your Own Perl with Moops
This document discusses the history of extensibility in Perl, from early techniques using import subroutines and prototypes, to modern approaches like Devel::Declare, the keyword API, and Moops. Moops provides an easy and extensible way to define new syntax using Keyword::Simple, and was created to improve on earlier modules like MooseX::Declare by using a simpler design focused on extensibility. The document concludes by showing how Moops can be used to define a custom "setup" module that injects imports and extends the syntax, providing a cleaner way to share commonly used functions and roles.
More Related Content
Similar to Make Your Own Perl with Moops
Make Your Own Perl with Moops
- 1. flickr: philip66 Make yourown Perl with M o o p s @friedo Mike Friedman London Perl Workshop 2014
- 2.
- 3. A brief history… Inthe Beginning, Perl 5 was already extensible.
- 4.
- 5. use Foo qw(bar); BEGIN{! require Foo;! Foo->import( ‘bar’ );! };
- 6.
- 7. sub import {! my$pkg = shift;! ... a typical import sub
- 8. sub import {! my$pkg = shift;! my $callpkg = caller;! ... a typical import sub
- 9. sub import {! my$pkg = shift;! my $callpkg = caller;! my @imports = @_;! ... a typical import sub
- 10. sub import {! ...! foreach ! my $sym(@imports) {! *{"${callpkg}::$sym"} = *{"${pkg}::$sym"} a typical import sub
- 11.
- 12. A brief history… importis compile-time.
- 13. A brief history… importis compile-time. 1. add functions. 2. pretend they’re keywords.
- 14. package Adder;! ! sub import{ ... }! sub add2 { ! return shift + 2;! } a pretend keyword
- 15. package Mine;! ! use Adder;! ! sayadd2 42; a pretend keyword
- 16. A brief history… Perl5.2 ! Prototypes
- 17. Make fake keywords ! Thatbehave like builtins
- 18.
- 19. sub doblock(&@) {! my $blk = shift;! return $blk->( @_ );! }! ! doblock { ! say $_ * $_ for @_;! } ( 1, 2, 3, 4, 5 );! a prototype pretend keyword
- 20. sub doblock(&) {... }! ! doblock { ! say "first";! }! ! say "second"; a prototype pretend keyword
- 21. sub doblock(&) {... }! ! doblock { ! say "first";! }! ! say "second"; a prototype pretend keyword # Fail :(
- 22. Prototype subs only workas expressions. ! Not statements.
- 23. sub doblock($&) {... }! ! doblock name { ! say "first";! }! ! a prototype pretend keyword # Fail :(
- 24. a prototype pretendkeyword # We have to say:
- 25. ! ! doblock name =>sub { ! say "first";! };! ! a prototype pretend keyword # We have to say:
- 26. "&" prototypes areonly magical if they're first.
- 27. A brief history… Perl5.8 ! Devel::Declare
- 28. The first realway to add ! new syntax.
- 29. use MooseX::Declare;! ! class Foo{ ! method bar { ... }! ...! }! ! a parser magic keyword
- 30.
- 31.
- 32.
- 33.
- 34.
- 35. MooseX::Declare is big, slow,and difficult to extend.
- 36. A brief history… Perl5.12 ! The keyword API
- 37. Real keyword interface inthe Perl core API.
- 38. package My::Keyword;! use Keyword::Simple;! ! subimport { ! Keyword::Simple::define( ! class => sub { ! munge_code( $$_[0] );! }! );! a real custom keyword
- 39. So... ! what is ! M oo p s ?
- 40. use Moops;! role NamedThing{! has name => ! (is => "ro", isa => Str);! }! ! class Person with NamedThing;! ... a Moops-defined class
- 41.
- 42.
- 43. Not exactly. •Moo bydefault, but can use Moose
- 44. Not exactly. •Moo bydefault, but can use Moose •Uses Keyword::Simple for new syntax.
- 45. Not exactly. •Moo bydefault, but can use Moose •Uses Keyword::Simple for new syntax. •Uses Kavorka for functions/methods
- 46. Not exactly. •Moo bydefault, but can use Moose •Uses Keyword::Simple for new syntax. •Uses Kavorka for functions/methods •Designed for easy extensibility
- 47. A brief history… Oneyear ago, ! I did this:
- 48.
- 49.
- 50. package MyApp::Setup;! use Import::Into;! ! useList::Util ();! use List::MoreUtils ();! use Scalar::Util ();! use Const::Fast ();! use Try::Tiny ();! use Data::Alias ();! use autodie ();! ... Custom setup class
- 51. ! ! sub import {! my $callpkg = caller;! Scalar::Util->import::into(! $callpkg, 'blessed', 'refaddr'! );! List::Util->import::into(! $callpkg, 'reduce', 'all', ...! );! ...! } Custom setup class
- 52.
- 53. Unless I wantto use custom syntax
- 54. use MooseX::Declare; ! #(or Moops)! ! class MyApp::Thing { ! use MyApp::Setup;! }! ! # :/! Custom setup class
- 55. I have touse the Setup class from within the right namespace.
- 56. What if theSetup class could also inject custom syntax?
- 57. package MyApp::Setup;! use parent'Moops';! sub import { ! my $pkg = shift;! my @imports = (! 'List::Util' => ['any'],! 'Scalar::Util' => ['blessed'],! 'experimental' => ['postderef']! ...! );! } Moops-based setup class
- 58. sub import {! ...! $pkg->SUPER::import(! imports=> @imports! );! }! ! ! # :D Moops-based setup class
- 59.
- 60. flickr: philip66 Questions @friedo Mike Friedman LondonPerl Workshop 2014