This document gives you some suggestions about how to go about writingPerl modules, preparing them for distribution, and making them availablevia CPAN.

One of the things that makes Perl really powerful is the fact that Perlhackers tend to want to share the solutions to problems they've faced,so you and I don't have to battle with the same problem again.

The main way they do this is by abstracting the solution into a Perlmodule. If you don't know what one of these is, the rest of thisdocument isn't going to be much use to you. You're also missing out onan awful lot of useful code; consider having a look at perlmod,perlmodlib and perlmodinstall before coming back here.

When you've found that there isn't a module available for what you'retrying to do, and you've had to write the code yourself, considerpackaging up the solution into a module and uploading it to CPAN so thatothers can benefit.

Warning

We're going to primarily concentrate on Perl-only modules here, ratherthan XS modules. XS modules serve a rather different purpose, andyou should consider different things before distributing them - thepopularity of the library you are gluing, the portability to otheroperating systems, and so on. However, the notes on preparing the Perlside of the module and packaging and distributing it will apply equallywell to an XS module as a pure-Perl one.

What should I make into a module?

You should make a module out of any code that you think is going to beuseful to others. Anything that's likely to fill a hole in the communallibrary and which someone else can slot directly into their program. Anypart of your code which you can isolate and extract and plug intosomething else is a likely candidate.

Let's take an example. Suppose you're reading in data from a localformat into a hash-of-hashes in Perl, turning that into a tree, walkingthe tree and then piping each node to an Acme Transmogrifier Server.

Now, quite a few people have the Acme Transmogrifier, and you've had towrite something to talk the protocol from scratch - you'd almostcertainly want to make that into a module. The level at which you pitchit is up to you: you might want protocol-level modules analogous toNet::SMTP which then talk to higher level modules analogousto Mail::Send. The choice is yours, but you do want to geta module out for that server protocol.

Nobody else on the planet is going to talk your local data format, so wecan ignore that. But what about the thing in the middle? Building treestructures from Perl variables and then traversing them is a nice,general problem, and if nobody's already written a module that doesthat, you might want to modularise that code too.

So hopefully you've now got a few ideas about what's good to modularise.Let's now see how it's done.

Step-by-step: Preparing the ground

Before we even start scraping out the code, there are a few things we'llwant to do in advance.

Look around
Dig into a bunch of modules to see how they're written. I'd suggeststarting with Text::Tabs, since it's in the standardlibrary and is nice and simple, and then looking at something a littlemore complex like File::Copy. For object orientedcode, WWW::Mechanize or the Email::* modules provide some goodexamples.
These should give you an overall feel for how modules are laid out andwritten.
Check it's new
There are a lot of modules on CPAN, and it's easy to miss one that'ssimilar to what you're planning on contributing. Have a good ploughthrough the http://search.cpan.org and make sure you're not the onereinventing the wheel!
Discuss the need
You might love it. You might feel that everyone else needs it. But theremight not actually be any real demand for it out there. If you're unsureabout the demand your module will have, consider sending out feelerson the comp.lang.perl.modules newsgroup, or as a last resort, ask themodules list at modules@perl.org. Remember that this is a closed listwith a very long turn-around time - be prepared to wait a good while fora response from them.
Choose a name
Perl modules included on CPAN have a naming hierarchy you should try tofit in with. See perlmodlib for more details on how this works, andbrowse around CPAN and the modules list to get a feel of it. At the veryleast, remember this: modules should be title capitalised, (This::Thing)fit in with a category, and explain their purpose succinctly.
Check again
While you're doing that, make really sure you haven't missed a modulesimilar to the one you're about to write.
When you've got your name sorted out and you're sure that your module iswanted and not currently available, it's time to start coding.

Step-by-step: Making the module

