From 6bb2b24d721b1950e38dca0dc814fde424f24143 Mon Sep 17 00:00:00 2001 From: jasper Date: Sat, 5 Apr 2014 07:53:03 +0000 Subject: [PATCH] tweak long DESCR --- devel/p5-Role-Tiny/pkg/DESCR | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/devel/p5-Role-Tiny/pkg/DESCR b/devel/p5-Role-Tiny/pkg/DESCR index bb04660ea4f..056854c1a5b 100644 --- a/devel/p5-Role-Tiny/pkg/DESCR +++ b/devel/p5-Role-Tiny/pkg/DESCR @@ -1,12 +1,6 @@ Role composition can be thought of as much more clever and meaningful multiple inheritance. The basics of this implementation of roles is: - If a method is already defined on a class, that method will not be -composed in from the role. + composed in from the role. - If a method that the role "requires" to be implemented is not -implemented, role application will fail loudly. - -Unlike Class::C3, where the last class inherited from "wins," role -composition is the other way around, where first wins. In a more -complete system (see Moose) roles are checked to see if they clash. The -goal of this is to be much simpler, hence disallowing composition of -multiple roles at once. + implemented, role application will fail loudly.