SecBSD's official ports repository

devel/p5-Class-Method-Modifiers/Makefile

@@ -0,0 +1,15 @@
+COMMENT =	provides Moose-like method modifiers
+
+MODULES =	cpan
+PKG_ARCH =	*
+DISTNAME =	Class-Method-Modifiers-2.15
+CATEGORIES =	devel
+FIX_EXTRACT_PERMISSIONS =	Yes
+
+# Perl
+PERMIT_PACKAGE =	Yes
+
+TEST_DEPENDS =	devel/p5-Test-Requires \
+		devel/p5-Moose
+
+.include <bsd.port.mk>

devel/p5-Class-Method-Modifiers/distinfo

@@ -0,0 +1,2 @@
+SHA256 (Class-Method-Modifiers-2.15.tar.gz) = Zc2Fv+R10GbpGG96jMY2BwmFswsOuxzehoHPBiwuFfw=
+SIZE (Class-Method-Modifiers-2.15.tar.gz) = 41167

devel/p5-Class-Method-Modifiers/pkg/DESCR

@@ -0,0 +1,18 @@
+Method modifiers are a powerful feature from the CLOS (Common Lisp
+Object System) world. In its most basic form, a method modifier is just
+a method that calls $self->SUPER::foo(@_).
+
+Class::Method::Modifiers provides three modifiers: before, around, and
+after. "before" and "after" are run just before and after the method they
+modify, but can not really affect that original method. "around" is run in
+place of the original method, with a hook to easily call that original
+method.
+
+One clear benefit of using Class::Method::Modifiers is that you can
+define multiple modifiers in a single namespace. These separate modifiers
+don't need to know about each other. This makes top-down design easy.
+Have a base class that provides the skeleton methods of each operation,
+and have plugins modify those methods to flesh out the specifics.
+
+In short, Class::Method::Modifiers solves the problem of making sure you
+call $self->SUPER::foo(@_), and provides a cleaner interface for it.

devel/p5-Class-Method-Modifiers/pkg/PLIST

@@ -0,0 +1,4 @@
+${P5SITE}/Class/
+${P5SITE}/Class/Method/
+${P5SITE}/Class/Method/Modifiers.pm
+@man man/man3p/Class::Method::Modifiers.3p