The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.
 / 
Acme-Tiny-0.6
River stage zero No dependents
++
/ Acme::Tiny

NAME

Acme::Tiny - As ::Tiny as a module can get

VERSION

This document describes Acme::Tiny version 0.6

SYNOPSIS

    use Acme::Tiny;

or for even less memory:

    require Acme::Tiny; # we saved about 24K, thats gold!!

DESCRIPTION

This module meets every rule of ::Tiny (see below) in fact it couldn't get any tinier (patches welcome if you've a tinier way, see 'Other solutions to the puzzle')

This module is stupid

Well... YEAH, its a play on concepts not an actual tool in the sense that you are a tool... It *is* Acme:: afterall...

What it might be useful for ...

Proof of concept?

Benchmarking or development testing of some sort?

Maybe a quick and easy to find reference of the criteria for the ::Tiny name space? (See '::Tiny')

I still think its stupid

Sorry, I'm afraid there's no hope for you then.

Why don't you spend time on useful stuff instead of this kind of junk?

Its fun and I needed a break. See 'I still think its stupid' above.

::Tiny

Writing a ::Tiny module

If there is a need for a ::Tiny version of a heavier module and it meets the criteria for the ::Tiny name space then go for it! I applaud your effort to make things efficient!

However, Please don't use ::Tiny unless it meets the ::Tiny criteria, thanks!

Also, I suggest documenting some specifics on why this legitimately belongs under ::Tiny.

For example, this module does so for itself under '10 Commandments of ::Tiny'.

Another example is File::Path::Tiny which has a "About the '::Tiny' status" section outlining bits of its tiny-ness.

A brief history of ::Tiny

Adam Kennedy started a revolution, or at least a good idea: the ::Tiny suffix.

While doing some 'tiny' jobs (for all the memory reduction possible) Adam was a great (patient) resource for feedback, (actual *useful* feedback on rt: awesome)

FYI, Adam if you want me to link to a more official ::Tiny resource or edit the rules, just let me know.

10 Commandments of ::Tiny

1. The module should be implemented in "as little code as possible"
2. The module should implement a useful subset of functionality
3. The module should use at least 1/10th the amount of memory overhead, ideally less than 100k
4. The module MUST have no non-core dependencies
5. The module MUST be only one single .pm file
6. The module should be back-compatible to at least 5.004
7. The module should omit functionality rather than implement it incorrectly.
8. If applicable, the module should be compatible with the larger module.

(Note: "there weren't ten": another joke! See rule #2 if you don't get it yet...)

Acme::Tiny is ::Tiny, a guide

1. The module should be implemented in "as little code as possible"

Technically we could ditch the $VERSION (and gain 8K +/-) but it'd be nice to be able to check the version (it has to do *something*)

2. The module should implement a useful subset of functionality

Acme doesn't really do anything so this expresses the most useful subset... pretty deep if you think about it.

3. The module should use at least 1/10th the amount of memory overhead, ideally less than 100k

Its only 52K if you require() it. (Acme is 1104K so its about 50% of 1/10th) Ways to get it down further are welcome!

4. The module MUST have no non-core dependencies

check

5. The module MUST be only one single .pm file

check

6. The module should be back-compatible to at least 5.004

check (so far anyway)

7. The module should omit functionality rather than implement it incorrectly.

check and double check

8. If applicable, the module should be compatible with the larger module.

Well you can still use it as a base class and use core isa stuff to see if you object isa one. Sounds like Mario.

Other solutions to the puzzle

no package() version

Sebastian Knapp asked me 'Why not $Acme::Tiny::VERSION=.4'.

Its a very good question actually. If we drop the package() and go with the full name space $VERSION it drops 4K and works the same (with VERSION var, VERSION method *and* 'isa' checking). I'd decided to go with package() though since it just felt right, somehow more proper in some mysterious way.

Thank you Sebatian for your email, excellent idea! I may switch to it in a future version but for now I'll hold on to the package().

absolute tiniest file

Another way is to have the .pm simply contain one character: 1

It would be loadable and cut off appx 16K. However you'd are unable to check its version or the package's state (isa() says 'Base class package "Acme::Tiny" is empty')

non decimal VERSION

VERSION=N is appx 4K smaller memory use than $VERSION=.N

Perhaps once I get a few more ideas like Sebastian's collected here and a URL fo Adam's offical ::Tiny page and any other useful information or items added we'll bump it to a whole number.

I just like the decimal though, so I may just end up keeping it...

INTERFACE

None really... well ok there is:

   $Acme::Tiny::VERSION
   
   Acme::Tiny->VERSION()

or the "subset" of the Acme functionality

   package my::thingy;
   use base 'Acme::Tiny';
   ...

meanwhile back at the script:

   use my::thingy;
   if (my::thingy->isa('Acme::Tiny')) {
       print "Yes please";
   }
   else {
       print "No thank you";
   }

DIAGNOSTICS

There's nothing to diagnose...

CONFIGURATION AND ENVIRONMENT

Acme::Tiny requires no configuration files or environment variables.

DEPENDENCIES

None.

INCOMPATIBILITIES

Its not compatible with up-tight people.

BUGS AND LIMITATIONS

No bugs have been reported.

Please report any bugs or feature requests to bug-acme-tiny@rt.cpan.org, or through the web interface at http://rt.cpan.org.

AUTHOR

Daniel Muey <http://drmuey.com/cpan_contact.pl>

LICENCE AND COPYRIGHT

Copyright (c) 2008, Daniel Muey <http://drmuey.com/cpan_contact.pl>. All rights reserved.

This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See perlartistic.

DISCLAIMER OF WARRANTY

BECAUSE THIS SOFTWARE IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENCE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.