Debian Codegraph @

upstream/opensuse-tumbleweed/man1/perlfaq2.1

raw
1 .\" -*- mode: troff; coding: utf-8 -*-
2 .\" Automatically generated by Pod::Man v6.0.2 (Pod::Simple 3.45)
3 .\"
4 .\" Standard preamble:
5 .\" ========================================================================
6 .de Sp \" Vertical space (when we can't use .PP)
7 .if t .sp .5v
8 .if n .sp
9 ..
10 .de Vb \" Begin verbatim text
11 .ft CW
12 .nf
13 .ne \\$1
14 ..
15 .de Ve \" End verbatim text
16 .ft R
17 .fi
18 ..
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
20 .ie n \{\
21 . ds C` ""
22 . ds C' ""
23 'br\}
24 .el\{\
25 . ds C`
26 . ds C'
27 'br\}
28 .\"
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
30 .ie \n(.g .ds Aq \(aq
31 .el .ds Aq '
32 .\"
33 .\" If the F register is >0, we'll generate index entries on stderr for
34 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
37 .\"
38 .\" Avoid warning from groff about undefined register 'F'.
39 .de IX
40 ..
41 .nr rF 0
42 .if \n(.g .if rF .nr rF 1
43 .if (\n(rF:(\n(.g==0)) \{\
44 . if \nF \{\
45 . de IX
46 . tm Index:\\$1\t\\n%\t"\\$2"
47 ..
48 . if !\nF==2 \{\
49 . nr % 0
50 . nr F 2
51 . \}
52 . \}
53 .\}
54 .rr rF
55 .\"
56 .\" Required to disable full justification in groff 1.23.0.
57 .if n .ds AD l
58 .\" ========================================================================
59 .\"
60 .IX Title "PERLFAQ2 1"
61 .TH PERLFAQ2 1 2026-03-09 "perl v5.42.1" "Perl Programmers Reference Guide"
62 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
63 .\" way too many mistakes in technical documents.
64 .if n .ad l
65 .nh
66 .SH NAME
67 perlfaq2 \- Obtaining and Learning about Perl
68 .SH VERSION
69 .IX Header "VERSION"
70 version 5.20250619
71 .SH DESCRIPTION
72 .IX Header "DESCRIPTION"
73 This section of the FAQ answers questions about where to find
74 source and documentation for Perl, support, and
75 related matters.
76 .SS "What machines support Perl? Where do I get it?"
77 .IX Subsection "What machines support Perl? Where do I get it?"
78 The standard release of Perl (the one maintained by the Perl
79 development team) is distributed only in source code form. You
80 can find the latest releases at <http://www.cpan.org/src/>.
81 .PP
82 Perl builds and runs on a bewildering number of platforms. Virtually
83 all known and current Unix derivatives are supported (perl\*(Aqs native
84 platform), as are other systems like VMS, DOS, OS/2, Windows,
85 QNX, BeOS, OS X, MPE/iX and the Amiga.
86 .PP
87 Binary distributions for some proprietary platforms can be found in the
88 <http://www.cpan.org/ports/> directory. Because these are not part of
89 the standard distribution, they may and in fact do differ from the
90 base perl port in a variety of ways. You\*(Aqll have to check their
91 respective release notes to see just what the differences are. These
92 differences can be either positive (e.g. extensions for the features
93 of the particular platform that are not supported in the source
94 release of perl) or negative (e.g. might be based upon a less current
95 source release of perl).
96 .SS "How can I get a binary version of Perl?"
97 .IX Subsection "How can I get a binary version of Perl?"
98 See CPAN Ports <http://www.cpan.org/ports/>
99 .SS "I don\*(Aqt have a C compiler. How can I build my own Perl interpreter?"
100 .IX Subsection "I don't have a C compiler. How can I build my own Perl interpreter?"
101 For Windows, use a binary version of Perl,
102 Strawberry Perl <http://strawberryperl.com/> and
103 ActivePerl <http://www.activestate.com/activeperl> come with a
104 bundled C compiler.
105 .PP
106 Otherwise if you really do want to build Perl, you need to get a
107 binary version of \f(CW\*(C`gcc\*(C'\fR for your system first. Use a search
108 engine to find out how to do this for your operating system.
109 .SS "I copied the Perl binary from one machine to another, but scripts don\*(Aqt work."
110 .IX Subsection "I copied the Perl binary from one machine to another, but scripts don't work."
111 That\*(Aqs probably because you forgot libraries, or library paths differ.
112 You really should build the whole distribution on the machine it will
113 eventually live on, and then type \f(CW\*(C`make install\*(C'\fR. Most other
114 approaches are doomed to failure.
115 .PP
116 One simple way to check that things are in the right place is to print out
117 the hard\-coded \f(CW@INC\fR that perl looks through for libraries:
118 .PP
119 .Vb 1
120 \& % perl \-le \*(Aqprint for @INC\*(Aq
121 .Ve
122 .PP
123 If this command lists any paths that don\*(Aqt exist on your system, then you
124 may need to move the appropriate libraries to these locations, or create
125 symbolic links, aliases, or shortcuts appropriately. \f(CW@INC\fR is also printed as
126 part of the output of
127 .PP
128 .Vb 1
129 \& % perl \-V
130 .Ve
131 .PP
132 You might also want to check out
133 "How do I keep my own module/library directory?" in perlfaq8.
134 .SS "I grabbed the sources and tried to compile but gdbm/dynamic loading/malloc/linking/... failed. How do I make it work?"
135 .IX Subsection "I grabbed the sources and tried to compile but gdbm/dynamic loading/malloc/linking/... failed. How do I make it work?"
136 Read the \fIINSTALL\fR file, which is part of the source distribution.
137 It describes in detail how to cope with most idiosyncrasies that the
138 \&\f(CW\*(C`Configure\*(C'\fR script can\*(Aqt work around for any given system or
139 architecture.
140 .SS "What modules and extensions are available for Perl? What is CPAN?"
141 .IX Subsection "What modules and extensions are available for Perl? What is CPAN?"
142 CPAN stands for Comprehensive Perl Archive Network, a multi\-gigabyte
143 archive replicated on hundreds of machines all over the world. CPAN
144 contains tens of thousands of modules and extensions, source code
145 and documentation, designed for \fIeverything\fR from commercial
146 database interfaces to keyboard/screen control and running large web sites.
147 .PP
148 You can search CPAN on <http://metacpan.org>.
149 .PP
150 The master web site for CPAN is <http://www.cpan.org/>,
151 <http://www.cpan.org/SITES.html> lists all mirrors.
152 .PP
153 See the CPAN FAQ at <http://www.cpan.org/misc/cpan\-faq.html> for answers
154 to the most frequently asked questions about CPAN.
155 .PP
156 The Task::Kensho module has a list of recommended modules which
157 you should review as a good starting point.
158 .SS "Where can I get information on Perl?"
159 .IX Subsection "Where can I get information on Perl?"
160 .IP \(bu 4
161 <http://www.perl.org/>
162 .IP \(bu 4
163 <http://perldoc.perl.org/>
164 .IP \(bu 4
165 <http://learn.perl.org/>
166 .PP
167 The complete Perl documentation is available with the Perl distribution.
168 If you have Perl installed locally, you probably have the documentation
169 installed as well: type \f(CW\*(C`perldoc perl\*(C'\fR in a terminal or
170 view online <http://perldoc.perl.org/perl.html>.
171 .PP
172 (Some operating system distributions may ship the documentation in a different
173 package; for instance, on Debian, you need to install the \f(CW\*(C`perl\-doc\*(C'\fR package.)
174 .PP
175 Many good books have been written about Perl\-\-see the "Perl Books" section
176 for more details.
177 .SS "What is perl.com? Perl Mongers? pm.org? perl.org? cpan.org?"
178 .IX Subsection "What is perl.com? Perl Mongers? pm.org? perl.org? cpan.org?"
179 Perl.com <http://www.perl.com/> used to be part of the O\*(AqReilly
180 Network, a subsidiary of O\*(AqReilly Media. Although it retains most of
181 the original content from its O\*(AqReilly Network, it is now hosted by
182 The Perl Foundation <http://www.perlfoundation.org/>.
183 .PP
184 The Perl Foundation is an advocacy organization for the Perl language
185 which maintains the web site <http://www.perl.org/> as a general
186 advocacy site for the Perl language. It uses the domain to provide
187 general support services to the Perl community, including the hosting
188 of mailing lists, web sites, and other services. There are also many
189 other sub\-domains for special topics like learning Perl and jobs in Perl,
190 such as:
191 .IP \(bu 4
192 <http://www.perl.org/>
193 .IP \(bu 4
194 <http://learn.perl.org/>
195 .IP \(bu 4
196 <http://jobs.perl.org/>
197 .IP \(bu 4
198 <http://lists.perl.org/>
199 .PP
200 Perl Mongers <http://www.pm.org/> uses the pm.org domain for services
201 related to local Perl user groups, including the hosting of mailing lists
202 and web sites. See the Perl Mongers web site <http://www.pm.org/> for more
203 information about joining, starting, or requesting services for a
204 Perl user group.
205 .PP
206 CPAN, or the Comprehensive Perl Archive Network <http://www.cpan.org/>,
207 is a replicated, worldwide repository of Perl software.
208 See What is CPAN?.
209 .SS "Where can I post questions?"
210 .IX Subsection "Where can I post questions?"
211 There are many Perl mailing lists <https://lists.perl.org> for various
212 topics, specifically the beginners list <http://lists.perl.org/list/beginners.html>
213 may be of use.
214 .PP
215 Other places to ask questions are on the
216 PerlMonks site <http://www.perlmonks.org/> or
217 stackoverflow <http://stackoverflow.com/questions/tagged/perl>.
218 .SS "Perl Books"
219 .IX Subsection "Perl Books"
220 There are many good books on Perl <http://www.perl.org/books/library.html>.
221 .SS "Which magazines have Perl content?"
222 .IX Subsection "Which magazines have Perl content?"
223 There are no current magazines that focus on Perl, although you sometimes
224 will find Perl content in more general interest programming titles.
225 .PP
226 In the distant past, there have been a few Perl magazines. The first was \fIThe Perl
227 Journal\fR, published by Jon Orwant. After that, there was \fIThe Perl Review\fR,
228 published by brian d foy, and \fR\f(CI$foo\fR\fI Magazin\fR, published by Renée Bäcker
229 (<http://www.foo\-magazin.de>).
230 .PP
231 The closest you might find today is Perl Weekly, (<https://perlweekly.com>),
232 an online newsletter with a magazine\-like format.
233 .SS "Which Perl blogs should I read?"
234 .IX Subsection "Which Perl blogs should I read?"
235 Perl News <http://perlnews.org/> covers some of the major events in the Perl
236 world, Perl Weekly <http://perlweekly.com/> is a weekly e\-mail
237 (and RSS feed) of hand\-picked Perl articles.
238 .PP
239 <http://blogs.perl.org/> hosts many Perl blogs, there are also
240 several blog aggregators: Perlsphere <http://perlsphere.net/> and
241 IronMan <http://ironman.enlightenedperl.org/> are two of them.
242 .SS "What mailing lists are there for Perl?"
243 .IX Subsection "What mailing lists are there for Perl?"
244 A comprehensive list of Perl\-related mailing lists can be found at
245 <http://lists.perl.org/>
246 .SS "Where can I buy a commercial version of Perl?"
247 .IX Subsection "Where can I buy a commercial version of Perl?"
248 Perl already \fIis\fR commercial software: it has a license
249 that you can grab and carefully read to your manager. It is distributed
250 in releases and comes in well\-defined packages. There is a very large
251 and supportive user community and an extensive literature.
252 .PP
253 If you still need commercial support
254 ActiveState <http://www.activestate.com/activeperl> offers
255 this.
256 .SS "Where do I send bug reports?"
257 .IX Subsection "Where do I send bug reports?"
258 (contributed by brian d foy)
259 .PP
260 First, ensure that you\*(Aqve found an actual bug. Second, ensure you\*(Aqve
261 found an actual bug.
262 .PP
263 If you\*(Aqve found a bug with the perl interpreter or one of the modules
264 in the standard library (those that come with Perl), submit a
265 bug report to the GitHub issue tracker at
266 <https://github.com/Perl/perl5/issues>.
267 .PP
268 To determine if a module came with your version of Perl, you can
269 install and use Module::CoreList. It knows the modules (with their
270 versions) included with each release of Perl:
271 .PP
272 .Vb 3
273 \& $ corelist File::Copy
274 \& Data for 2023\-07\-02
275 \& File::Copy was first released with perl 5.002
276 \&
277 \& $ corelist Business::ISBN
278 \& Data for 2023\-07\-02
279 \& Business::ISBN was not in CORE (or so I think)
280 .Ve
281 .PP
282 If the module does not come with Perl, report its issues
283 using the tool that the particular module author decided to use, such as
284 a GitHub or Google Code. The quickest way may be to check the MetaCPAN
285 page for the module (for example,
286 <https://metacpan.org/pod/Business::ISBN>), which shows the denoted
287 bugtracker in the left sidebar as the "Issues" link.
288 .PP
289 Also check the module\*(Aqs documentation, \fIREADME\fR, the build files
290 (\fIMakefile.PL\fR or \f(CW\*(C`Build.PL\*(C'\fR), or \fIMETA.{json,yml}\fR files. Although
291 many module authors follow the same pattern, some have their own way.
292 Use the directions you find.
293 .PP
294 Sometimes the module author does not declare a bugtracker. For a long
295 time, everyone assumed that the CPAN Request Tracker
296 (<https://rt.cpan.org>) was the bugtracker since every distribution had
297 an RT queue generated automatically. In some cases, the author might
298 use CPAN RT. They also might have not declared a different
299 bugtracker but don\*(Aqt use CPAN RT.
300 .PP
301 Submit bugs to RT either through its web interface,
302 <https://rt.cpan.org>, or by email. Send email to \fIbug\-<distribution\-name>@rt.cpan.org\fR. For example, if you
303 wanted to report a bug in the example module \f(CW\*(C`Foo::Bar\*(C'\fR, you could send
304 a message to \fIbug\-Foo\[email protected]\fR.
305 .SH "AUTHOR AND COPYRIGHT"
306 .IX Header "AUTHOR AND COPYRIGHT"
307 Copyright (c) 1997\-2010 Tom Christiansen, Nathan Torkington, and
308 other authors as noted. All rights reserved.
309 .PP
310 This documentation is free; you can redistribute it and/or modify it
311 under the same terms as Perl itself.
312 .PP
313 Irrespective of its distribution, all code examples here are in the public
314 domain. You are permitted and encouraged to use this code and any
315 derivatives thereof in your own programs for fun or for profit as you
316 see fit. A simple comment in the code giving credit to the FAQ would
317 be courteous but is not required.