-
Notifications
You must be signed in to change notification settings - Fork 0
/
00modlist.long.html
3418 lines (3285 loc) · 508 KB
/
00modlist.long.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><!-- -*- coding: utf-8 -*- --><head><title>The Perl 5 Module List</title><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body>
<h1>The Perl 5 Module List</h1>
Maintained by Tim Bunce and Andreas König <a href="mailto:[email protected]"><[email protected]></a>;<br />
<i> $Revision: 3.112 $ $Date: 2002/08/27 23:28:18 $ -*- coding:utf-8 -*-</i><br />
<h3>Contents</h3>
<a href="#Introduction"> Introduction</a><br />
<a href="#WhereAreTheModu"> Where Are The Modules Kept?</a><br />
<a href="#PlayingYourPart"> Playing Your Part</a><br />
<a href="#HowToGetaMoreRe"> How To Get a More Recent Copy of the List</a><br />
<a href="#EditorialInform"> Editorial Information and Copyright</a><br />
<p> </p><h4><a href="#Part1-Modules:C">Part 1 - Modules: Creation, Use and Abuse</a></h4>
<a href="#ID1_Perl5Module">1) Perl 5 Module Terminology</a><br />
<a href="#ID2_Guidelinesf">2) Guidelines for Module Creation</a><br />
<a href="#ID3_Guidelinesf">3) Guidelines for Converting Perl 4 Library Scripts into Modules</a><br />
<a href="#ID4_Guidelinesf">4) Guidelines for Reusing Application Code</a><br />
<a href="#ID5_NamespaceCo">5) Namespace Coordination</a><br />
<h4><a href="#Part2-ThePerl5M">Part 2 - The Perl 5 Module List</a></h4>
<a href="#ID1_ModuleListi">1) Module Listing Format</a><br />
<a href="#ID2_PerlCoreMod">2) Perl Core Modules, Perl Language Extensions and Documentation Tools</a><br />
<a href="#ID3_Development">3) Development Support</a><br />
<a href="#ID4_OperatingSy">4) Operating System Interfaces, Hardware Drivers</a><br />
<a href="#ID5_Networking_">5) Networking, Device Control (modems) and InterProcess Communication</a><br />
<a href="#ID6_DataTypesan">6) Data Types and Data Type Utilities</a><br />
<a href="#ID7_DatabaseInt">7) Database Interfaces</a><br />
<a href="#ID8_UserInterfa">8) User Interfaces</a><br />
<a href="#ID9_Interfacest">9) Interfaces to or Emulations of Other Programming Languages</a><br />
<a href="#ID10_FileNames_">10) File Names, File Systems and File Locking (see also File Handles)</a><br />
<a href="#ID11_StringProc">11) String Processing, Language Text Processing, Parsing and Searching</a><br />
<a href="#ID12_Option_Arg">12) Option, Argument, Parameter and Configuration File Processing</a><br />
<a href="#ID13_Internatio">13) Internationalization and Locale</a><br />
<a href="#ID14_Authentica">14) Authentication, Security and Encryption</a><br />
<a href="#ID15_WorldWideW">15) World Wide Web, HTML, HTTP, CGI, MIME</a><br />
<a href="#ID16_ServerandD">16) Server and Daemon Utilities</a><br />
<a href="#ID17_Archiving_">17) Archiving, Compression and Conversion</a><br />
<a href="#ID18_Images_Pix">18) Images, Pixmap and Bitmap Manipulation, Drawing and Graphing</a><br />
<a href="#ID19_MailandUse">19) Mail and Usenet News</a><br />
<a href="#ID20_ControlFlo">20) Control Flow Utilities (callbacks and exceptions etc)</a><br />
<a href="#ID21_FileHandle">21) File Handle, Directory Handle and Input/Output Stream Utilities</a><br />
<a href="#ID22_MicrosoftW">22) Microsoft Windows Modules</a><br />
<a href="#ID23_Miscellane">23) Miscellaneous Modules</a><br />
<a href="#ID24_InterfaceM">24) Interface Modules to Commercial Software</a><br />
<a href="#ID25_Bundles">25) Bundles</a><br />
<h4><a href="#Part3-Standards">Part 3 - Standards Cross-reference</a></h4>
<a href="#ID3.1_IETF-Inte">3.1) IETF - Internet Engineering Task Force (RFCs)</a><br />
<a href="#ID3.2_ITU-Inter">3.2) ITU - International Telegraph Union (X.*)</a><br />
<a href="#ID3.3_ISO-Inter">3.3) ISO - International Standards Organization (ISO*)</a><br />
<h4><a href="#Part4-Who_sWhoa">Part 4 - Who's Who and What's Where</a></h4>
<a href="#ID4.1_Informati">4.1) Information / Contact Reference Details</a><br />
<a href="#ID4.2_PerlFrequ">4.2) Perl Frequently Asked Questions (FAQ) Files</a><br />
<p> </p>
<hr /><h4><a id="Introduction" name="Introduction">Introduction</a></h4>
This document is a semi-formal list of Perl 5 Modules. The Perl 4
concept of packages has been extended in Perl 5 and a new standardised
form of reusable software component has been defined: the Module.
<p> </p>
Perl 5 Modules typically conform to certain guidelines which make them
easier to use, reuse, integrate and extend.
<p> </p>
<h4>This list has two key aims:</h4>
<ul><li> FOR DEVELOPERS: To change duplication of effort into cooperation.</li><li> FOR USERS: To quickly locate existing software which can be reused.</li></ul>
<p> </p>
This list includes the Perl 5 standard modules, other completed
modules, work-in-progress modules and would-be-nice-to-have ideas for
modules. It also includes guidelines for those wishing to create new
modules including how to name them.
<p> </p>
<h4><a id="WhereAreTheModu" name="WhereAreTheModu">Where Are The Modules Kept?</a></h4>
Most, but not all, of the modules can be found within CPAN, the
Comprehensive Perl Archive Network of mirrored FTP sites. Within the
CPAN scheme the modules described in this list can be found in the
modules/ directory below the CPAN root directory. CPAN is a worlswide
network of mirrors and you can find your closest mirror in the file
<a href="http://www.cpan.org/SITES.html">http://www.cpan.org/SITES.html</a>
<p> </p>
NOTE: If you can't find what you want, or wish to check that what
you've found is the latest version, or wonder why a module mentioned in
this list is not on CPAN, you should contact the person associated with
the module (and not the maintainers of the archives or this list).
Contact details are given at the start of Part 4.
<p> </p>
<h4><a id="PlayingYourPart" name="PlayingYourPart">Playing Your Part</a></h4>
Perl is a huge collaborative effort. Everyone who uses perl is
benefiting from the contributions of many hundreds, maybe thousands, of
people. How much time has perl saved you since you started using it?
<p> </p>
Do you have any modules you could share with others? For example, you
may have some perl4 scripts from which generally useful, and reusable,
modules could be extracted. There may be many people who would find
your work very useful. Please play your part and contribute to the Perl
community where you can. [ end of sermon :-]
<p> </p>
Help save the world! Please submit new entries and updates to us so we
can keep this list up-to-date. Send the new or corrected entry by
email to
<a href="mailto:[email protected]">[email protected]</a>
. Please do not send code to this address.
Instead upload your module, once registered, to the PAUSE site for
forwarding on to CPAN. See section 2, especially 2.6 and 2.11.
<p> </p>
<h4><a id="HowToGetaMoreRe" name="HowToGetaMoreRe">How To Get a More Recent Copy of the List</a></h4>
This Module List is fed into CPAN on a semi-regular basis. Its
relative path within a CPAN mirror is in modules/00modlist.long.html .
<p> </p>
<h4><a id="EditorialInform" name="EditorialInform">Editorial Information and Copyright</a></h4>
This document is Copyright (c) 1997-2000 by Tim Bunce and Andreas
König. All rights reserved. Permission to distribute this document, in
full or part, via electronic means (emailed, posted or archived) or
printed copy is granted providing that no charges are involved,
reasonable attempt is made to use the most current version, and all
credits and copyright notices are retained. Requests for other
distribution rights, including incorporation in commercial products,
such as books, magazine articles, or CD-ROMs should be made to
<a href="mailto:[email protected]">[email protected]</a>
and
<a href="mailto:[email protected]">[email protected]</a>
.
<p> </p>
Disclaimer: The content of this document is simply a collection of
information gathered from many sources with little or no checking.
There are NO warranties with regard to this information or its use.
<p> </p>
A little background information... I (Tim) created the Module List in
August 1994 and maintained it manually till April 1996. By that time
Andreas had implemented the Perl Authors Upload Server (PAUSE) and it
was happily feeding modules through to the CPAN archive sites (see
<a href="http://www.cpan.org/modules/04pause.html">http://www.cpan.org/modules/04pause.html</a>
for details). Since PAUSE
held a database of module information which could be maintained by
module authors it made sense for the module listing part of the Module
List to be built from that database. In April 1996 Andreas took over
the automatic posting of the Module List and I now maintain the other
parts of the text. We plan to add value to the automation over time.
<p> </p>
<p> </p>
<h2><a id="Part1-Modules:C" name="Part1-Modules:C">Part 1 - Modules: Creation, Use and Abuse</a></h2>
<h3><a id="ID1_Perl5Module" name="ID1_Perl5Module">1) Perl 5 Module Terminology</a></h3>
Perl 5 implements a class using a package, but the presence of a
package doesn't imply the presence of a class. A package is just a
namespace. A class is a package that provides subroutines that can be
used as methods. A method is just a subroutine that expects, as its
first argument, either the name of a package (for "static" methods), or
a reference to something (for "virtual" methods).
<p> </p>
A module is a file that (by convention) provides a class of the same
name (sans the .pm), plus an import method in that class that can be
called to fetch exported symbols. This module may implement some of its
methods by loading dynamic C or C++ objects, but that should be totally
transparent to the user of the module. Likewise, the module might set
up an AUTOLOAD function to slurp in subroutine definitions on demand,
but this is also transparent. Only the .pm file is required to exist.
<p> </p>
<h3><a id="ID2_Guidelinesf" name="ID2_Guidelinesf">2) Guidelines for Module Creation</a></h3>
<h4>2.1 Do similar modules already exist in some form?</h4>
If so, please try to reuse the existing modules either in whole or
by inheriting useful features into a new class. If this is not
practical try to get together with the module authors to work on
extending or enhancing the functionality of the existing modules.
A perfect example is the plethora of packages in perl4 for dealing
with command line options.
<p> </p>
If you are writing a module to expand an already existing set of
modules, please coordinate with the author of the package. It
helps if you follow the same naming scheme and module interaction
scheme as the original author.
<p> </p>
<h4>2.2 Try to design the new module to be easy to extend and reuse.</h4>
Use blessed references. Use the two argument form of bless to bless
into the class name given as the first parameter of the constructor,
e.g.:
<p> </p>
<blockquote> sub new {
my $class = shift;
return bless {}, $class;
}
</blockquote>
or even this if you'd like it to be used as either a static
or a virtual method.
<p> </p>
<blockquote> sub new {
my $self = shift;
my $class = ref($self) || $self;
return bless {}, $class;
}
</blockquote>
Pass arrays as references so more parameters can be added later
(it's also faster). Convert functions into methods where
appropriate. Split large methods into smaller more flexible ones.
Inherit methods from other modules if appropriate.
<p> </p>
Avoid class name tests like: die "Invalid" unless ref $ref eq 'FOO'.
Generally you can delete the "eq 'FOO'" part with no harm at all.
Let the objects look after themselves! If it's vital then you can
use the UNIVERSAL methods isa and can. Generally, avoid hardwired
class names as far as possible.
<p> </p>
Avoid $r->Class::func() where using @ISA=qw(... Class ...) and
$r->func() would work (see perlbot man page for more details).
<p> </p>
Use autosplit or the SelfLoader module so little used or newly added
functions won't be a burden to programs which don't use them. Add
test functions to the module after __END__ either using autosplit or
by saying:
<p> </p>
<blockquote> eval join('',<main::DATA>) || die $@ unless caller();
</blockquote>
Does your module pass the 'empty sub-class' test? If you say
"@SUBCLASS::ISA = qw(YOURCLASS);" your applications should be able
to use SUBCLASS in exactly the same way as YOURCLASS. For example,
does your application still work if you change: $obj = new YOURCLASS;
into: $obj = new SUBCLASS; ?
<p> </p>
Avoid keeping any state information in your packages. It makes it
difficult for multiple other packages to use yours. Keep state
information in objects.
<p> </p>
Always use -w. Try to "use strict;" (or "use strict qw(...);").
Remember that you can add "no strict qw(...);" to individual blocks
of code which need less strictness. Always use -w. Always use -w!
Follow the guidelines in the perlstyle(1) manual.
<p> </p>
<h4>2.3 Some simple style guidelines</h4>
The perlstyle manual supplied with perl has many helpful points.
<p> </p>
Coding style is a matter of personal taste. Many people evolve their
style over several years as they learn what helps them write and
maintain good code. Here's one set of assorted suggestions that
seem to be widely used by experienced developers:
<p> </p>
Use underscores to separate words. It is generally easier to read
$var_names_like_this than $VarNamesLikeThis, especially for
non-native speakers of English. It's also a simple rule that works
consistently with VAR_NAMES_LIKE_THIS.
<p> </p>
Package/Module names are an exception to this rule. Perl informally
reserves lowercase module names for 'pragma' modules like integer
and strict. Other modules normally begin with a capital letter and
use mixed case with no underscores (need to be short and portable).
<p> </p>
You may find it helpful to use letter case to indicate the scope
or nature of a variable. For example:
<p> </p>
<blockquote> $ALL_CAPS_HERE constants only (beware clashes with perl vars)
$Some_Caps_Here package-wide global/static
$no_caps_here function scope my() or local() variables
</blockquote>
Function and method names seem to work best as all lowercase.
E.g., $obj->as_string().
<p> </p>
You can use a leading underscore to indicate that a variable or
function should not be used outside the package that defined it.
<p> </p>
For method calls use either
<p> </p>
<blockquote> $foo = new Foo $arg1, $arg2; # no parentheses
$foo = Foo->new($arg1, $arg2);
</blockquote>
but avoid the ambiguous form
<p> </p>
<blockquote> $foo = new Foo($arg1, $arg2); # Foo() looks like function call
</blockquote>
It can be very helpful if the names of the classes that your module
uses can be specified as parameters. Consider:
<p> </p>
<blockquote> $dog_class = $args{dog_class} || 'Dog';
$spot = $dog_class->new(...);
</blockquote>
This allows the user of your module to specify an alternative class
(typically a subclass of the one you would normally have used).
<p> </p>
On how to report constructor failure, Larry said:
<p> </p>
I tend to see it as exceptional enough that I'll throw a real Perl
exception (die) if I can't construct an object. This has a couple
of advantages right off the bat. First, you don't have to check the
return value of every constructor. Just say "$fido = new Doggie;"
and presume it succeeded. This leads to clearer code in most cases.
<p> </p>
Second, if it does fail, you get a better diagnostic than just the
undefinedness of the return value. In fact, the exception it throws
may be quite rich in "stacked" error messages, if it's rethrowing an
exception caught further in.
<p> </p>
And you can always catch the exception if it does happen using eval {}.
<p> </p>
If, on the other hand, you expect your constructor to fail a goodly
part of the time, then you shouldn't use exceptions, but you should
document the interface so that people will know to check the return
value. You don't need to use defined(), since a constructor would
only return a true reference or a false undef. So good Perl style
for checking a return value would simply say
<p> </p>
<blockquote> $conn = new Connection $addr
or die "Couldn't create Connection";
</blockquote>
In general, make as many things meaningful in a Boolean context as
you can. This leads to straightforward code. Never write anything
like
<p> </p>
<blockquote> if (do_your_thing() == OK)
</blockquote>
in Perl. That's just asking for logic errors and domain errors.
Just write
<p> </p>
<blockquote> if (do_your_thing())
</blockquote>
Perl is designed to help you eschew obfuscation, if that's your thing.
<p> </p>
<h4>2.4 Select what to export.</h4>
Do NOT export method names!
Do NOT export anything else by default without a good reason!
<p> </p>
Exports pollute the namespace of the module user. If you must
export try to use @EXPORT_OK in preference to @EXPORT and avoid
short or common names to reduce the risk of name clashes.
<p> </p>
Generally anything not exported is still accessible from outside the
module using the ModuleName::item_name (or $blessed_ref->method)
syntax. By convention you can use a leading underscore on names to
informally indicate that they are 'internal' and not for public use.
<p> </p>
(It is actually possible to get private functions by saying:
my $subref = sub { ... }; &$subref; But there's no way to call that
directly as a method, since a method must have a name in the symbol
table.)
<p> </p>
As a general rule, if the module is trying to be object oriented
then export nothing. If it's just a collection of functions then
@EXPORT_OK anything but use @EXPORT with caution.
<p> </p>
<h4>2.5 Select a name for the module.</h4>
This name should be as descriptive, accurate and complete as
possible. Avoid any risk of ambiguity. Always try to use two or
more whole words. Generally the name should reflect what is special
about what the module does rather than how it does it.
<p> </p>
Having 57 modules all called Sort will not make life easy for anyone
(though having 23 called Sort::Quick is only marginally better :-).
Imagine someone trying to install your module alongside many others.
If in any doubt ask for suggestions in comp.lang.perl.modules or
<a href="mailto:[email protected]">[email protected]</a>
.
<p> </p>
Please use a nested module name to informally group or categorise
a module, e.g., placing a sorting module into a Sort:: category.
A module should have a very good reason not to have a nested name.
Please avoid using more than one level of nesting for module names
(packages or classes within modules can, of course, use any number).
<p> </p>
Module names should begin with a capital letter. Lowercase names are
reserved for special modules such as pragmas (e.g., lib and strict).
<p> </p>
Note that module names are not related to class hierarchies.
A module name Foo::Bar does not in any way imply that Foo::Bar
inherits from Foo. Nested names are simply used to provide some
useful categorisation for humans. The same is generally true for
all package names.
<p> </p>
Since the CPAN is huge and growing daily, it's essential that
module authors choose names which lend themselves to browsing.
That means minimizing acronyms, cute names, and jargon. Also,
don't make up a new top level category unless you have a good
reason; please choose an already-existing category when
possible. Send mail to
<a href="mailto:[email protected]">[email protected]</a>
before you upload, so
we can help you select a name.
<p> </p>
If you insist on a name that we consider inappropriate, we
won't prevent you from uploading your module -- but it'll
remain in your "author" directory and won't be directly visible
from CPAN/modules/by-module.
<p> </p>
We appreciate the efforts of the contributors who have helped
make the CPAN the world's largest reusable code repository.
Please help us enhance it by working with us to choose the
best name possible.
<p> </p>
If you are developing a suite of related modules/classes it's good
practice to use nested classes with a common prefix as this will
avoid namespace clashes. For example: Xyz::Control, Xyz::View,
Xyz::Model etc. Use the modules in this list as a naming guide.
<p> </p>
If adding a new module to a set, follow the original author's
standards for naming modules and the interface to methods in
those modules.
<p> </p>
If developing modules for private internal or project specific use,
that will never be released to the public, then you should ensure
that their names will not clash with any future public module. You
can do this either by using the reserved Local::* category or by
using an underscore in the top level name like Foo_Corp::*.
<p> </p>
To be portable each component of a module name should be limited to
11 characters. If it might be used on DOS then try to ensure each is
unique in the first 8 characters. Nested modules make this easier.
<p> </p>
<h4>2.6 Have you got it right?</h4>
How do you know that you've made the right decisions? Have you
picked an interface design that will cause problems later? Have
you picked the most appropriate name? Do you have any questions?
<p> </p>
The best way to know for sure, and pick up many helpful suggestions,
is to ask someone who knows. The comp.lang.perl.modules Usenet
newsgroup is read by just about all the people who develop modules
and it's generally the best place to ask first. If you need more
help then try
<a href="mailto:[email protected]">[email protected]</a>
.
<p> </p>
All you need to do is post a short summary of the module, its
purpose and interfaces. A few lines on each of the main methods is
probably enough. (If you post the whole module it might be ignored
by busy people - generally the very people you want to read it!)
<p> </p>
Don't worry about posting if you can't say when the module will be
ready - just say so in the message. It might be worth inviting
others to help you, they may be able to complete it for you!
<p> </p>
<h4>2.7 README and other Additional Files.</h4>
It's well known that software developers usually fully document the
software they write. If, however, the world is in urgent need of
your software and there is not enough time to write the full
documentation please at least provide a README file containing:
<p> </p>
<ul><li> A description of the module/package/extension etc.</li><li> A copyright notice - see below.</li><li> Prerequisites - what else you may need to have.</li><li> How to build it - possible changes to Makefile.PL etc.</li><li> How to install it.</li><li> Recent changes in this release, especially incompatibilities</li><li> Changes / enhancements you plan to make in the future.</li></ul>
<p> </p>
If the README file seems to be getting too large you may wish to
split out some of the sections into separate files: INSTALL,
Copying, ToDo etc.
<p> </p>
<h4>2.8 Adding a Copyright Notice.</h4>
How you choose to licence your work is a personal decision.
The general mechanism is to assert your Copyright and then make
a declaration of how others may copy/use/modify your work.
<p> </p>
Perl, for example, is supplied with two types of licence: The GNU
GPL and The Artistic License (see the files README, Copying and
Artistic). Larry has good reasons for NOT just using the GNU GPL.
<p> </p>
My personal recommendation, out of respect for Larry, Perl and the
perl community at large is to simply state something like:
<p> </p>
<blockquote> Copyright (c) 1997 Your Name. All rights reserved.
This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.
</blockquote>
This statement should at least appear in the README file. You may
also wish to include it in a Copying file and your source files.
Remember to include the other words in addition to the Copyright.
<p> </p>
<h4>2.9 Give the module a version/issue/release number.</h4>
To be fully compatible with the Exporter and MakeMaker modules you
should store your module's version number in a non-my package
variable called $VERSION. This should be a valid floating point
number with at least two digits after the decimal (ie hundredths,
e.g, $VERSION = "0.01"). See Exporter.pm for details.
<p> </p>
Don't use a "1.3.2" style version directly. If you use RCS or a
similar system which supports multilevel versions/branches you can
use this (but put it all on one line for MakeMaker VERSION_FROM):
<p> </p>
$VERSION = do { my @r=(q$Revision: 3.112 $=~/\d+/g);
sprintf "%d."."%03d"x$#r,@r };
<p> </p>
It may be handy to add a function or method to retrieve the number.
Use the number in announcements and archive file names when
releasing the module (ModuleName-1.02.tar.gz).
See perldoc ExtUtils::MakeMaker.pm for details.
<p> </p>
<h4>2.10 Listing Prerequisites in a Bundle module</h4>
If your module needs some others that are available on CPAN, you
might consider creating a 'bundle' module that lists all the
prerequisites in a standardized way. Automatic installation software
such as the CPAN.pm module can take advantage of such a listing and
enable your users to install all prerequisites and your own module
with one single command. See the CPAN.pm module for details.
<p> </p>
<h4>2.11 How to release and distribute a module.</h4>
By far the best way to release modules is to register yourself with
the Perl Authors Upload Server (PAUSE). By registering with PAUSE
you will be able to easily upload (or mirror) your modules to the
PAUSE server from where they will be mirrored to CPAN sites across
the planet.
<p> </p>
It's good idea to post an announcement of the availability of your
module to the comp.lang.perl.announce Usenet newsgroup. This will
at least ensure very wide once-off distribution.
<p> </p>
If not using PAUSE you should place the module into a major ftp
archive and include details of it's location in your announcement.
Some notes about ftp archives: Please use a long descriptive file
name which includes the version number. Most incoming directories
will not be readable/listable, i.e., you won't be able to see your
file after uploading it. Remember to send your email notification
message as soon as possible after uploading else your file may get
deleted automatically. Allow time for the file to be processed
and/or check the file has been processed before announcing its
location.
<p> </p>
FTP Archives for Perl Modules:
<p> </p>
Follow the instructions and links on
<p> </p>
<a href="http://www.cpan.org/modules/04pause.html">http://www.cpan.org/modules/04pause.html</a>
<p> </p>
or upload to:
<p> </p>
<a href="ftp://pause.kbx.de/incoming">ftp://pause.kbx.de/incoming</a>
<p> </p>
and notify
<a href="mailto:[email protected]">[email protected]</a>
.
<p> </p>
By using the PAUSE WWW interface you can ask the Upload Server to
mirror your modules from your ftp or WWW site into your own
directory on CPAN. Please remember to send us an updated entry for
the Module list!
<p> </p>
<h4>2.12 Take care when changing a released module.</h4>
Always strive to remain compatible with previous released versions
(see 2.2 above) Otherwise try to add a mechanism to revert to the
old behaviour if people rely on it. Document incompatible changes.
<p> </p>
<h3><a id="ID3_Guidelinesf" name="ID3_Guidelinesf">3) Guidelines for Converting Perl 4 Library Scripts into Modules</a></h3>
<h4>3.1 There is no requirement to convert anything.</h4>
If it ain't broke, don't fix it! Perl 4 library scripts should
continue to work with no problems. You may need to make some minor
changes (like escaping non-array @'s in double quoted strings) but
there is no need to convert a .pl file into a Module for just that.
See perltrap.pod for details of all known perl4-to-perl5 issues.
<p> </p>
<h4>3.2 Consider the implications.</h4>
All the perl applications which make use of the script will need to
be changed (slightly) if the script is converted into a module. Is
it worth it unless you plan to make other changes at the same time?
<p> </p>
<h4>3.3 Make the most of the opportunity.</h4>
If you are going to convert the script to a module you can use the
opportunity to redesign the interface. The 'Guidelines for Module
Creation' above include many of the issues you should consider.
<p> </p>
<h4>3.4 The pl2pm utility will get you started.</h4>
This utility will read *.pl files (given as parameters) and write corresponding *.pm files. The pl2pm utilities does the following:<ul><li> Adds the standard Module prologue lines</li><li> Converts package specifiers from ' to ::</li><li> Converts die(...) to croak(...)</li><li> Several other minor changes</li></ul> Being a mechanical process pl2pm is not bullet proof. The converted code will need careful checking, especially any package statements. Don't delete the original .pl file till the new .pm one works!<p> </p>
<h3><a id="ID4_Guidelinesf" name="ID4_Guidelinesf">4) Guidelines for Reusing Application Code</a></h3>
4.1 Complete applications rarely belong in the Perl Module Library.<p> </p>
4.2 Many applications contain some perl code which could be reused.
Help save the world! Share your code in a form that makes it easy
to reuse.
<p> </p>
4.3 Break-out the reusable code into one or more separate module files.<p> </p>
4.4 Take the opportunity to reconsider and redesign the interfaces.<p> </p>
4.5 In some cases the 'application' can then be reduced to a small
fragment of code built on top of the reusable modules. In these
cases the application could invoked as:
<p> </p>
<h4><a id="ID5_NamespaceCo" name="ID5_NamespaceCo">5) Namespace Coordination</a></h4>
The maintainers of the module list are not the Internic for perl
namespaces. They do neither sell namespaces nor can they establish
property rights. What they try to do is to minimize namespace clashes
and maximize usablility of the CPAN archive by setting up a catalogue
of modules and control the indexers. Time permitting, they will also
try to give advice for what they think is a proper usage of the
namespace.
<p> </p>
It is an important part of the namespace concept that the module list
maintainers do not guarantee to you that somebody else won't use the,
say, Foo::Bar namespace. The upload area is not censored except for
abuse. People are free to upload any modules they like. Instead, there
are several levels of protection for your namespaces:
<p> </p>
a) The most important is the module list which actually lists and
proclaims your namespace.
<p> </p>
b) The second is the indexing mechanism of the CPAN. Modules are
indexed on a first-come-first-serve basis. The module namespace
that is uploaded for the first time ever gets indexed, but not the
module of the second one who tries to use the same namespace.
<p> </p>
c) As the whole process is trying to benefit the community, all
parties are subject to a wider monitoring within the community.
This is sometimes referred to as security by visibility.
<p> </p>
d) So the next level of namespace protection is the common sense. Your
own common sense. Help to save the world. If you get the impression
that something goes wrong with regard to namespaces, please write
to
<a href="mailto:[email protected]">[email protected]</a>
and let them know.
<p> </p>
e) The perhaps most interesting namespace protection is provided by
the perl symbol table itself. A namespace Foo:: is just a package
name and its relationship to a namespace Foo::Bar:: is not
predetermined whatsoever. The two namespaces can be closely or
loosely related or not related at all, but what's most important,
they can be writen by different authors who may work rather
independently from each other. So if you have registered any
namespace, it does not mean that you own the whole namespace tree
that starts there. If you are registered as the contact for
Foo::Bar, you are not necessarily also associated with
Foo::Bar::Baz.
<p> </p>
f) In a few rare cases the module list people restrict indexing of
certain categories. For example:
DBI::* under the control of Tim Bunce
Sun::* under the control of Sun Microsystems
<p> </p>
<p> </p>
<h2><a id="Part2-ThePerl5M" name="Part2-ThePerl5M">Part 2 - The Perl 5 Module List</a></h2>
The remainder of this document is divided up into sections. Each
section deals with a particular topic and lists all known modules
related to that topic. Modules are only listed in one section so
check all sections that might related to your particular needs.
<p> </p>
All the information corresponds to the latest updates we have received.
We don't record the version number or release dates of the listed
Modules. Nor do we record the locations of these Modules. Consult the
contact, try the usual perl CPAN sites or ask in comp.lang.perl.modules.
Please do *not* ask us directly, we simply don't have the time. Sorry.
<p> </p>
<h4><a id="ID1_ModuleListi" name="ID1_ModuleListi">1) Module Listing Format</a></h4>
Each Module listing is very short. The main goal is to simply publish
the existence of the modules, or ideas for modules, and enough contact
information for you to find out more. Each listing includes some
characters which convey (approximate) basic status information.
<p> </p>
<h4>For example:</h4>
<pre>Name DSLIP Description Info
------------- ----- -------------------------------------------- -----
Fcntl Sdcfp Defines fcntl() constants (see File::Lock) JHI
</pre><p> </p>
<h4>Where the 'DSLIP' characters have the following meanings:</h4>
<ul><li> D - Development Stage (Note: *NO IMPLIED TIMESCALES*):</li><li><ul><li> i - Idea, listed to gain consensus or as a placeholder</li><li> c - under construction but pre-alpha (not yet released)</li><li> a/b - Alpha/Beta testing</li><li> R - Released</li><li> M - Mature (no rigorous definition)</li><li> S - Standard, supplied with Perl 5</li></ul></li></ul>
<ul><li> S - Support Level:</li><li><ul><li> m - Mailing-list</li><li> d - Developer</li><li> u - Usenet newsgroup comp.lang.perl.modules</li><li> n - None known, try comp.lang.perl.modules</li></ul></li></ul>
<ul><li> L - Language Used:</li><li><ul><li> p - Perl-only, no compiler needed, should be platform independent</li><li> c - C and perl, a C compiler will be needed</li><li> h - Hybrid, written in perl with optional C code, no compiler needed</li><li> + - C++ and perl, a C++ compiler will be needed</li><li> o - perl and another language other than C or C++</li></ul></li></ul>
<ul><li> I - Interface Style</li><li><ul><li> f - plain Functions, no references used</li><li> h - hybrid, object and function interfaces available</li><li> n - no interface at all (huh?)</li><li> r - some use of unblessed References or ties</li><li> O - Object oriented using blessed references and/or inheritance</li></ul></li></ul>
<ul><li> P - Public License</li><li><ul><li> p - Standard-Perl: user may choose between GPL and Artistic</li><li> g - GPL: GNU General Public License</li><li> l - LGPL: "GNU Lesser General Public License" (previously known as "GNU Library</li><li> General Public License")</li><li> b - BSD: The BSD License</li><li> a - Artistic license alone</li><li> o - other (but distribution allowed without restrictions)</li></ul></li></ul>
DISCLAIMER: The status of the Public License field is there for
informational purpose only and does not constitute a legal binding of
any kind. To obtain proper information about the Licencing terms of a
module and its accompanying files, please refer to the distribution of
the modules or contact the author as appropriate. Please inform
<a href="mailto:[email protected]">[email protected]</a>
if you encounter any mismatch between the contents of
the Public License field and what the distribution actually says about
it.
<p> </p>
Where letters are missing they can usually be inferred from the
others. For example 'i' implies 'id', 'S' implies 'Su'.
<p> </p>
The Info column gives a contact reference 'tag'. Lookup this tag in
the "Information / Contact Reference Details" section in Pert 3 of
this document. If no contact is given always try asking in
comp.lang.perl.modules.
<p> </p>
Most Modules are nested in categories such as IPC::Open2 and IPC::Open3.
These are shown as 'IPC::' on one line then each module listed below
with a '::' prefix.
<p> </p>
<h4>Ideas For Adoption</h4>
Modules listed as in the 'i' Development Stage with no contact
reference are ideas without an owner. Feel free to 'adopt' these but
please let me know so that we can update the list and thus inform anyone
else who might be interested. Adoption simply means that you either
hope to implement the module one day or would like to cooperate with
anyone else who might be interested in implementing it.
<p> </p>
<h4>Cooperation</h4>
Similarly, if an idea that interests you has been adopted by someone
please contact them so you can share ideas. Just because an idea has
been adopted does NOT imply that it's going to be implemented. Just
because a module is listed and being implemented does NOT mean it'll
get finished. Waiting silently in the hope that the Module will appear
one day is unlikely to be fruitful! Offer to help. Cooperate. Pool your
efforts. Go on, try it!
<p> </p>
The same applies to modules in all states. Most modules are developed
in limited spare time. If you're interested in a module don't just wait
for it to happen, offer to help.
<p> </p>
Module developers should feel free to announce incomplete work early.
If you're not going to be able to spend much time on something then say
so. If you invite cooperation maybe someone will implement it for you!
<p> </p>
<p> </p>
<h4><a href="by-category/02_Perl_Core_Modules"
id="ID2_PerlCoreMod" name="ID2_PerlCoreMod">2) Perl Core Modules, Perl Language Extensions and Documentation Tools</a></h4>
<pre>Name <a href="#ID1_ModuleListi">DSLIP</a> Description Info
------------ ----- -------------------------------------------- ----
CORE Sucf? Internal package for perl native functions <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=UNIVERSAL">UNIVERSAL</a> SucOp Internal universal base-class <a href="../authors/00whois.html#P5P">P5P</a>
SUPER SucO? Internal class to access superclass methods <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=DynaLoader">DynaLoader</a> SucO? Dynamic loader for shared libraries <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=AutoLoader">AutoLoader</a> SupO? Automatic function loader (using AutoSplit) <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=SelfLoader">SelfLoader</a> SupO? Automatic function loader (using __DATA__) <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Exporter">Exporter</a> SupO? Implements default import method for modules <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Carp">Carp</a> Supf? Throw exceptions outside current package <a href="../authors/00whois.html#P5P">P5P</a>
Config Supf? Stores details of perl build configuration <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=English">English</a> Supf? Defines English names for special variables <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Symbol">Symbol</a> SupO? Create 'anonymous' symbol (typeglobs) refs <a href="http://search.cpan.org/search?author=CHIPS">CHIPS</a>
<a href="http://search.cpan.org/search?module=Opcode">Opcode</a> Supf? Disable named opcodes when compiling code <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Taint">Taint</a> bdpf? Utilities related to tainting <a href="http://search.cpan.org/search?author=PHOENIX">PHOENIX</a></pre> <h4>Perl Pragmatic Modules</h4>
<pre><a href="http://search.cpan.org/search?module=constant">constant</a> Supf? Define compile-time constants <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=diagnostics">diagnostics</a> Sdpf? For reporting perl diagnostics in full form <a href="http://search.cpan.org/search?author=TOMC">TOMC</a>
<a href="http://search.cpan.org/search?module=enum">enum</a> cdpf? resemble enumerated types in C <a href="http://search.cpan.org/search?author=ZENIN">ZENIN</a>
<a href="http://search.cpan.org/search?module=integer">integer</a> Supf? Controls float vs. integer arithmetic <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=less">less</a> Supf? Controls optimisations (yet unimplemented) <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=lib">lib</a> Supf? Simple way to add/delete directories in @INC <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=namespace">namespace</a> Rdpnp Perl pragma to use like C++ namespace alias <a href="http://search.cpan.org/search?author=AMICHAUER">AMICHAUER</a>
<a href="http://search.cpan.org/search?module=overload">overload</a> SdpO? Overload perl operators for new data types <a href="http://search.cpan.org/search?author=ILYAZ">ILYAZ</a>
<a href="http://search.cpan.org/search?module=sigtrap">sigtrap</a> Supf? For trapping an abort and giving a traceback <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=strict">strict</a> Supf? Controls averments (similar to pragmas) <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=subs">subs</a> Supf? use subs qw(x y); is short for sub x; sub y; <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=vars">vars</a> Supf? predeclare variable names <a href="../authors/00whois.html#P5P">P5P</a></pre> <h4>Experimental pragmatic modules live in the ex:: namespace</h4>
<pre>ex::
<a href="http://search.cpan.org/search?module=ex::implements">::implements</a> RdpO? Study in Polymorphism <a href="http://search.cpan.org/search?author=PDCAWLEY">PDCAWLEY</a>
<a href="http://search.cpan.org/search?module=ex::interface">::interface</a> RdpO? Another study in polymorphism <a href="http://search.cpan.org/search?author=PDCAWLEY">PDCAWLEY</a>
<a href="http://search.cpan.org/search?module=ex::override">::override</a> Rdpf? perl pragma to override core functions <a href="http://search.cpan.org/search?author=CTWETEN">CTWETEN</a>
::caution bdpn? Same as use warnings; use strict; <a href="http://search.cpan.org/search?author=YVES">YVES</a></pre> <pre>ex::constant::
<a href="http://search.cpan.org/search?module=ex::constant::vars">::vars</a> Rdph? Perl pragma to create readonly variables <a href="http://search.cpan.org/search?author=CTWETEN">CTWETEN</a></pre> <h4>Perl Language Extensions</h4>
<pre><a href="http://search.cpan.org/search?module=Alias">Alias</a> bdcf? Convenient access to data/code via aliases <a href="http://search.cpan.org/search?author=GSAR">GSAR</a>
<a href="http://search.cpan.org/search?module=End">End</a> RdpO? Generalized END {}. <a href="http://search.cpan.org/search?author=ABIGAIL">ABIGAIL</a>
<a href="http://search.cpan.org/search?module=Error">Error</a> adpOp Error/exception handling in an OO-ish way <a href="http://search.cpan.org/search?author=UARUN">UARUN</a>
<a href="http://search.cpan.org/search?module=NEXT">NEXT</a> RdpO? Perl5 implementation of NEXT (RFC190) <a href="http://search.cpan.org/search?author=DCONWAY">DCONWAY</a>
<a href="http://search.cpan.org/search?module=Perl">Perl</a> adcO? Create Perl interpreters from within Perl <a href="http://search.cpan.org/search?author=GSAR">GSAR</a>
Protect bdpf? declare subs private or member <a href="http://search.cpan.org/search?author=JDUNCAN">JDUNCAN</a>
<a href="http://search.cpan.org/search?module=Safe">Safe</a> SdcO? Restrict eval'd code to safe subset of ops <a href="http://search.cpan.org/search?author=MICB">MICB</a>
<a href="http://search.cpan.org/search?module=Softref">Softref</a> bdcf? Extension for weak/soft referenced SVs <a href="http://search.cpan.org/search?author=ILYAZ">ILYAZ</a></pre> <pre>Attribute::
<a href="http://search.cpan.org/search?module=Attribute::Handlers">::Handlers</a> RdpO? Simpler definition of attribute handlers <a href="http://search.cpan.org/search?author=ABERGMAN">ABERGMAN</a>
<a href="http://search.cpan.org/search?module=Attribute::Types">::Types</a> RdpO? Attributes that confer type on variables <a href="http://search.cpan.org/search?author=DCONWAY">DCONWAY</a>
<a href="http://search.cpan.org/search?module=Attribute::Memoize">::Memoize</a> RdpOp Attribute interface to Memoize.pm <a href="http://search.cpan.org/search?author=MARCEL">MARCEL</a>
<a href="http://search.cpan.org/search?module=Attribute::TieClasses">::TieClasses</a> RdpOp attribute wrappers for CPAN Tie classes <a href="http://search.cpan.org/search?author=MARCEL">MARCEL</a>
<a href="http://search.cpan.org/search?module=Attribute::Abstract">::Abstract</a> RdpOp implement abstract methods with attributes <a href="http://search.cpan.org/search?author=MARCEL">MARCEL</a>
<a href="http://search.cpan.org/search?module=Attribute::Overload">::Overload</a> RdpOp Attribute that makes overloading easier <a href="http://search.cpan.org/search?author=MARCEL">MARCEL</a>
<a href="http://search.cpan.org/search?module=Attribute::Deprecated">::Deprecated</a> RdpOp Mark deprecated methods <a href="http://search.cpan.org/search?author=KASEI">KASEI</a>
<a href="http://search.cpan.org/search?module=Attribute::Signature">::Signature</a> bdphp Signatures on methods and subroutines <a href="http://search.cpan.org/search?author=JDUNCAN">JDUNCAN</a></pre> <pre>Exporter::
::Import Rdpn? Alternate symbol exporter <a href="http://search.cpan.org/search?author=GARROW">GARROW</a>
::Options adpO? Extends Exporter to handle use-line options <a href="http://search.cpan.org/search?author=YSTH">YSTH</a>
::PkgAlias adpf? Load a module into multiple namespaces <a href="http://search.cpan.org/search?author=JDPORTER">JDPORTER</a></pre> <pre><a href="http://search.cpan.org/search?module=Inline">Inline</a> bdp?p Write Perl subroutines in other languages <a href="http://search.cpan.org/search?author=INGY">INGY</a>
Inline::
<a href="http://search.cpan.org/search?module=Inline::CPR">::CPR</a> adpn? C Perl Run - Embed Perl in C, ala Inline <a href="http://search.cpan.org/search?author=INGY">INGY</a>
<a href="http://search.cpan.org/search?module=Inline::C">::C</a> bdpnp Write Perl subroutines in C <a href="http://search.cpan.org/search?author=INGY">INGY</a>
<a href="http://search.cpan.org/search?module=Inline::CPP">::CPP</a> bdpO? Easy implementation of C++ extensions <a href="http://search.cpan.org/search?author=NEILW">NEILW</a>
<a href="http://search.cpan.org/search?module=Inline::Python">::Python</a> adcO? Easy implementation of Python extensions <a href="http://search.cpan.org/search?author=NEILW">NEILW</a>
<a href="http://search.cpan.org/search?module=Inline::Tcl">::Tcl</a> adcf? Write Perl subroutines in Tcl <a href="http://search.cpan.org/search?author=RRS">RRS</a>
<a href="http://search.cpan.org/search?module=Inline::Java">::Java</a> amhpp Easy implementation of Java extensions <a href="http://search.cpan.org/search?author=PATL">PATL</a>
<a href="http://search.cpan.org/search?module=Inline::ASM">::ASM</a> adpO? Write Perl subroutines in Assembler <a href="http://search.cpan.org/search?author=NEILW">NEILW</a>
<a href="http://search.cpan.org/search?module=Inline::Struct">::Struct</a> adpO? Bind C structures directly to Perl. <a href="http://search.cpan.org/search?author=NEILW">NEILW</a>
<a href="http://search.cpan.org/search?module=Inline::Files">::Files</a> RdpO? Multiple virtual files after __END__ <a href="http://search.cpan.org/search?author=DCONWAY">DCONWAY</a>
<a href="http://search.cpan.org/search?module=Inline::Guile">::Guile</a> amhhp Inline module for Guile Scheme interpreter <a href="http://search.cpan.org/search?author=SAMTREGAR">SAMTREGAR</a></pre> <pre>Regexp::
<a href="http://search.cpan.org/search?module=Regexp::Common">::Common</a> RdpO? Provide commonly requested regular expr. <a href="http://search.cpan.org/search?author=ABIGAIL">ABIGAIL</a>
<a href="http://search.cpan.org/search?module=Regexp::Shellish">::Shellish</a> RdpO? Shell-like regular expressions <a href="http://search.cpan.org/search?author=RBS">RBS</a>
::Func adpf? Replace =~, !~, m//, s/// with functions <a href="http://search.cpan.org/search?author=NWIGER">NWIGER</a></pre> <pre>Safe::
<a href="http://search.cpan.org/search?module=Safe::Hole">::Hole</a> bdcO? Exec subs in the original package from Safe <a href="http://search.cpan.org/search?author=SEYN">SEYN</a></pre> <pre>Symbol::
::Table RdpO? OO interface to package symbols <a href="http://search.cpan.org/search?author=GARROW">GARROW</a></pre> <pre>Symbol::Approx::
<a href="http://search.cpan.org/search?module=Symbol::Approx::Sub">::Sub</a> Rmphp Call subroutines using approximate names <a href="http://search.cpan.org/search?author=DAVECROSS">DAVECROSS</a></pre> <h4>The Perl Compiler</h4>
<pre><a href="http://search.cpan.org/search?module=B">B</a> aucO? The Perl Compiler <a href="http://search.cpan.org/search?author=MICB">MICB</a>
<a href="http://search.cpan.org/search?module=O">O</a> aucO? Perl Compiler frontends <a href="http://search.cpan.org/search?author=MICB">MICB</a></pre> <pre>B::
<a href="http://search.cpan.org/search?module=B::Fathom">::Fathom</a> bdpO? Estimate the readability of Perl code <a href="http://search.cpan.org/search?author=KSTAR">KSTAR</a>
<a href="http://search.cpan.org/search?module=B::Graph">::Graph</a> bdpr? Perl Compiler backend to diagram OP trees <a href="http://search.cpan.org/search?author=SMCCAM">SMCCAM</a>
<a href="http://search.cpan.org/search?module=B::LexInfo">::LexInfo</a> bdcO? Show info about subroutine lexical variables <a href="http://search.cpan.org/search?author=DOUGM">DOUGM</a>
<a href="http://search.cpan.org/search?module=B::Size">::Size</a> bdcO? Measure size of Perl OPs and SVs <a href="http://search.cpan.org/search?author=DOUGM">DOUGM</a>
<a href="http://search.cpan.org/search?module=B::TerseSize">::TerseSize</a> bdpO? Info about ops and their (estimated) size <a href="http://search.cpan.org/search?author=DOUGM">DOUGM</a></pre> <h4>Source Code Filters</h4>
<pre>Filter::Util::
<a href="http://search.cpan.org/search?module=Filter::Util::Exec">::Exec</a> bdcf? Interface for creation of coprocess Filters <a href="http://search.cpan.org/search?author=PMQS">PMQS</a>
<a href="http://search.cpan.org/search?module=Filter::Util::Call">::Call</a> bdcf? Interface for creation of Perl Filters <a href="http://search.cpan.org/search?author=PMQS">PMQS</a></pre> <pre>Filter::
<a href="http://search.cpan.org/search?module=Filter::exec">::exec</a> bdcf? Filters script through an external command <a href="http://search.cpan.org/search?author=PMQS">PMQS</a>
<a href="http://search.cpan.org/search?module=Filter::sh">::sh</a> bdcf? Filters script through a shell command <a href="http://search.cpan.org/search?author=PMQS">PMQS</a>
<a href="http://search.cpan.org/search?module=Filter::cpp">::cpp</a> bdcf? Filters script through C preprocessor <a href="http://search.cpan.org/search?author=PMQS">PMQS</a>
<a href="http://search.cpan.org/search?module=Filter::tee">::tee</a> bdcf? Copies to file perl source being compiled <a href="http://search.cpan.org/search?author=PMQS">PMQS</a>
<a href="http://search.cpan.org/search?module=Filter::decrypt">::decrypt</a> bdcf? Template for a perl source decryption filter <a href="http://search.cpan.org/search?author=PMQS">PMQS</a>
<a href="http://search.cpan.org/search?module=Filter::Simple">::Simple</a> RdpO? Simplified source filtering <a href="http://search.cpan.org/search?author=DCONWAY">DCONWAY</a>
::constant idpnp constant mod working like real Pre Processor <a href="http://search.cpan.org/search?author=MZSANFORD">MZSANFORD</a>
<a href="http://search.cpan.org/search?module=Filter::Trigraph">::Trigraph</a> bdpnp Understand ANSI C trigraphs in Perl source. <a href="http://search.cpan.org/search?author=KASEI">KASEI</a></pre> <pre><a href="http://search.cpan.org/search?module=PerlIO">PerlIO</a> Rucnp On demand loader for PerlIO layers <a href="../authors/00whois.html#P5P">P5P</a></pre> <pre>PerlIO::
<a href="http://search.cpan.org/search?module=PerlIO::gzip">::gzip</a> RdcO? provide a PerlIO layer to gzip/gunzip <a href="http://search.cpan.org/search?author=NWCLARK">NWCLARK</a></pre> <h4>Thread support (note that these are experimental, i.e. pre-alpha)</h4>
<pre><a href="http://search.cpan.org/search?module=Thread">Thread</a> cuhO? Manipulate threads in Perl (EXPERIMENTAL) <a href="../authors/00whois.html#P5P">P5P</a></pre> <pre>Thread::
::Group bdph? Wait()-like and grouping functions <a href="http://search.cpan.org/search?author=DSUGAL">DSUGAL</a>
<a href="http://search.cpan.org/search?module=Thread::Pool">::Pool</a> bdpOp Worker pools to run Perl code asynchronously <a href="http://search.cpan.org/search?author=ELIZABETH">ELIZABETH</a>
<a href="http://search.cpan.org/search?module=Thread::Queue">::Queue</a> cuph? Thread-safe queues <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Thread::Semaphore">::Semaphore</a> cuph? Thread-safe semaphores <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Thread::Signal">::Signal</a> cuhh? A thread which runs signal handlers reliably <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Thread::Specific">::Specific</a> cuhh? Thread-specific keys <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Thread::RWLock">::RWLock</a> RdpOp rwlock implementation for perl threads <a href="http://search.cpan.org/search?author=AFERBER">AFERBER</a>
::IO i ? IO routines <a href="http://search.cpan.org/search?author=DSUGAL">DSUGAL</a>
::Object i ? OO routines <a href="http://search.cpan.org/search?author=DSUGAL">DSUGAL</a></pre> <h4>Module Support</h4>
<pre>Module::
<a href="http://search.cpan.org/search?module=Module::Reload">::Reload</a> Rdpf? Reloads files in %INC based on timestamps <a href="http://search.cpan.org/search?author=JPRIT">JPRIT</a>
<a href="http://search.cpan.org/search?module=Module::InstalledVersion">::InstalledVersion</a> bdpOp Find version number of installed module <a href="http://search.cpan.org/search?author=SKUD">SKUD</a>
<a href="http://search.cpan.org/search?module=Module::Use">::Use</a> bdpnp Tracks modules loaded by a script <a href="http://search.cpan.org/search?author=JSMITH">JSMITH</a>
<a href="http://search.cpan.org/search?module=Module::Signature">::Signature</a> cdpfp Module signature file manipulation <a href="http://search.cpan.org/search?author=AUTRIJUS">AUTRIJUS</a></pre> <h4>Documentation Tools:</h4>
<pre>Pod::
<a href="http://search.cpan.org/search?module=Pod::Diff">::Diff</a> cdpf? compare two POD files and report diff <a href="http://search.cpan.org/search?author=IANC">IANC</a>
<a href="http://search.cpan.org/search?module=Pod::DocBook">::DocBook</a> adpO? convert POD to and from DocBook <a href="http://search.cpan.org/search?author=MBERENDS">MBERENDS</a>
<a href="http://search.cpan.org/search?module=Pod::HTML">::HTML</a> cdpr? converter to HTML <a href="http://search.cpan.org/search?author=KJALB">KJALB</a>
<a href="http://search.cpan.org/search?module=Pod::HTML2Pod">::HTML2Pod</a> RdpOp Translate HTML into POD <a href="http://search.cpan.org/search?author=SBURKE">SBURKE</a>
<a href="http://search.cpan.org/search?module=Pod::Hlp">::Hlp</a> RdpO? Convert POD to formatted VMS Help text <a href="http://search.cpan.org/search?author=PVHP">PVHP</a>
::Index cdpr? index generator <a href="http://search.cpan.org/search?author=KJALB">KJALB</a>
<a href="http://search.cpan.org/search?module=Pod::LaTeX">::LaTeX</a> bdpOp Converts pod to latex with Pod::Parser <a href="http://search.cpan.org/search?author=TJENNESS">TJENNESS</a>
::Latex cdpr? converter to LaTeX <a href="http://search.cpan.org/search?author=KJALB">KJALB</a>
<a href="http://search.cpan.org/search?module=Pod::Lyx">::Lyx</a> adpO? A pod to LyX format conversion class <a href="http://search.cpan.org/search?author=RICHARDJ">RICHARDJ</a>
::MIF adpO? converter to FrameMaker MIF <a href="http://search.cpan.org/search?author=JNH">JNH</a>
<a href="http://search.cpan.org/search?module=Pod::Man">::Man</a> cdpr? converter to man page <a href="http://search.cpan.org/search?author=KJALB">KJALB</a>
<a href="http://search.cpan.org/search?module=Pod::PP">::PP</a> adpOa A Pod pre-processor <a href="http://search.cpan.org/search?author=RAM">RAM</a>
<a href="http://search.cpan.org/search?module=Pod::Parser">::Parser</a> bdpO? Base class for parsing pod syntax <a href="http://search.cpan.org/search?author=BRADAPP">BRADAPP</a>
<a href="http://search.cpan.org/search?module=Pod::Pdf">::Pdf</a> bdpf? Converter to PDF <a href="http://search.cpan.org/search?author=AJFRY">AJFRY</a>
::Pod cdpr? converter to canonical pod <a href="http://search.cpan.org/search?author=KJALB">KJALB</a>
<a href="http://search.cpan.org/search?module=Pod::RTF">::RTF</a> cdpr? converter to RTF <a href="http://search.cpan.org/search?author=KJALB">KJALB</a>
<a href="http://search.cpan.org/search?module=Pod::Rtf">::Rtf</a> RdpO? Converter from POD to Rich Text Format <a href="http://search.cpan.org/search?author=PVHP">PVHP</a>
<a href="http://search.cpan.org/search?module=Pod::Sdf">::Sdf</a> cdpf? converter to SDF <a href="http://search.cpan.org/search?author=IANC">IANC</a>
<a href="http://search.cpan.org/search?module=Pod::Select">::Select</a> bdpf? Print only selected sections of pod docs <a href="http://search.cpan.org/search?author=BRADAPP">BRADAPP</a>
<a href="http://search.cpan.org/search?module=Pod::Simplify">::Simplify</a> cdpr? Common pod parsing code <a href="http://search.cpan.org/search?author=KJALB">KJALB</a>
::Texinfo cdpr? converter to texinfo <a href="http://search.cpan.org/search?author=KJALB">KJALB</a>
<a href="http://search.cpan.org/search?module=Pod::Text">::Text</a> Supf? convert POD data to formatted ASCII text <a href="http://search.cpan.org/search?author=TOMC">TOMC</a>
<a href="http://search.cpan.org/search?module=Pod::Usage">::Usage</a> bdpf? Print Usage messages based on your own pod <a href="http://search.cpan.org/search?author=BRADAPP">BRADAPP</a>
<a href="http://search.cpan.org/search?module=Pod::XML">::XML</a> RdpO? Generate XML from POD <a href="http://search.cpan.org/search?author=MSERGEANT">MSERGEANT</a>
<a href="http://search.cpan.org/search?module=Pod::Tree">::Tree</a> RdpOp Create a static syntax tree for a POD <a href="http://search.cpan.org/search?author=SWMCD">SWMCD</a>
<a href="http://search.cpan.org/search?module=Pod::Checker">::Checker</a> RdpO? Check pod documents for syntax errors <a href="http://search.cpan.org/search?author=BRADAPP">BRADAPP</a>
<a href="http://search.cpan.org/search?module=Pod::POM">::POM</a> RdpOp Pod Object Model <a href="http://search.cpan.org/search?author=ABW">ABW</a></pre> <pre>Perl6::
<a href="http://search.cpan.org/search?module=Perl6::Variables">::Variables</a> RdpO? Perl 6 variable syntax for Perl 5 <a href="http://search.cpan.org/search?author=DCONWAY">DCONWAY</a>
<a href="http://search.cpan.org/search?module=Perl6::Interpolators">::Interpolators</a> bdpnp Use Perl 6 function-interpolation syntax <a href="http://search.cpan.org/search?author=BRENTDAX">BRENTDAX</a>
<a href="http://search.cpan.org/search?module=Perl6::Parameters">::Parameters</a> bdpnp Use Perl 6-style named parameters <a href="http://search.cpan.org/search?author=BRENTDAX">BRENTDAX</a></pre> <pre>Concurrent adpOp Concurrent and Remotable Objects in Perl <a href="http://search.cpan.org/search?author=VIPUL">VIPUL</a></pre> <pre>Acme::
<a href="http://search.cpan.org/search?module=Acme::Buffy">::Buffy</a> Rdphp An encoding scheme for Buffy fans <a href="http://search.cpan.org/search?author=LBROCARD">LBROCARD</a></pre> <pre>Acme::Morse::
<a href="http://search.cpan.org/search?module=Acme::Morse::Audible">::Audible</a> Rdpnp Audio(Morse) Programming with Perl <a href="http://search.cpan.org/search?author=ITRIVIZKI">ITRIVIZKI</a></pre> <p> </p>
<h4><a href="by-category/03_Development_Support"
id="ID3_Development" name="ID3_Development">3) Development Support</a></h4>
<pre>Name <a href="#ID1_ModuleListi">DSLIP</a> Description Info
------------ ----- -------------------------------------------- ----
<a href="http://search.cpan.org/search?module=AutoSplit">AutoSplit</a> Supf? Splits modules into files for AutoLoader <a href="../authors/00whois.html#P5P">P5P</a>
Bleach RdpO? For really clean programs <a href="http://search.cpan.org/search?author=DCONWAY">DCONWAY</a>
<a href="http://search.cpan.org/search?module=Continuus">Continuus</a> adpO? Interface to Continuus Code Management tool <a href="http://search.cpan.org/search?author=HENKE">HENKE</a>
<a href="http://search.cpan.org/search?module=Coy">Coy</a> Rdpn? Like Carp - only prettier <a href="http://search.cpan.org/search?author=DCONWAY">DCONWAY</a>
<a href="http://search.cpan.org/search?module=FindBin">FindBin</a> adpf? Locate current script bin directory <a href="../authors/00whois.html#P5P">P5P</a>
<a href="http://search.cpan.org/search?module=Include">Include</a> adpO? Parse C header files for use in XS <a href="http://search.cpan.org/search?author=GBARR">GBARR</a>
<a href="http://search.cpan.org/search?module=Make">Make</a> adpO? Makefile parsing, and 'make' replacement <a href="http://search.cpan.org/search?author=NI-S">NI-S</a>
<a href="http://search.cpan.org/search?module=Perlbug">Perlbug</a> RdpOp Database driven bug tracking system (mysql) <a href="http://search.cpan.org/search?author=RFOLEY">RFOLEY</a>
<a href="http://search.cpan.org/search?module=Rcs">Rcs</a> adcf? Alternate RCS interface (see VCS::RCS) <a href="http://search.cpan.org/search?author=CFRETER">CFRETER</a>
Smirch Rdpfa For really dirty programs <a href="http://search.cpan.org/search?author=JNAGRA">JNAGRA</a>
<a href="http://search.cpan.org/search?module=Usage">Usage</a> bnpr? Type and range checking on subroutine args <a href="http://search.cpan.org/search?author=JACKS">JACKS</a>
<a href="http://search.cpan.org/search?module=VCS">VCS</a> ampOp Generic interface to Version Control Systems <a href="http://search.cpan.org/search?author=LBROCARD">LBROCARD</a></pre> <pre><a href="http://search.cpan.org/search?module=Benchmark">Benchmark</a> Supf? Easy way to time fragments of perl code <a href="../authors/00whois.html#P5P">P5P</a>
Benchmark::
<a href="http://search.cpan.org/search?module=Benchmark::Timer">::Timer</a> RdpO? Perl code benchmarking tool <a href="http://search.cpan.org/search?author=ANDREWHO">ANDREWHO</a></pre> <pre>ExtUtils::
<a href="http://search.cpan.org/search?module=ExtUtils::DynaGlue">::DynaGlue</a> adcr? Methods for generating Perl extension files <a href="http://search.cpan.org/search?author=DOUGM">DOUGM</a>
<a href="http://search.cpan.org/search?module=ExtUtils::MakeMaker">::MakeMaker</a> SupO? Writes Makefiles for extensions <a href="../authors/00whois.html#MMML">MMML</a>
<a href="http://search.cpan.org/search?module=ExtUtils::Manifest">::Manifest</a> Supf? Utilities for managing MANIFEST files <a href="../authors/00whois.html#MMML">MMML</a>
<a href="http://search.cpan.org/search?module=ExtUtils::Embed">::Embed</a> Sdpf? Utilities for embedding Perl in C/C++ apps <a href="http://search.cpan.org/search?author=DOUGM">DOUGM</a>
<a href="http://search.cpan.org/search?module=ExtUtils::F77">::F77</a> RdpO? Facilitate use of FORTRAN from Perl/XS code <a href="http://search.cpan.org/search?author=KGB">KGB</a>
<a href="http://search.cpan.org/search?module=ExtUtils::configPL">::configPL</a> adpOp configures .PL files <a href="http://search.cpan.org/search?author=PEASE">PEASE</a></pre> <pre>Carp::
<a href="http://search.cpan.org/search?module=Carp::Assert">::Assert</a> adpf? Stating the obvious to let the computer know <a href="http://search.cpan.org/search?author=MSCHWERN">MSCHWERN</a>
::CheckArgs Rdpf? Check subroutine argument types <a href="http://search.cpan.org/search?author=GARROW">GARROW</a>
<a href="http://search.cpan.org/search?module=Carp::Datum">::Datum</a> adpfa Debugging And Tracing Ultimate Module <a href="http://search.cpan.org/search?author=SQUIRREL">SQUIRREL</a></pre> <pre>ClearCase idcf? Environment for ClearCase revision control <a href="http://search.cpan.org/search?author=BRADAPP">BRADAPP</a>
ClearCase::</pre> <pre>Conjury::
<a href="http://search.cpan.org/search?module=Conjury::C">::C</a> Rdph? Generic software construction toolset <a href="http://search.cpan.org/search?author=JWOODYATT">JWOODYATT</a>
<a href="http://search.cpan.org/search?module=Conjury::Core">::Core</a> Rdph? Generic software construction toolset <a href="http://search.cpan.org/search?author=JWOODYATT">JWOODYATT</a>
<a href="http://search.cpan.org/search?module=Conjury::Stage">::Stage</a> Rdph? Generic software construction toolset <a href="http://search.cpan.org/search?author=JWOODYATT">JWOODYATT</a></pre> <pre>Devel::
<a href="http://search.cpan.org/search?module=Devel::CallerItem">::CallerItem</a> RnpO? 'caller()' Object wrapper + useful methods <a href="http://search.cpan.org/search?author=JACKS">JACKS</a>
<a href="http://search.cpan.org/search?module=Devel::CoreStack">::CoreStack</a> adpf? generate a stack dump from a core file <a href="http://search.cpan.org/search?author=ADESC">ADESC</a>
<a href="http://search.cpan.org/search?module=Devel::Cover">::Cover</a> adchp Code coverage metrics for Perl <a href="http://search.cpan.org/search?author=PJCJ">PJCJ</a>
<a href="http://search.cpan.org/search?module=Devel::Coverage">::Coverage</a> adpf? Coverage analysis for Perl code <a href="http://search.cpan.org/search?author=RJRAY">RJRAY</a>
<a href="http://search.cpan.org/search?module=Devel::DProf">::DProf</a> Rdcf? Execution profiler <a href="http://search.cpan.org/search?author=DMR">DMR</a>
::DebugAPI bdpf? Interface to the Perl debug environment <a href="http://search.cpan.org/search?author=JHA">JHA</a>
<a href="http://search.cpan.org/search?module=Devel::DebugInit">::DebugInit</a> bdpf? Create a .gdbinit or similar file <a href="http://search.cpan.org/search?author=JASONS">JASONS</a>
<a href="http://search.cpan.org/search?module=Devel::DumpStack">::DumpStack</a> Rnpf? Dumping of the current function stack <a href="http://search.cpan.org/search?author=JACKS">JACKS</a>
<a href="http://search.cpan.org/search?module=Devel::Leak">::Leak</a> Rdcf? Find perl objects that are not reclaimed <a href="http://search.cpan.org/search?author=NI-S">NI-S</a>
<a href="http://search.cpan.org/search?module=Devel::Modlist">::Modlist</a> Rdpf? Collect module use information <a href="http://search.cpan.org/search?author=RJRAY">RJRAY</a>
<a href="http://search.cpan.org/search?module=Devel::PPPort">::PPPort</a> bdcn? Portability aid for your XS code <a href="http://search.cpan.org/search?author=PMQS">PMQS</a>
<a href="http://search.cpan.org/search?module=Devel::Peek">::Peek</a> adcf? Peek at internal representation of Perl data <a href="http://search.cpan.org/search?author=ILYAZ">ILYAZ</a>
<a href="http://search.cpan.org/search?module=Devel::RegExp">::RegExp</a> adcO? Access perl internal regex functions <a href="http://search.cpan.org/search?author=ILYAZ">ILYAZ</a>
<a href="http://search.cpan.org/search?module=Devel::SearchINC">::SearchINC</a> Rdpnp loading Perl modules from development dirs <a href="http://search.cpan.org/search?author=MARCEL">MARCEL</a>
<a href="http://search.cpan.org/search?module=Devel::SmallProf">::SmallProf</a> Rdpf? Line-by-line profiler <a href="http://search.cpan.org/search?author=ASHTED">ASHTED</a>
<a href="http://search.cpan.org/search?module=Devel::StackTrace">::StackTrace</a> RdpOp Stacktrace object w/ info form caller() <a href="http://search.cpan.org/search?author=DROLSKY">DROLSKY</a>
<a href="http://search.cpan.org/search?module=Devel::Symdump">::Symdump</a> RdpO? Perl symbol table access and dumping <a href="http://search.cpan.org/search?author=ANDK">ANDK</a>
<a href="http://search.cpan.org/search?module=Devel::TraceFuncs">::TraceFuncs</a> adpO? Trace funcs by using object destructions <a href="http://search.cpan.org/search?author=JOEHIL">JOEHIL</a>
<a href="http://search.cpan.org/search?module=Devel::TraceLoad">::TraceLoad</a> Rdpfp Traces the loading of perl source code <a href="http://search.cpan.org/search?author=PVERD">PVERD</a>