aboutsummaryrefslogtreecommitdiffstats
path: root/x11-servers/x2vnc
diff options
context:
space:
mode:
authorsunpoet <sunpoet@FreeBSD.org>2012-03-31 09:15:00 +0800
committersunpoet <sunpoet@FreeBSD.org>2012-03-31 09:15:00 +0800
commit11d4851837a87b47ee5335a5807e463a1fd1a093 (patch)
tree59295df90e0df45dff9f7692906777991dfd036b /x11-servers/x2vnc
parent0eacc8d7b42752f6189039d87d83fc1fc629dacf (diff)
downloadfreebsd-ports-gnome-11d4851837a87b47ee5335a5807e463a1fd1a093.tar.gz
freebsd-ports-gnome-11d4851837a87b47ee5335a5807e463a1fd1a093.tar.zst
freebsd-ports-gnome-11d4851837a87b47ee5335a5807e463a1fd1a093.zip
- Add p5-Role-Tiny 1.000000
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. - 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. WWW: http://search.cpan.org/dist/Role-Tiny/ Feature safe: yes
Diffstat (limited to 'x11-servers/x2vnc')
0 files changed, 0 insertions, 0 deletions