Debian Codegraph @

debian/control

raw
1 Source: libclass-spiffy-perl
2 Section: perl
3 Priority: optional
4 Build-Depends: debhelper-compat (= 13), libmodule-install-perl
5 Build-Depends-Indep: perl
6 Maintainer: Debian Perl Group <[email protected]>
7 Uploaders: Damyan Ivanov <[email protected]>
8 Standards-Version: 4.7.2
9 Homepage: https://metacpan.org/release/Class-Spiffy
10 Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libclass-spiffy-perl.git
11 Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libclass-spiffy-perl
12 Testsuite: autopkgtest-pkg-perl
13
14 Package: libclass-spiffy-perl
15 Architecture: all
16 Depends: ${misc:Depends}, ${perl:Depends}
17 Description: Spiffy Perl interface framework
18 Class::Spiffy is a framework and methodology for doing object oriented
19 programming in Perl. Class::Spiffy combines the best parts of Exporter.pm,
20 base.pm, mixin.pm and SUPER.pm into one magic foundation class. It attempts to
21 fix all the nits and warts of traditional Perl OO, in a clean, straightforward
22 and (perhaps someday) standard way.
23 .
24 Class::Spiffy borrows ideas from other OO languages like Python, Ruby, Java
25 and Perl 6. It also adds a few tricks of its own.
26 .
27 If you take a look on CPAN, there are a ton of OO related modules. When
28 starting a new project, you need to pick the set of modules that makes most
29 sense, and then you need to use those modules in each of your classes.
30 Class::Spiffy, on the other hand, has everything you'll probably need in one
31 module, and you only need to use it once in one of your classes. If you make
32 Class::Spiffy the base class of the basest class in your project,
33 Class::Spiffy will automatically pass all of its magic to all of your
34 subclasses. You may eventually forget that you're even using it!
35 .
36 The most striking difference between Class::Spiffy and other Perl object
37 oriented base classes, is that it has the ability to export things. If you
38 create a subclass of Class::Spiffy, all the things that Class::Spiffy exports
39 will automatically be exported by your subclass, in addition to any more
40 things that you want to export. And if someone creates a subclass of your
41 subclass, all of those things will be exported automatically, and so on. Think
42 of it as "Inherited Exportation", and it uses the familiar Exporter.pm
43 specification syntax.