Start with module-starter or h2xs
The module-starter utility is distributed as part of theModule::Starter CPAN package. It creates a directorywith stubs of all the necessary files to start a new module, accordingto recent "best practice" for module development, and is invoked fromthe command line, thus:
```
 module-starter --module=Foo::Bar \
    --author="Your Name" [email protected]
 
```
If you do not wish to install the Module::Starterpackage from CPAN, h2xs is an older tool, originally intended for thedevelopment of XS modules, which comes packaged with the Perldistribution.
A typical invocation of h2xs for a pure Perl module is:
```
 h2xs -AX --skip-exporter --use-new-tests -n Foo::Bar
 
```
The -A omits the Autoloader code, -X omits XS elements,--skip-exporter omits the Exporter code, --use-new-tests sets up amodern testing environment, and -n specifies the name of the module.
Use strict and warnings
A module's code has to be warning and strict-clean, since you can'tguarantee the conditions that it'll be used under. Besides, you wouldn'twant to distribute code that wasn't warning or strict-clean anyway,right?
Use Carp
The Carp module allows you to present your error messages fromthe caller's perspective; this gives you a way to signal a problem withthe caller and not your module. For instance, if you say this:
```
 warn "No hostname given";
 
```
the user will see something like this:
```
 No hostname given at /usr/local/lib/perl5/site_perl/5.6.0/Net/Acme.pm
  line 123.
 
```
which looks like your module is doing something wrong. Instead, you wantto put the blame on the user, and say this:
```
 No hostname given at bad_code, line 10.
 
```
You do this by using Carp and replacing your warns withcarps. If you need to die, say croak instead. However, keepwarn and die in place for your sanity checks - where it really isyour module at fault.
Use Exporter - wisely!
Exporter gives you a standard way of exporting symbols andsubroutines from your module into the caller's namespace. For instance,saying use Net::Acme qw(&frob) would import the frob subroutine.
The package variable @EXPORT will determine which symbols will getexported when the caller simply says use Net::Acme - you will hardlyever want to put anything in there. @EXPORT_OK, on the other hand,specifies which symbols you're willing to export. If you do want toexport a bunch of symbols, use the %EXPORT_TAGS and define a standardexport set - look at Exporter for more details.
Use plain old documentation
The work isn't over until the paperwork is done, and you're going toneed to put in some time writing some documentation for your module.module-starter or h2xs will provide a stub for you to fill in; ifyou're not sure about the format, look at perlpod for anintroduction. Provide a good synopsis of how your module is used incode, a description, and then notes on the syntax and function of theindividual subroutines or methods. Use Perl comments for developer notesand POD for end-user notes.
Write tests
You're encouraged to create self-tests for your module to ensure it'sworking as intended on the myriad platforms Perl supports; if you uploadyour module to CPAN, a host of testers will build your module and sendyou the results of the tests. Again, module-starter and h2xsprovide a test framework which you can extend - you should do somethingmore than just checking your module will compile.Test::Simple and Test::More are goodplaces to start when writing a test suite.
Write the README
If you're uploading to CPAN, the automated gremlins will extract theREADME file and place that in your CPAN directory. It'll also appear inthe main by-module and by-category directories if you make it ontothe modules list. It's a good idea to put here what the module actuallydoes in detail, and the user-visible changes since the last release.

Step-by-step: Distributing your module

Get a CPAN user ID
Every developer publishing modules on CPAN needs a CPAN ID. Visithttp://pause.perl.org/, select "Request PAUSE Account", and wait foryour request to be approved by the PAUSE administrators.
perl Makefile.PL; make test; make dist
Once again, module-starter or h2xs has done all the work for you.They produce the standard Makefile.PL you see when you download andinstall modules, and this produces a Makefile with a dist target.
Once you've ensured that your module passes its own tests - always agood thing to make sure - you can make dist, and the Makefile willhopefully produce you a nice tarball of your module, ready for upload.
Upload the tarball
The email you got when you received your CPAN ID will tell you how tolog in to PAUSE, the Perl Authors Upload SErver. From the menus there,you can upload your module to CPAN.
Announce to the modules list
Once uploaded, it'll sit unnoticed in your author directory. If you wantit connected to the rest of the CPAN, you'll need to go to "RegisterNamespace" on PAUSE. Once registered, your module will appear in theby-module and by-category listings on CPAN.
Announce to clpa
If you have a burning desire to tell the world about your release, postan announcement to the moderated comp.lang.perl.announce newsgroup.
Fix bugs!
Once you start accumulating users, they'll send you bug reports. Ifyou're lucky, they'll even send you patches. Welcome to the joys ofmaintaining a software project...

AUTHOR

Simon Cozens, simon@cpan.org

Updated by Kirrily "Skud" Robert, skud@cpan.org

Preparing a new module for distribution

Daftar Isi

NAME