From aa403b978860210fcbace7fcdf5830066f3e14e0 Mon Sep 17 00:00:00 2001 From: Jesse Luehrs Date: Sat, 13 Oct 2018 02:17:44 -0400 Subject: import site content --- .../talks/extending_moose_yapc_na_2010/index.html | 97 ++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 static/talks/extending_moose_yapc_na_2010/index.html (limited to 'static/talks/extending_moose_yapc_na_2010/index.html') diff --git a/static/talks/extending_moose_yapc_na_2010/index.html b/static/talks/extending_moose_yapc_na_2010/index.html new file mode 100644 index 0000000..c894505 --- /dev/null +++ b/static/talks/extending_moose_yapc_na_2010/index.html @@ -0,0 +1,97 @@ + + +Extending Moose + + + + + +

Use SPACEBAR to peruse the slides or click one to start...

+

Extending Moose

Extending Moose
motivation
moose
using only the basic features doesn't gain you much
package Foo;
package Foo;
but...
moose gives you more than this
but the real power of moose is in extensibility
typical object systems are defined in terms of, well, object systems
code should be written with the intent of communicating with *humans*
this has different levels:
perl:
moose (by default):
but what we'd really like is:
moose can give us this too
the mop
models classes as objects
every class is represented by a metaclass
Moose::Meta::Class
access these objects through Class->meta (a class method installed by "use Moose")
class information is stored and manipulated through these objects
also provides informational methods
and provides other functionality specific to the mop
Moose::Meta::Attribute
accessed through $meta->get_attribute, etc
informational methods:
accessing data handled by the attribute
Moose::Meta::Method
accessed through $meta->get_method, etc
so how does this all work?
metacircularity
metaclasses are instances of the class Moose::Meta::Class
this is accomplished by two tricks
compiler bootstrapping
Moose::Meta::Class has a metaclass, but it's also a Moose::Meta::Class
but this is mostly irrelevant
the idea to take away is that moose is built on top of moose
so we have this foundation, but how can we make this easy to use?
Moose::Exporter
we have __PACKAGE__->meta->add_attribute(foo => (is => 'ro'))
Moose::Exporter is a wrapper around Sub::Exporter providing moose-specific functionality
Moose itself uses Moose::Exporter
so the key here is that all of these metaclasses can be customized, and Moose::Exporter can wrap those customizations to make them pretty
basic extensions don't even need to alter the metaclass
package FileAttributes;
package Foo;
but altering metaclasses can provide more powerful abstractions
package AtomicMethod::Role::Method;
and make it pretty
package Foo;
combining metaclass alterations can be even more powerful
package Command::Role::Method;
package Command::Role::Class;
package Command;
package Foo;
package My::App;
for larger projects, providing a custom exporter can simplify things greatly
package Mooose;
the positive side
these things are easily packaged up into standalone modules
any questions?

This presentation was generated by Vroom. Use <SPACE> key to go +forward and <BACKSPACE> to go backwards. +

+ -- cgit v1.2.3-54-g00ecf