Commit | Line | Data |
---|---|---|
a0d0e21e | 1 | =head1 NAME |
d74e8afc | 2 | X<function> |
a0d0e21e LW |
3 | |
4 | perlfunc - Perl builtin functions | |
5 | ||
6 | =head1 DESCRIPTION | |
7 | ||
8 | The functions in this section can serve as terms in an expression. | |
9 | They fall into two major categories: list operators and named unary | |
10 | operators. These differ in their precedence relationship with a | |
11 | following comma. (See the precedence table in L<perlop>.) List | |
12 | operators take more than one argument, while unary operators can never | |
13 | take more than one argument. Thus, a comma terminates the argument of | |
14 | a unary operator, but merely separates the arguments of a list | |
8f1da26d | 15 | operator. A unary operator generally provides scalar context to its |
2b5ab1e7 | 16 | argument, while a list operator may provide either scalar or list |
3b10bc60 | 17 | contexts for its arguments. If it does both, scalar arguments |
18 | come first and list argument follow, and there can only ever | |
19 | be one such list argument. For instance, splice() has three scalar | |
2b5ab1e7 TC |
20 | arguments followed by a list, whereas gethostbyname() has four scalar |
21 | arguments. | |
a0d0e21e LW |
22 | |
23 | In the syntax descriptions that follow, list operators that expect a | |
3b10bc60 | 24 | list (and provide list context for elements of the list) are shown |
a0d0e21e LW |
25 | with LIST as an argument. Such a list may consist of any combination |
26 | of scalar arguments or list values; the list values will be included | |
27 | in the list as if each individual element were interpolated at that | |
28 | point in the list, forming a longer single-dimensional list value. | |
8bdbc703 | 29 | Commas should separate literal elements of the LIST. |
a0d0e21e LW |
30 | |
31 | Any function in the list below may be used either with or without | |
32 | parentheses around its arguments. (The syntax descriptions omit the | |
3b10bc60 | 33 | parentheses.) If you use parentheses, the simple but occasionally |
34 | surprising rule is this: It I<looks> like a function, therefore it I<is> a | |
a0d0e21e | 35 | function, and precedence doesn't matter. Otherwise it's a list |
3b10bc60 | 36 | operator or unary operator, and precedence does matter. Whitespace |
37 | between the function and left parenthesis doesn't count, so sometimes | |
38 | you need to be careful: | |
a0d0e21e | 39 | |
5ed4f2ec | 40 | print 1+2+4; # Prints 7. |
41 | print(1+2) + 4; # Prints 3. | |
42 | print (1+2)+4; # Also prints 3! | |
43 | print +(1+2)+4; # Prints 7. | |
44 | print ((1+2)+4); # Prints 7. | |
a0d0e21e LW |
45 | |
46 | If you run Perl with the B<-w> switch it can warn you about this. For | |
47 | example, the third line above produces: | |
48 | ||
49 | print (...) interpreted as function at - line 1. | |
50 | Useless use of integer addition in void context at - line 1. | |
51 | ||
2b5ab1e7 TC |
52 | A few functions take no arguments at all, and therefore work as neither |
53 | unary nor list operators. These include such functions as C<time> | |
54 | and C<endpwent>. For example, C<time+86_400> always means | |
55 | C<time() + 86_400>. | |
56 | ||
a0d0e21e | 57 | For functions that can be used in either a scalar or list context, |
8f1da26d TC |
58 | nonabortive failure is generally indicated in scalar context by |
59 | returning the undefined value, and in list context by returning the | |
3b10bc60 | 60 | empty list. |
a0d0e21e | 61 | |
5a964f20 TC |
62 | Remember the following important rule: There is B<no rule> that relates |
63 | the behavior of an expression in list context to its behavior in scalar | |
64 | context, or vice versa. It might do two totally different things. | |
80d38338 | 65 | Each operator and function decides which sort of value would be most |
2b5ab1e7 | 66 | appropriate to return in scalar context. Some operators return the |
5a964f20 | 67 | length of the list that would have been returned in list context. Some |
a0d0e21e LW |
68 | operators return the first value in the list. Some operators return the |
69 | last value in the list. Some operators return a count of successful | |
70 | operations. In general, they do what you want, unless you want | |
71 | consistency. | |
d74e8afc | 72 | X<context> |
a0d0e21e | 73 | |
d1be9408 | 74 | A named array in scalar context is quite different from what would at |
5a964f20 TC |
75 | first glance appear to be a list in scalar context. You can't get a list |
76 | like C<(1,2,3)> into being in scalar context, because the compiler knows | |
77 | the context at compile time. It would generate the scalar comma operator | |
78 | there, not the list construction version of the comma. That means it | |
79 | was never a list to start with. | |
80 | ||
3b10bc60 | 81 | In general, functions in Perl that serve as wrappers for system calls ("syscalls") |
5dac7880 | 82 | of the same name (like chown(2), fork(2), closedir(2), etc.) return |
5a964f20 TC |
83 | true when they succeed and C<undef> otherwise, as is usually mentioned |
84 | in the descriptions below. This is different from the C interfaces, | |
5dac7880 | 85 | which return C<-1> on failure. Exceptions to this rule include C<wait>, |
19799a22 | 86 | C<waitpid>, and C<syscall>. System calls also set the special C<$!> |
5a964f20 TC |
87 | variable on failure. Other functions do not, except accidentally. |
88 | ||
88e1f1a2 JV |
89 | Extension modules can also hook into the Perl parser to define new |
90 | kinds of keyword-headed expression. These may look like functions, but | |
91 | may also look completely different. The syntax following the keyword | |
92 | is defined entirely by the extension. If you are an implementor, see | |
93 | L<perlapi/PL_keyword_plugin> for the mechanism. If you are using such | |
94 | a module, see the module's documentation for details of the syntax that | |
95 | it defines. | |
96 | ||
cb1a09d0 | 97 | =head2 Perl Functions by Category |
d74e8afc | 98 | X<function> |
cb1a09d0 AD |
99 | |
100 | Here are Perl's functions (including things that look like | |
5a964f20 | 101 | functions, like some keywords and named operators) |
cb1a09d0 AD |
102 | arranged by category. Some functions appear in more |
103 | than one place. | |
104 | ||
13a2d996 | 105 | =over 4 |
cb1a09d0 AD |
106 | |
107 | =item Functions for SCALARs or strings | |
d74e8afc | 108 | X<scalar> X<string> X<character> |
cb1a09d0 | 109 | |
c17cdb72 NC |
110 | =for Pod::Functions =String |
111 | ||
628253b8 BF |
112 | C<chomp>, C<chop>, C<chr>, C<crypt>, C<fc>, C<hex>, C<index>, C<lc>, |
113 | C<lcfirst>, C<length>, C<oct>, C<ord>, C<pack>, C<q//>, C<qq//>, C<reverse>, | |
945c54fd | 114 | C<rindex>, C<sprintf>, C<substr>, C<tr///>, C<uc>, C<ucfirst>, C<y///> |
cb1a09d0 | 115 | |
4fe70ef9 NC |
116 | C<fc> is available only if the C<"fc"> feature is enabled or if it is |
117 | prefixed with C<CORE::>. The C<"fc"> feature is enabled automatically | |
3dd9a840 | 118 | with a C<use v5.16> (or higher) declaration in the current scope. |
4fe70ef9 NC |
119 | |
120 | ||
cb1a09d0 | 121 | =item Regular expressions and pattern matching |
d74e8afc | 122 | X<regular expression> X<regex> X<regexp> |
cb1a09d0 | 123 | |
c17cdb72 NC |
124 | =for Pod::Functions =Regexp |
125 | ||
f5fa2679 | 126 | C<m//>, C<pos>, C<qr//>, C<quotemeta>, C<s///>, C<split>, C<study> |
cb1a09d0 AD |
127 | |
128 | =item Numeric functions | |
d74e8afc | 129 | X<numeric> X<number> X<trigonometric> X<trigonometry> |
cb1a09d0 | 130 | |
c17cdb72 NC |
131 | =for Pod::Functions =Math |
132 | ||
22fae026 TM |
133 | C<abs>, C<atan2>, C<cos>, C<exp>, C<hex>, C<int>, C<log>, C<oct>, C<rand>, |
134 | C<sin>, C<sqrt>, C<srand> | |
cb1a09d0 AD |
135 | |
136 | =item Functions for real @ARRAYs | |
d74e8afc | 137 | X<array> |
cb1a09d0 | 138 | |
c17cdb72 NC |
139 | =for Pod::Functions =ARRAY |
140 | ||
a5ce339c | 141 | C<each>, C<keys>, C<pop>, C<push>, C<shift>, C<splice>, C<unshift>, C<values> |
cb1a09d0 AD |
142 | |
143 | =item Functions for list data | |
d74e8afc | 144 | X<list> |
cb1a09d0 | 145 | |
c17cdb72 NC |
146 | =for Pod::Functions =LIST |
147 | ||
1dc8ecb8 | 148 | C<grep>, C<join>, C<map>, C<qw//>, C<reverse>, C<sort>, C<unpack> |
cb1a09d0 AD |
149 | |
150 | =item Functions for real %HASHes | |
d74e8afc | 151 | X<hash> |
cb1a09d0 | 152 | |
c17cdb72 NC |
153 | =for Pod::Functions =HASH |
154 | ||
22fae026 | 155 | C<delete>, C<each>, C<exists>, C<keys>, C<values> |
cb1a09d0 AD |
156 | |
157 | =item Input and output functions | |
d74e8afc | 158 | X<I/O> X<input> X<output> X<dbm> |
cb1a09d0 | 159 | |
c17cdb72 NC |
160 | =for Pod::Functions =I/O |
161 | ||
22fae026 TM |
162 | C<binmode>, C<close>, C<closedir>, C<dbmclose>, C<dbmopen>, C<die>, C<eof>, |
163 | C<fileno>, C<flock>, C<format>, C<getc>, C<print>, C<printf>, C<read>, | |
7c919445 NC |
164 | C<readdir>, C<readline> C<rewinddir>, C<say>, C<seek>, C<seekdir>, C<select>, |
165 | C<syscall>, C<sysread>, C<sysseek>, C<syswrite>, C<tell>, C<telldir>, | |
166 | C<truncate>, C<warn>, C<write> | |
cb1a09d0 | 167 | |
4fe70ef9 NC |
168 | C<say> is available only if the C<"say"> feature is enabled or if it is |
169 | prefixed with C<CORE::>. The C<"say"> feature is enabled automatically | |
170 | with a C<use v5.10> (or higher) declaration in the current scope. | |
171 | ||
5dac7880 | 172 | =item Functions for fixed-length data or records |
cb1a09d0 | 173 | |
c17cdb72 NC |
174 | =for Pod::Functions =Binary |
175 | ||
7c919445 NC |
176 | C<pack>, C<read>, C<syscall>, C<sysread>, C<sysseek>, C<syswrite>, C<unpack>, |
177 | C<vec> | |
cb1a09d0 AD |
178 | |
179 | =item Functions for filehandles, files, or directories | |
d74e8afc | 180 | X<file> X<filehandle> X<directory> X<pipe> X<link> X<symlink> |
cb1a09d0 | 181 | |
c17cdb72 NC |
182 | =for Pod::Functions =File |
183 | ||
22fae026 | 184 | C<-I<X>>, C<chdir>, C<chmod>, C<chown>, C<chroot>, C<fcntl>, C<glob>, |
5ff3f7a4 | 185 | C<ioctl>, C<link>, C<lstat>, C<mkdir>, C<open>, C<opendir>, |
1e278fd9 JH |
186 | C<readlink>, C<rename>, C<rmdir>, C<stat>, C<symlink>, C<sysopen>, |
187 | C<umask>, C<unlink>, C<utime> | |
cb1a09d0 | 188 | |
cf264981 | 189 | =item Keywords related to the control flow of your Perl program |
d74e8afc | 190 | X<control flow> |
cb1a09d0 | 191 | |
c17cdb72 NC |
192 | =for Pod::Functions =Flow |
193 | ||
dba7b065 | 194 | C<break>, C<caller>, C<continue>, C<die>, C<do>, |
7289c5e6 | 195 | C<dump>, C<eval>, C<evalbytes> C<exit>, |
cfa52385 | 196 | C<__FILE__>, C<goto>, C<last>, C<__LINE__>, C<next>, C<__PACKAGE__>, |
17d15541 | 197 | C<redo>, C<return>, C<sub>, C<__SUB__>, C<wantarray> |
84ed0108 | 198 | |
dba7b065 | 199 | C<break> is available only if you enable the experimental C<"switch"> |
7161e5c2 | 200 | feature or use the C<CORE::> prefix. The C<"switch"> feature also enables |
dba7b065 | 201 | the C<default>, C<given> and C<when> statements, which are documented in |
7161e5c2 | 202 | L<perlsyn/"Switch Statements">. The C<"switch"> feature is enabled |
dba7b065 | 203 | automatically with a C<use v5.10> (or higher) declaration in the current |
7161e5c2 | 204 | scope. In Perl v5.14 and earlier, C<continue> required the C<"switch"> |
dba7b065 NC |
205 | feature, like the other keywords. |
206 | ||
e3f68f70 | 207 | C<evalbytes> is only available with the C<"evalbytes"> feature (see |
4fe70ef9 | 208 | L<feature>) or if prefixed with C<CORE::>. C<__SUB__> is only available |
7161e5c2 | 209 | with the C<"current_sub"> feature or if prefixed with C<CORE::>. Both |
4fe70ef9 NC |
210 | the C<"evalbytes"> and C<"current_sub"> features are enabled automatically |
211 | with a C<use v5.16> (or higher) declaration in the current scope. | |
cb1a09d0 | 212 | |
54310121 | 213 | =item Keywords related to scoping |
cb1a09d0 | 214 | |
c17cdb72 NC |
215 | =for Pod::Functions =Namespace |
216 | ||
8f1da26d | 217 | C<caller>, C<import>, C<local>, C<my>, C<our>, C<package>, C<state>, C<use> |
36fb85f3 | 218 | |
4fe70ef9 NC |
219 | C<state> is available only if the C<"state"> feature is enabled or if it is |
220 | prefixed with C<CORE::>. The C<"state"> feature is enabled automatically | |
221 | with a C<use v5.10> (or higher) declaration in the current scope. | |
cb1a09d0 AD |
222 | |
223 | =item Miscellaneous functions | |
224 | ||
c17cdb72 NC |
225 | =for Pod::Functions =Misc |
226 | ||
17d15541 | 227 | C<defined>, C<formline>, C<lock>, C<prototype>, C<reset>, C<scalar>, C<undef> |
cb1a09d0 AD |
228 | |
229 | =item Functions for processes and process groups | |
d74e8afc | 230 | X<process> X<pid> X<process id> |
cb1a09d0 | 231 | |
c17cdb72 NC |
232 | =for Pod::Functions =Process |
233 | ||
22fae026 | 234 | C<alarm>, C<exec>, C<fork>, C<getpgrp>, C<getppid>, C<getpriority>, C<kill>, |
4319b00c FC |
235 | C<pipe>, C<qx//>, C<readpipe>, C<setpgrp>, |
236 | C<setpriority>, C<sleep>, C<system>, | |
22fae026 | 237 | C<times>, C<wait>, C<waitpid> |
cb1a09d0 | 238 | |
3b10bc60 | 239 | =item Keywords related to Perl modules |
d74e8afc | 240 | X<module> |
cb1a09d0 | 241 | |
c17cdb72 NC |
242 | =for Pod::Functions =Modules |
243 | ||
22fae026 | 244 | C<do>, C<import>, C<no>, C<package>, C<require>, C<use> |
cb1a09d0 | 245 | |
353c6505 | 246 | =item Keywords related to classes and object-orientation |
d74e8afc | 247 | X<object> X<class> X<package> |
cb1a09d0 | 248 | |
c17cdb72 NC |
249 | =for Pod::Functions =Objects |
250 | ||
22fae026 TM |
251 | C<bless>, C<dbmclose>, C<dbmopen>, C<package>, C<ref>, C<tie>, C<tied>, |
252 | C<untie>, C<use> | |
cb1a09d0 AD |
253 | |
254 | =item Low-level socket functions | |
d74e8afc | 255 | X<socket> X<sock> |
cb1a09d0 | 256 | |
c17cdb72 NC |
257 | =for Pod::Functions =Socket |
258 | ||
22fae026 TM |
259 | C<accept>, C<bind>, C<connect>, C<getpeername>, C<getsockname>, |
260 | C<getsockopt>, C<listen>, C<recv>, C<send>, C<setsockopt>, C<shutdown>, | |
737dd4b4 | 261 | C<socket>, C<socketpair> |
cb1a09d0 AD |
262 | |
263 | =item System V interprocess communication functions | |
d74e8afc | 264 | X<IPC> X<System V> X<semaphore> X<shared memory> X<memory> X<message> |
cb1a09d0 | 265 | |
c17cdb72 NC |
266 | =for Pod::Functions =SysV |
267 | ||
22fae026 TM |
268 | C<msgctl>, C<msgget>, C<msgrcv>, C<msgsnd>, C<semctl>, C<semget>, C<semop>, |
269 | C<shmctl>, C<shmget>, C<shmread>, C<shmwrite> | |
cb1a09d0 AD |
270 | |
271 | =item Fetching user and group info | |
d74e8afc | 272 | X<user> X<group> X<password> X<uid> X<gid> X<passwd> X</etc/passwd> |
cb1a09d0 | 273 | |
c17cdb72 NC |
274 | =for Pod::Functions =User |
275 | ||
22fae026 TM |
276 | C<endgrent>, C<endhostent>, C<endnetent>, C<endpwent>, C<getgrent>, |
277 | C<getgrgid>, C<getgrnam>, C<getlogin>, C<getpwent>, C<getpwnam>, | |
278 | C<getpwuid>, C<setgrent>, C<setpwent> | |
cb1a09d0 AD |
279 | |
280 | =item Fetching network info | |
d74e8afc | 281 | X<network> X<protocol> X<host> X<hostname> X<IP> X<address> X<service> |
cb1a09d0 | 282 | |
c17cdb72 NC |
283 | =for Pod::Functions =Network |
284 | ||
22fae026 TM |
285 | C<endprotoent>, C<endservent>, C<gethostbyaddr>, C<gethostbyname>, |
286 | C<gethostent>, C<getnetbyaddr>, C<getnetbyname>, C<getnetent>, | |
287 | C<getprotobyname>, C<getprotobynumber>, C<getprotoent>, | |
288 | C<getservbyname>, C<getservbyport>, C<getservent>, C<sethostent>, | |
289 | C<setnetent>, C<setprotoent>, C<setservent> | |
cb1a09d0 AD |
290 | |
291 | =item Time-related functions | |
d74e8afc | 292 | X<time> X<date> |
cb1a09d0 | 293 | |
c17cdb72 NC |
294 | =for Pod::Functions =Time |
295 | ||
22fae026 | 296 | C<gmtime>, C<localtime>, C<time>, C<times> |
cb1a09d0 | 297 | |
8f0d6a61 RS |
298 | =item Non-function keywords |
299 | ||
c17cdb72 NC |
300 | =for Pod::Functions =!Non-functions |
301 | ||
f5fa2679 | 302 | C<and>, C<AUTOLOAD>, C<BEGIN>, C<CHECK>, C<cmp>, C<CORE>, C<__DATA__>, |
dba7b065 NC |
303 | C<default>, C<DESTROY>, C<else>, C<elseif>, C<elsif>, C<END>, C<__END__>, |
304 | C<eq>, C<for>, C<foreach>, C<ge>, C<given>, C<gt>, C<if>, C<INIT>, C<le>, | |
305 | C<lt>, C<ne>, C<not>, C<or>, C<UNITCHECK>, C<unless>, C<until>, C<when>, | |
306 | C<while>, C<x>, C<xor> | |
8f0d6a61 | 307 | |
cb1a09d0 AD |
308 | =back |
309 | ||
60f9f73c | 310 | =head2 Portability |
d74e8afc | 311 | X<portability> X<Unix> X<portable> |
60f9f73c | 312 | |
2b5ab1e7 TC |
313 | Perl was born in Unix and can therefore access all common Unix |
314 | system calls. In non-Unix environments, the functionality of some | |
8f1da26d | 315 | Unix system calls may not be available or details of the available |
2b5ab1e7 | 316 | functionality may differ slightly. The Perl functions affected |
60f9f73c JH |
317 | by this are: |
318 | ||
319 | C<-X>, C<binmode>, C<chmod>, C<chown>, C<chroot>, C<crypt>, | |
320 | C<dbmclose>, C<dbmopen>, C<dump>, C<endgrent>, C<endhostent>, | |
321 | C<endnetent>, C<endprotoent>, C<endpwent>, C<endservent>, C<exec>, | |
ef5a6dd7 JH |
322 | C<fcntl>, C<flock>, C<fork>, C<getgrent>, C<getgrgid>, C<gethostbyname>, |
323 | C<gethostent>, C<getlogin>, C<getnetbyaddr>, C<getnetbyname>, C<getnetent>, | |
54d7b083 | 324 | C<getppid>, C<getpgrp>, C<getpriority>, C<getprotobynumber>, |
60f9f73c JH |
325 | C<getprotoent>, C<getpwent>, C<getpwnam>, C<getpwuid>, |
326 | C<getservbyport>, C<getservent>, C<getsockopt>, C<glob>, C<ioctl>, | |
327 | C<kill>, C<link>, C<lstat>, C<msgctl>, C<msgget>, C<msgrcv>, | |
2b5ab1e7 | 328 | C<msgsnd>, C<open>, C<pipe>, C<readlink>, C<rename>, C<select>, C<semctl>, |
60f9f73c JH |
329 | C<semget>, C<semop>, C<setgrent>, C<sethostent>, C<setnetent>, |
330 | C<setpgrp>, C<setpriority>, C<setprotoent>, C<setpwent>, | |
331 | C<setservent>, C<setsockopt>, C<shmctl>, C<shmget>, C<shmread>, | |
737dd4b4 | 332 | C<shmwrite>, C<socket>, C<socketpair>, |
80cbd5ad JH |
333 | C<stat>, C<symlink>, C<syscall>, C<sysopen>, C<system>, |
334 | C<times>, C<truncate>, C<umask>, C<unlink>, | |
2b5ab1e7 | 335 | C<utime>, C<wait>, C<waitpid> |
60f9f73c JH |
336 | |
337 | For more information about the portability of these functions, see | |
338 | L<perlport> and other available platform-specific documentation. | |
339 | ||
cb1a09d0 AD |
340 | =head2 Alphabetical Listing of Perl Functions |
341 | ||
3b10bc60 | 342 | =over |
a0d0e21e | 343 | |
5b3c99c0 | 344 | =item -X FILEHANDLE |
d74e8afc ITB |
345 | X<-r>X<-w>X<-x>X<-o>X<-R>X<-W>X<-X>X<-O>X<-e>X<-z>X<-s>X<-f>X<-d>X<-l>X<-p> |
346 | X<-S>X<-b>X<-c>X<-t>X<-u>X<-g>X<-k>X<-T>X<-B>X<-M>X<-A>X<-C> | |
a0d0e21e | 347 | |
5b3c99c0 | 348 | =item -X EXPR |
a0d0e21e | 349 | |
5228a96c SP |
350 | =item -X DIRHANDLE |
351 | ||
5b3c99c0 | 352 | =item -X |
a0d0e21e | 353 | |
c17cdb72 NC |
354 | =for Pod::Functions a file test (-r, -x, etc) |
355 | ||
a0d0e21e | 356 | A file test, where X is one of the letters listed below. This unary |
5228a96c SP |
357 | operator takes one argument, either a filename, a filehandle, or a dirhandle, |
358 | and tests the associated file to see if something is true about it. If the | |
7660c0ab | 359 | argument is omitted, tests C<$_>, except for C<-t>, which tests STDIN. |
139c8d14 DG |
360 | Unless otherwise documented, it returns C<1> for true and C<''> for false. |
361 | If the file doesn't exist or can't be examined, it returns C<undef> and | |
362 | sets C<$!> (errno). Despite the funny names, precedence is the same as any | |
363 | other named unary operator. The operator may be any of: | |
a0d0e21e | 364 | |
5ed4f2ec | 365 | -r File is readable by effective uid/gid. |
366 | -w File is writable by effective uid/gid. | |
367 | -x File is executable by effective uid/gid. | |
368 | -o File is owned by effective uid. | |
a0d0e21e | 369 | |
5ed4f2ec | 370 | -R File is readable by real uid/gid. |
371 | -W File is writable by real uid/gid. | |
372 | -X File is executable by real uid/gid. | |
373 | -O File is owned by real uid. | |
a0d0e21e | 374 | |
5ed4f2ec | 375 | -e File exists. |
376 | -z File has zero size (is empty). | |
377 | -s File has nonzero size (returns size in bytes). | |
a0d0e21e | 378 | |
5ed4f2ec | 379 | -f File is a plain file. |
380 | -d File is a directory. | |
381 | -l File is a symbolic link. | |
382 | -p File is a named pipe (FIFO), or Filehandle is a pipe. | |
383 | -S File is a socket. | |
384 | -b File is a block special file. | |
385 | -c File is a character special file. | |
386 | -t Filehandle is opened to a tty. | |
a0d0e21e | 387 | |
5ed4f2ec | 388 | -u File has setuid bit set. |
389 | -g File has setgid bit set. | |
390 | -k File has sticky bit set. | |
a0d0e21e | 391 | |
5ed4f2ec | 392 | -T File is an ASCII text file (heuristic guess). |
393 | -B File is a "binary" file (opposite of -T). | |
a0d0e21e | 394 | |
5ed4f2ec | 395 | -M Script start time minus file modification time, in days. |
396 | -A Same for access time. | |
f7051f2c FC |
397 | -C Same for inode change time (Unix, may differ for other |
398 | platforms) | |
a0d0e21e | 399 | |
a0d0e21e LW |
400 | Example: |
401 | ||
402 | while (<>) { | |
a9a5a0dc VP |
403 | chomp; |
404 | next unless -f $_; # ignore specials | |
405 | #... | |
a0d0e21e LW |
406 | } |
407 | ||
4fb67938 FC |
408 | Note that C<-s/a/b/> does not do a negated substitution. Saying |
409 | C<-exp($foo)> still works as expected, however: only single letters | |
410 | following a minus are interpreted as file tests. | |
411 | ||
412 | These operators are exempt from the "looks like a function rule" described | |
4d0444a3 FC |
413 | above. That is, an opening parenthesis after the operator does not affect |
414 | how much of the following code constitutes the argument. Put the opening | |
4fb67938 FC |
415 | parentheses before the operator to separate it from code that follows (this |
416 | applies only to operators with higher precedence than unary operators, of | |
417 | course): | |
418 | ||
419 | -s($file) + 1024 # probably wrong; same as -s($file + 1024) | |
420 | (-s $file) + 1024 # correct | |
421 | ||
5ff3f7a4 GS |
422 | The interpretation of the file permission operators C<-r>, C<-R>, |
423 | C<-w>, C<-W>, C<-x>, and C<-X> is by default based solely on the mode | |
424 | of the file and the uids and gids of the user. There may be other | |
ecae030f MO |
425 | reasons you can't actually read, write, or execute the file: for |
426 | example network filesystem access controls, ACLs (access control lists), | |
427 | read-only filesystems, and unrecognized executable formats. Note | |
428 | that the use of these six specific operators to verify if some operation | |
429 | is possible is usually a mistake, because it may be open to race | |
430 | conditions. | |
5ff3f7a4 | 431 | |
2b5ab1e7 TC |
432 | Also note that, for the superuser on the local filesystems, the C<-r>, |
433 | C<-R>, C<-w>, and C<-W> tests always return 1, and C<-x> and C<-X> return 1 | |
5ff3f7a4 GS |
434 | if any execute bit is set in the mode. Scripts run by the superuser |
435 | may thus need to do a stat() to determine the actual mode of the file, | |
2b5ab1e7 | 436 | or temporarily set their effective uid to something else. |
5ff3f7a4 GS |
437 | |
438 | If you are using ACLs, there is a pragma called C<filetest> that may | |
439 | produce more accurate results than the bare stat() mode bits. | |
5dac7880 FC |
440 | When under C<use filetest 'access'> the above-mentioned filetests |
441 | test whether the permission can(not) be granted using the | |
3b10bc60 | 442 | access(2) family of system calls. Also note that the C<-x> and C<-X> may |
5ff3f7a4 GS |
443 | under this pragma return true even if there are no execute permission |
444 | bits set (nor any extra execute permission ACLs). This strangeness is | |
391b733c | 445 | due to the underlying system calls' definitions. Note also that, due to |
ecae030f MO |
446 | the implementation of C<use filetest 'access'>, the C<_> special |
447 | filehandle won't cache the results of the file tests when this pragma is | |
448 | in effect. Read the documentation for the C<filetest> pragma for more | |
449 | information. | |
5ff3f7a4 | 450 | |
a0d0e21e LW |
451 | The C<-T> and C<-B> switches work as follows. The first block or so of the |
452 | file is examined for odd characters such as strange control codes or | |
61eff3bc | 453 | characters with the high bit set. If too many strange characters (>30%) |
cf264981 | 454 | are found, it's a C<-B> file; otherwise it's a C<-T> file. Also, any file |
3b10bc60 | 455 | containing a zero byte in the first block is considered a binary file. If C<-T> |
9124316e | 456 | or C<-B> is used on a filehandle, the current IO buffer is examined |
3b10bc60 | 457 | rather than the first block. Both C<-T> and C<-B> return true on an empty |
54310121 | 458 | file, or a file at EOF when testing a filehandle. Because you have to |
4633a7c4 LW |
459 | read a file to do the C<-T> test, on most occasions you want to use a C<-f> |
460 | against the file first, as in C<next unless -f $file && -T $file>. | |
a0d0e21e | 461 | |
5dac7880 | 462 | If any of the file tests (or either the C<stat> or C<lstat> operator) is given |
28757baa | 463 | the special filehandle consisting of a solitary underline, then the stat |
a0d0e21e LW |
464 | structure of the previous file test (or stat operator) is used, saving |
465 | a system call. (This doesn't work with C<-t>, and you need to remember | |
3b10bc60 | 466 | that lstat() and C<-l> leave values in the stat structure for the |
5c9aa243 | 467 | symbolic link, not the real file.) (Also, if the stat buffer was filled by |
cf264981 | 468 | an C<lstat> call, C<-T> and C<-B> will reset it with the results of C<stat _>). |
5c9aa243 | 469 | Example: |
a0d0e21e LW |
470 | |
471 | print "Can do.\n" if -r $a || -w _ || -x _; | |
472 | ||
473 | stat($filename); | |
474 | print "Readable\n" if -r _; | |
475 | print "Writable\n" if -w _; | |
476 | print "Executable\n" if -x _; | |
477 | print "Setuid\n" if -u _; | |
478 | print "Setgid\n" if -g _; | |
479 | print "Sticky\n" if -k _; | |
480 | print "Text\n" if -T _; | |
481 | print "Binary\n" if -B _; | |
482 | ||
e9fa405d | 483 | As of Perl 5.10.0, as a form of purely syntactic sugar, you can stack file |
fbb0b3b3 | 484 | test operators, in a way that C<-f -w -x $file> is equivalent to |
a5840dee | 485 | C<-x $file && -w _ && -f _>. (This is only fancy syntax: if you use |
fbb0b3b3 RGS |
486 | the return value of C<-f $file> as an argument to another filetest |
487 | operator, no special magic will happen.) | |
488 | ||
bee96257 | 489 | Portability issues: L<perlport/-X>. |
ea9eb35a | 490 | |
bade7fbc TC |
491 | To avoid confusing would-be users of your code with mysterious |
492 | syntax errors, put something like this at the top of your script: | |
493 | ||
494 | use 5.010; # so filetest ops can stack | |
495 | ||
a0d0e21e | 496 | =item abs VALUE |
d74e8afc | 497 | X<abs> X<absolute> |
a0d0e21e | 498 | |
54310121 | 499 | =item abs |
bbce6d69 | 500 | |
c17cdb72 NC |
501 | =for Pod::Functions absolute value function |
502 | ||
a0d0e21e | 503 | Returns the absolute value of its argument. |
7660c0ab | 504 | If VALUE is omitted, uses C<$_>. |
a0d0e21e LW |
505 | |
506 | =item accept NEWSOCKET,GENERICSOCKET | |
d74e8afc | 507 | X<accept> |
a0d0e21e | 508 | |
c17cdb72 NC |
509 | =for Pod::Functions accept an incoming socket connect |
510 | ||
3b10bc60 | 511 | Accepts an incoming socket connect, just as accept(2) |
19799a22 | 512 | does. Returns the packed address if it succeeded, false otherwise. |
2b5ab1e7 | 513 | See the example in L<perlipc/"Sockets: Client/Server Communication">. |
a0d0e21e | 514 | |
8d2a6795 GS |
515 | On systems that support a close-on-exec flag on files, the flag will |
516 | be set for the newly opened file descriptor, as determined by the | |
517 | value of $^F. See L<perlvar/$^F>. | |
518 | ||
a0d0e21e | 519 | =item alarm SECONDS |
d74e8afc ITB |
520 | X<alarm> |
521 | X<SIGALRM> | |
522 | X<timer> | |
a0d0e21e | 523 | |
54310121 | 524 | =item alarm |
bbce6d69 | 525 | |
c17cdb72 NC |
526 | =for Pod::Functions schedule a SIGALRM |
527 | ||
a0d0e21e | 528 | Arranges to have a SIGALRM delivered to this process after the |
cf264981 | 529 | specified number of wallclock seconds has elapsed. If SECONDS is not |
391b733c | 530 | specified, the value stored in C<$_> is used. (On some machines, |
d400eac8 JH |
531 | unfortunately, the elapsed time may be up to one second less or more |
532 | than you specified because of how seconds are counted, and process | |
533 | scheduling may delay the delivery of the signal even further.) | |
534 | ||
535 | Only one timer may be counting at once. Each call disables the | |
536 | previous timer, and an argument of C<0> may be supplied to cancel the | |
537 | previous timer without starting a new one. The returned value is the | |
538 | amount of time remaining on the previous timer. | |
a0d0e21e | 539 | |
2bc69794 BS |
540 | For delays of finer granularity than one second, the Time::HiRes module |
541 | (from CPAN, and starting from Perl 5.8 part of the standard | |
542 | distribution) provides ualarm(). You may also use Perl's four-argument | |
543 | version of select() leaving the first three arguments undefined, or you | |
544 | might be able to use the C<syscall> interface to access setitimer(2) if | |
391b733c | 545 | your system supports it. See L<perlfaq8> for details. |
2b5ab1e7 | 546 | |
80d38338 TC |
547 | It is usually a mistake to intermix C<alarm> and C<sleep> calls, because |
548 | C<sleep> may be internally implemented on your system with C<alarm>. | |
a0d0e21e | 549 | |
19799a22 GS |
550 | If you want to use C<alarm> to time out a system call you need to use an |
551 | C<eval>/C<die> pair. You can't rely on the alarm causing the system call to | |
f86cebdf | 552 | fail with C<$!> set to C<EINTR> because Perl sets up signal handlers to |
19799a22 | 553 | restart system calls on some systems. Using C<eval>/C<die> always works, |
5a964f20 | 554 | modulo the caveats given in L<perlipc/"Signals">. |
ff68c719 | 555 | |
556 | eval { | |
a9a5a0dc VP |
557 | local $SIG{ALRM} = sub { die "alarm\n" }; # NB: \n required |
558 | alarm $timeout; | |
559 | $nread = sysread SOCKET, $buffer, $size; | |
560 | alarm 0; | |
ff68c719 | 561 | }; |
ff68c719 | 562 | if ($@) { |
a9a5a0dc | 563 | die unless $@ eq "alarm\n"; # propagate unexpected errors |
5ed4f2ec | 564 | # timed out |
ff68c719 | 565 | } |
566 | else { | |
5ed4f2ec | 567 | # didn't |
ff68c719 | 568 | } |
569 | ||
91d81acc JH |
570 | For more information see L<perlipc>. |
571 | ||
ea9eb35a BJ |
572 | Portability issues: L<perlport/alarm>. |
573 | ||
a0d0e21e | 574 | =item atan2 Y,X |
d74e8afc | 575 | X<atan2> X<arctangent> X<tan> X<tangent> |
a0d0e21e | 576 | |
c17cdb72 NC |
577 | =for Pod::Functions arctangent of Y/X in the range -PI to PI |
578 | ||
a0d0e21e LW |
579 | Returns the arctangent of Y/X in the range -PI to PI. |
580 | ||
ca6e1c26 | 581 | For the tangent operation, you may use the C<Math::Trig::tan> |
28757baa | 582 | function, or use the familiar relation: |
583 | ||
584 | sub tan { sin($_[0]) / cos($_[0]) } | |
585 | ||
a1021d57 RGS |
586 | The return value for C<atan2(0,0)> is implementation-defined; consult |
587 | your atan2(3) manpage for more information. | |
bf5f1b4c | 588 | |
ea9eb35a BJ |
589 | Portability issues: L<perlport/atan2>. |
590 | ||
a0d0e21e | 591 | =item bind SOCKET,NAME |
d74e8afc | 592 | X<bind> |
a0d0e21e | 593 | |
c17cdb72 NC |
594 | =for Pod::Functions binds an address to a socket |
595 | ||
3b10bc60 | 596 | Binds a network address to a socket, just as bind(2) |
19799a22 | 597 | does. Returns true if it succeeded, false otherwise. NAME should be a |
4633a7c4 LW |
598 | packed address of the appropriate type for the socket. See the examples in |
599 | L<perlipc/"Sockets: Client/Server Communication">. | |
a0d0e21e | 600 | |
fae2c0fb | 601 | =item binmode FILEHANDLE, LAYER |
d74e8afc | 602 | X<binmode> X<binary> X<text> X<DOS> X<Windows> |
1c1fc3ea | 603 | |
a0d0e21e LW |
604 | =item binmode FILEHANDLE |
605 | ||
c17cdb72 NC |
606 | =for Pod::Functions prepare binary files for I/O |
607 | ||
1cbfc93d NIS |
608 | Arranges for FILEHANDLE to be read or written in "binary" or "text" |
609 | mode on systems where the run-time libraries distinguish between | |
610 | binary and text files. If FILEHANDLE is an expression, the value is | |
611 | taken as the name of the filehandle. Returns true on success, | |
b5fe5ca2 | 612 | otherwise it returns C<undef> and sets C<$!> (errno). |
1cbfc93d | 613 | |
8f1da26d | 614 | On some systems (in general, DOS- and Windows-based systems) binmode() |
d807c6f4 | 615 | is necessary when you're not working with a text file. For the sake |
d7a0d798 FC |
616 | of portability it is a good idea always to use it when appropriate, |
617 | and never to use it when it isn't appropriate. Also, people can | |
8f1da26d | 618 | set their I/O to be by default UTF8-encoded Unicode, not bytes. |
d807c6f4 JH |
619 | |
620 | In other words: regardless of platform, use binmode() on binary data, | |
d7a0d798 | 621 | like images, for example. |
d807c6f4 JH |
622 | |
623 | If LAYER is present it is a single string, but may contain multiple | |
391b733c | 624 | directives. The directives alter the behaviour of the filehandle. |
d7a0d798 | 625 | When LAYER is present, using binmode on a text file makes sense. |
d807c6f4 | 626 | |
fae2c0fb | 627 | If LAYER is omitted or specified as C<:raw> the filehandle is made |
391b733c | 628 | suitable for passing binary data. This includes turning off possible CRLF |
0226bbdb | 629 | translation and marking it as bytes (as opposed to Unicode characters). |
749683d2 | 630 | Note that, despite what may be implied in I<"Programming Perl"> (the |
3b10bc60 | 631 | Camel, 3rd edition) or elsewhere, C<:raw> is I<not> simply the inverse of C<:crlf>. |
632 | Other layers that would affect the binary nature of the stream are | |
391b733c | 633 | I<also> disabled. See L<PerlIO>, L<perlrun>, and the discussion about the |
0226bbdb | 634 | PERLIO environment variable. |
01e6739c | 635 | |
3b10bc60 | 636 | The C<:bytes>, C<:crlf>, C<:utf8>, and any other directives of the |
d807c6f4 JH |
637 | form C<:...>, are called I/O I<layers>. The C<open> pragma can be used to |
638 | establish default I/O layers. See L<open>. | |
639 | ||
fae2c0fb RGS |
640 | I<The LAYER parameter of the binmode() function is described as "DISCIPLINE" |
641 | in "Programming Perl, 3rd Edition". However, since the publishing of this | |
642 | book, by many known as "Camel III", the consensus of the naming of this | |
643 | functionality has moved from "discipline" to "layer". All documentation | |
644 | of this version of Perl therefore refers to "layers" rather than to | |
645 | "disciplines". Now back to the regularly scheduled documentation...> | |
646 | ||
8f1da26d | 647 | To mark FILEHANDLE as UTF-8, use C<:utf8> or C<:encoding(UTF-8)>. |
6902c96a | 648 | C<:utf8> just marks the data as UTF-8 without further checking, |
8f1da26d | 649 | while C<:encoding(UTF-8)> checks the data for actually being valid |
391b733c | 650 | UTF-8. More details can be found in L<PerlIO::encoding>. |
1cbfc93d | 651 | |
ed53a2bb | 652 | In general, binmode() should be called after open() but before any I/O |
3b10bc60 | 653 | is done on the filehandle. Calling binmode() normally flushes any |
01e6739c | 654 | pending buffered output data (and perhaps pending input data) on the |
fae2c0fb | 655 | handle. An exception to this is the C<:encoding> layer that |
d7a0d798 | 656 | changes the default character encoding of the handle; see L</open>. |
fae2c0fb | 657 | The C<:encoding> layer sometimes needs to be called in |
3874323d JH |
658 | mid-stream, and it doesn't flush the stream. The C<:encoding> |
659 | also implicitly pushes on top of itself the C<:utf8> layer because | |
3b10bc60 | 660 | internally Perl operates on UTF8-encoded Unicode characters. |
16fe6d59 | 661 | |
19799a22 | 662 | The operating system, device drivers, C libraries, and Perl run-time |
8f1da26d TC |
663 | system all conspire to let the programmer treat a single |
664 | character (C<\n>) as the line terminator, irrespective of external | |
30168b04 GS |
665 | representation. On many operating systems, the native text file |
666 | representation matches the internal representation, but on some | |
667 | platforms the external representation of C<\n> is made up of more than | |
668 | one character. | |
669 | ||
8f1da26d TC |
670 | All variants of Unix, Mac OS (old and new), and Stream_LF files on VMS use |
671 | a single character to end each line in the external representation of text | |
672 | (even though that single character is CARRIAGE RETURN on old, pre-Darwin | |
391b733c | 673 | flavors of Mac OS, and is LINE FEED on Unix and most VMS files). In other |
8f1da26d TC |
674 | systems like OS/2, DOS, and the various flavors of MS-Windows, your program |
675 | sees a C<\n> as a simple C<\cJ>, but what's stored in text files are the | |
676 | two characters C<\cM\cJ>. That means that if you don't use binmode() on | |
677 | these systems, C<\cM\cJ> sequences on disk will be converted to C<\n> on | |
678 | input, and any C<\n> in your program will be converted back to C<\cM\cJ> on | |
679 | output. This is what you want for text files, but it can be disastrous for | |
680 | binary files. | |
30168b04 GS |
681 | |
682 | Another consequence of using binmode() (on some systems) is that | |
683 | special end-of-file markers will be seen as part of the data stream. | |
d7a0d798 FC |
684 | For systems from the Microsoft family this means that, if your binary |
685 | data contain C<\cZ>, the I/O subsystem will regard it as the end of | |
30168b04 GS |
686 | the file, unless you use binmode(). |
687 | ||
3b10bc60 | 688 | binmode() is important not only for readline() and print() operations, |
30168b04 GS |
689 | but also when using read(), seek(), sysread(), syswrite() and tell() |
690 | (see L<perlport> for more details). See the C<$/> and C<$\> variables | |
691 | in L<perlvar> for how to manually set your input and output | |
692 | line-termination sequences. | |
a0d0e21e | 693 | |
ea9eb35a BJ |
694 | Portability issues: L<perlport/binmode>. |
695 | ||
4633a7c4 | 696 | =item bless REF,CLASSNAME |
d74e8afc | 697 | X<bless> |
a0d0e21e LW |
698 | |
699 | =item bless REF | |
700 | ||
c17cdb72 NC |
701 | =for Pod::Functions create an object |
702 | ||
2b5ab1e7 TC |
703 | This function tells the thingy referenced by REF that it is now an object |
704 | in the CLASSNAME package. If CLASSNAME is omitted, the current package | |
19799a22 | 705 | is used. Because a C<bless> is often the last thing in a constructor, |
2b5ab1e7 | 706 | it returns the reference for convenience. Always use the two-argument |
cf264981 | 707 | version if a derived class might inherit the function doing the blessing. |
e54e4959 | 708 | See L<perlobj> for more about the blessing (and blessings) of objects. |
a0d0e21e | 709 | |
57668c4d | 710 | Consider always blessing objects in CLASSNAMEs that are mixed case. |
2b5ab1e7 | 711 | Namespaces with all lowercase names are considered reserved for |
391b733c | 712 | Perl pragmata. Builtin types have all uppercase names. To prevent |
2b5ab1e7 TC |
713 | confusion, you may wish to avoid such package names as well. Make sure |
714 | that CLASSNAME is a true value. | |
60ad88b8 GS |
715 | |
716 | See L<perlmod/"Perl Modules">. | |
717 | ||
0d863452 RH |
718 | =item break |
719 | ||
d9b04284 | 720 | =for Pod::Functions +switch break out of a C<given> block |
c17cdb72 | 721 | |
0d863452 RH |
722 | Break out of a C<given()> block. |
723 | ||
a8a26e52 JK |
724 | This keyword is enabled by the C<"switch"> feature; see L<feature> for |
725 | more information on C<"switch">. You can also access it by prefixing it | |
726 | with C<CORE::>. Alternatively, include a C<use v5.10> or later to the | |
727 | current scope. | |
0d863452 | 728 | |
a0d0e21e | 729 | =item caller EXPR |
d74e8afc | 730 | X<caller> X<call stack> X<stack> X<stack trace> |
a0d0e21e LW |
731 | |
732 | =item caller | |
733 | ||
c17cdb72 NC |
734 | =for Pod::Functions get context of the current subroutine call |
735 | ||
1d56df50 DD |
736 | Returns the context of the current pure perl subroutine call. In scalar |
737 | context, returns the caller's package name if there I<is> a caller (that is, if | |
80d38338 | 738 | we're in a subroutine or C<eval> or C<require>) and the undefined value |
1d56df50 DD |
739 | otherwise. caller never returns XS subs and they are skipped. The next pure |
740 | perl sub will appear instead of the XS sub in caller's return values. In list | |
741 | context, caller returns | |
a0d0e21e | 742 | |
ee6b43cc | 743 | # 0 1 2 |
748a9306 | 744 | ($package, $filename, $line) = caller; |
a0d0e21e LW |
745 | |
746 | With EXPR, it returns some extra information that the debugger uses to | |
747 | print a stack trace. The value of EXPR indicates how many call frames | |
748 | to go back before the current one. | |
749 | ||
ee6b43cc | 750 | # 0 1 2 3 4 |
f3aa04c2 | 751 | ($package, $filename, $line, $subroutine, $hasargs, |
ee6b43cc | 752 | |
753 | # 5 6 7 8 9 10 | |
b3ca2e83 | 754 | $wantarray, $evaltext, $is_require, $hints, $bitmask, $hinthash) |
ee6b43cc | 755 | = caller($i); |
e7ea3e70 | 756 | |
02729fef DM |
757 | Here, $subroutine is the function that the caller called (rather than the |
758 | function containing the caller). Note that $subroutine may be C<(eval)> if | |
759 | the frame is not a subroutine call, but an C<eval>. In such a case | |
760 | additional elements $evaltext and | |
7660c0ab | 761 | C<$is_require> are set: C<$is_require> is true if the frame is created by a |
19799a22 | 762 | C<require> or C<use> statement, $evaltext contains the text of the |
277ddfaf | 763 | C<eval EXPR> statement. In particular, for an C<eval BLOCK> statement, |
cc1c2e42 | 764 | $subroutine is C<(eval)>, but $evaltext is undefined. (Note also that |
0fc9dec4 RGS |
765 | each C<use> statement creates a C<require> frame inside an C<eval EXPR> |
766 | frame.) $subroutine may also be C<(unknown)> if this particular | |
767 | subroutine happens to have been deleted from the symbol table. | |
768 | C<$hasargs> is true if a new instance of C<@_> was set up for the frame. | |
769 | C<$hints> and C<$bitmask> contain pragmatic hints that the caller was | |
585d73c3 | 770 | compiled with. C<$hints> corresponds to C<$^H>, and C<$bitmask> |
1adb05cd FC |
771 | corresponds to C<${^WARNING_BITS}>. The |
772 | C<$hints> and C<$bitmask> values are subject | |
585d73c3 | 773 | to change between versions of Perl, and are not meant for external use. |
748a9306 | 774 | |
b3ca2e83 | 775 | C<$hinthash> is a reference to a hash containing the value of C<%^H> when the |
391b733c | 776 | caller was compiled, or C<undef> if C<%^H> was empty. Do not modify the values |
b3ca2e83 NC |
777 | of this hash, as they are the actual values stored in the optree. |
778 | ||
ffe0c19d FC |
779 | Furthermore, when called from within the DB package in |
780 | list context, and with an argument, caller returns more | |
7660c0ab | 781 | detailed information: it sets the list variable C<@DB::args> to be the |
54310121 | 782 | arguments with which the subroutine was invoked. |
748a9306 | 783 | |
7660c0ab | 784 | Be aware that the optimizer might have optimized call frames away before |
19799a22 | 785 | C<caller> had a chance to get the information. That means that C<caller(N)> |
80d38338 | 786 | might not return information about the call frame you expect it to, for |
b76cc8ba | 787 | C<< N > 1 >>. In particular, C<@DB::args> might have information from the |
19799a22 | 788 | previous time C<caller> was called. |
7660c0ab | 789 | |
8f1da26d | 790 | Be aware that setting C<@DB::args> is I<best effort>, intended for |
391b733c | 791 | debugging or generating backtraces, and should not be relied upon. In |
ca9f0cb5 NC |
792 | particular, as C<@_> contains aliases to the caller's arguments, Perl does |
793 | not take a copy of C<@_>, so C<@DB::args> will contain modifications the | |
794 | subroutine makes to C<@_> or its contents, not the original values at call | |
391b733c | 795 | time. C<@DB::args>, like C<@_>, does not hold explicit references to its |
ca9f0cb5 | 796 | elements, so under certain cases its elements may have become freed and |
391b733c | 797 | reallocated for other variables or temporary values. Finally, a side effect |
d7a0d798 | 798 | of the current implementation is that the effects of C<shift @_> can |
8f1da26d TC |
799 | I<normally> be undone (but not C<pop @_> or other splicing, I<and> not if a |
800 | reference to C<@_> has been taken, I<and> subject to the caveat about reallocated | |
ca9f0cb5 | 801 | elements), so C<@DB::args> is actually a hybrid of the current state and |
391b733c | 802 | initial state of C<@_>. Buyer beware. |
ca9f0cb5 | 803 | |
a0d0e21e | 804 | =item chdir EXPR |
d74e8afc ITB |
805 | X<chdir> |
806 | X<cd> | |
f723aae1 | 807 | X<directory, change> |
a0d0e21e | 808 | |
c4aca7d0 GA |
809 | =item chdir FILEHANDLE |
810 | ||
811 | =item chdir DIRHANDLE | |
812 | ||
ce2984c3 PF |
813 | =item chdir |
814 | ||
c17cdb72 NC |
815 | =for Pod::Functions change your current working directory |
816 | ||
391b733c | 817 | Changes the working directory to EXPR, if possible. If EXPR is omitted, |
0bfc1ec4 | 818 | changes to the directory specified by C<$ENV{HOME}>, if set; if not, |
391b733c FC |
819 | changes to the directory specified by C<$ENV{LOGDIR}>. (Under VMS, the |
820 | variable C<$ENV{SYS$LOGIN}> is also checked, and used if it is set.) If | |
821 | neither is set, C<chdir> does nothing. It returns true on success, | |
822 | false otherwise. See the example under C<die>. | |
a0d0e21e | 823 | |
3b10bc60 | 824 | On systems that support fchdir(2), you may pass a filehandle or |
34169887 | 825 | directory handle as the argument. On systems that don't support fchdir(2), |
3b10bc60 | 826 | passing handles raises an exception. |
c4aca7d0 | 827 | |
a0d0e21e | 828 | =item chmod LIST |
d74e8afc | 829 | X<chmod> X<permission> X<mode> |
a0d0e21e | 830 | |
c17cdb72 NC |
831 | =for Pod::Functions changes the permissions on a list of files |
832 | ||
a0d0e21e | 833 | Changes the permissions of a list of files. The first element of the |
8f1da26d | 834 | list must be the numeric mode, which should probably be an octal |
4ad40acf | 835 | number, and which definitely should I<not> be a string of octal digits: |
3b10bc60 | 836 | C<0644> is okay, but C<"0644"> is not. Returns the number of files |
8f1da26d | 837 | successfully changed. See also L</oct> if all you have is a string. |
a0d0e21e | 838 | |
3b10bc60 | 839 | $cnt = chmod 0755, "foo", "bar"; |
a0d0e21e | 840 | chmod 0755, @executables; |
3b10bc60 | 841 | $mode = "0644"; chmod $mode, "foo"; # !!! sets mode to |
f86cebdf | 842 | # --w----r-T |
3b10bc60 | 843 | $mode = "0644"; chmod oct($mode), "foo"; # this is better |
844 | $mode = 0644; chmod $mode, "foo"; # this is best | |
a0d0e21e | 845 | |
3b10bc60 | 846 | On systems that support fchmod(2), you may pass filehandles among the |
847 | files. On systems that don't support fchmod(2), passing filehandles raises | |
848 | an exception. Filehandles must be passed as globs or glob references to be | |
849 | recognized; barewords are considered filenames. | |
c4aca7d0 GA |
850 | |
851 | open(my $fh, "<", "foo"); | |
852 | my $perm = (stat $fh)[2] & 07777; | |
853 | chmod($perm | 0600, $fh); | |
854 | ||
3b10bc60 | 855 | You can also import the symbolic C<S_I*> constants from the C<Fcntl> |
ca6e1c26 JH |
856 | module: |
857 | ||
3b10bc60 | 858 | use Fcntl qw( :mode ); |
ca6e1c26 | 859 | chmod S_IRWXU|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH, @executables; |
3b10bc60 | 860 | # Identical to the chmod 0755 of the example above. |
ca6e1c26 | 861 | |
ea9eb35a BJ |
862 | Portability issues: L<perlport/chmod>. |
863 | ||
a0d0e21e | 864 | =item chomp VARIABLE |
d74e8afc | 865 | X<chomp> X<INPUT_RECORD_SEPARATOR> X<$/> X<newline> X<eol> |
a0d0e21e | 866 | |
313c9f5c | 867 | =item chomp( LIST ) |
a0d0e21e LW |
868 | |
869 | =item chomp | |
870 | ||
c17cdb72 NC |
871 | =for Pod::Functions remove a trailing record separator from a string |
872 | ||
2b5ab1e7 TC |
873 | This safer version of L</chop> removes any trailing string |
874 | that corresponds to the current value of C<$/> (also known as | |
28757baa | 875 | $INPUT_RECORD_SEPARATOR in the C<English> module). It returns the total |
876 | number of characters removed from all its arguments. It's often used to | |
877 | remove the newline from the end of an input record when you're worried | |
2b5ab1e7 TC |
878 | that the final record may be missing its newline. When in paragraph |
879 | mode (C<$/ = "">), it removes all trailing newlines from the string. | |
4c5a6083 | 880 | When in slurp mode (C<$/ = undef>) or fixed-length record mode (C<$/> is |
34169887 | 881 | a reference to an integer or the like; see L<perlvar>) chomp() won't |
b76cc8ba | 882 | remove anything. |
19799a22 | 883 | If VARIABLE is omitted, it chomps C<$_>. Example: |
a0d0e21e LW |
884 | |
885 | while (<>) { | |
a9a5a0dc VP |
886 | chomp; # avoid \n on last field |
887 | @array = split(/:/); | |
888 | # ... | |
a0d0e21e LW |
889 | } |
890 | ||
feef49c9 FC |
891 | If VARIABLE is a hash, it chomps the hash's values, but not its keys, |
892 | resetting the C<each> iterator in the process. | |
4bf21a6d | 893 | |
a0d0e21e LW |
894 | You can actually chomp anything that's an lvalue, including an assignment: |
895 | ||
896 | chomp($cwd = `pwd`); | |
897 | chomp($answer = <STDIN>); | |
898 | ||
899 | If you chomp a list, each element is chomped, and the total number of | |
900 | characters removed is returned. | |
901 | ||
15e44fd8 RGS |
902 | Note that parentheses are necessary when you're chomping anything |
903 | that is not a simple variable. This is because C<chomp $cwd = `pwd`;> | |
904 | is interpreted as C<(chomp $cwd) = `pwd`;>, rather than as | |
905 | C<chomp( $cwd = `pwd` )> which you might expect. Similarly, | |
906 | C<chomp $a, $b> is interpreted as C<chomp($a), $b> rather than | |
907 | as C<chomp($a, $b)>. | |
908 | ||
a0d0e21e | 909 | =item chop VARIABLE |
d74e8afc | 910 | X<chop> |
a0d0e21e | 911 | |
313c9f5c | 912 | =item chop( LIST ) |
a0d0e21e LW |
913 | |
914 | =item chop | |
915 | ||
c17cdb72 NC |
916 | =for Pod::Functions remove the last character from a string |
917 | ||
a0d0e21e | 918 | Chops off the last character of a string and returns the character |
5b3eff12 | 919 | chopped. It is much more efficient than C<s/.$//s> because it neither |
7660c0ab | 920 | scans nor copies the string. If VARIABLE is omitted, chops C<$_>. |
feef49c9 FC |
921 | If VARIABLE is a hash, it chops the hash's values, but not its keys, |
922 | resetting the C<each> iterator in the process. | |
4bf21a6d | 923 | |
5b3eff12 | 924 | You can actually chop anything that's an lvalue, including an assignment. |
a0d0e21e LW |
925 | |
926 | If you chop a list, each element is chopped. Only the value of the | |
19799a22 | 927 | last C<chop> is returned. |
a0d0e21e | 928 | |
19799a22 | 929 | Note that C<chop> returns the last character. To return all but the last |
748a9306 LW |
930 | character, use C<substr($string, 0, -1)>. |
931 | ||
15e44fd8 RGS |
932 | See also L</chomp>. |
933 | ||
a0d0e21e | 934 | =item chown LIST |
d74e8afc | 935 | X<chown> X<owner> X<user> X<group> |
a0d0e21e | 936 | |
c17cdb72 NC |
937 | =for Pod::Functions change the ownership on a list of files |
938 | ||
a0d0e21e | 939 | Changes the owner (and group) of a list of files. The first two |
19799a22 GS |
940 | elements of the list must be the I<numeric> uid and gid, in that |
941 | order. A value of -1 in either position is interpreted by most | |
942 | systems to leave that value unchanged. Returns the number of files | |
943 | successfully changed. | |
a0d0e21e LW |
944 | |
945 | $cnt = chown $uid, $gid, 'foo', 'bar'; | |
946 | chown $uid, $gid, @filenames; | |
947 | ||
3b10bc60 | 948 | On systems that support fchown(2), you may pass filehandles among the |
949 | files. On systems that don't support fchown(2), passing filehandles raises | |
950 | an exception. Filehandles must be passed as globs or glob references to be | |
951 | recognized; barewords are considered filenames. | |
c4aca7d0 | 952 | |
54310121 | 953 | Here's an example that looks up nonnumeric uids in the passwd file: |
a0d0e21e LW |
954 | |
955 | print "User: "; | |
19799a22 | 956 | chomp($user = <STDIN>); |
5a964f20 | 957 | print "Files: "; |
19799a22 | 958 | chomp($pattern = <STDIN>); |
a0d0e21e LW |
959 | |
960 | ($login,$pass,$uid,$gid) = getpwnam($user) | |
a9a5a0dc | 961 | or die "$user not in passwd file"; |
a0d0e21e | 962 | |
5ed4f2ec | 963 | @ary = glob($pattern); # expand filenames |
a0d0e21e LW |
964 | chown $uid, $gid, @ary; |
965 | ||
54310121 | 966 | On most systems, you are not allowed to change the ownership of the |
4633a7c4 LW |
967 | file unless you're the superuser, although you should be able to change |
968 | the group to any of your secondary groups. On insecure systems, these | |
969 | restrictions may be relaxed, but this is not a portable assumption. | |
19799a22 GS |
970 | On POSIX systems, you can detect this condition this way: |
971 | ||
972 | use POSIX qw(sysconf _PC_CHOWN_RESTRICTED); | |
973 | $can_chown_giveaway = not sysconf(_PC_CHOWN_RESTRICTED); | |
4633a7c4 | 974 | |
f48496b1 | 975 | Portability issues: L<perlport/chown>. |
ea9eb35a | 976 | |
a0d0e21e | 977 | =item chr NUMBER |
d74e8afc | 978 | X<chr> X<character> X<ASCII> X<Unicode> |
a0d0e21e | 979 | |
54310121 | 980 | =item chr |
bbce6d69 | 981 | |
c17cdb72 NC |
982 | =for Pod::Functions get character this number represents |
983 | ||
a0d0e21e | 984 | Returns the character represented by that NUMBER in the character set. |
a0ed51b3 | 985 | For example, C<chr(65)> is C<"A"> in either ASCII or Unicode, and |
2575c402 | 986 | chr(0x263a) is a Unicode smiley face. |
aaa68c4a | 987 | |
8a064bd6 | 988 | Negative values give the Unicode replacement character (chr(0xfffd)), |
80d38338 | 989 | except under the L<bytes> pragma, where the low eight bits of the value |
8a064bd6 JH |
990 | (truncated to an integer) are used. |
991 | ||
974da8e5 JH |
992 | If NUMBER is omitted, uses C<$_>. |
993 | ||
b76cc8ba | 994 | For the reverse, use L</ord>. |
a0d0e21e | 995 | |
2575c402 JW |
996 | Note that characters from 128 to 255 (inclusive) are by default |
997 | internally not encoded as UTF-8 for backward compatibility reasons. | |
974da8e5 | 998 | |
2575c402 | 999 | See L<perlunicode> for more about Unicode. |
bbce6d69 | 1000 | |
a0d0e21e | 1001 | =item chroot FILENAME |
d74e8afc | 1002 | X<chroot> X<root> |
a0d0e21e | 1003 | |
54310121 | 1004 | =item chroot |
bbce6d69 | 1005 | |
c17cdb72 NC |
1006 | =for Pod::Functions make directory new root for path lookups |
1007 | ||
5a964f20 | 1008 | This function works like the system call by the same name: it makes the |
4633a7c4 | 1009 | named directory the new root directory for all further pathnames that |
951ba7fe | 1010 | begin with a C</> by your process and all its children. (It doesn't |
28757baa | 1011 | change your current working directory, which is unaffected.) For security |
4633a7c4 | 1012 | reasons, this call is restricted to the superuser. If FILENAME is |
19799a22 | 1013 | omitted, does a C<chroot> to C<$_>. |
a0d0e21e | 1014 | |
ea9eb35a BJ |
1015 | Portability issues: L<perlport/chroot>. |
1016 | ||
a0d0e21e | 1017 | =item close FILEHANDLE |
d74e8afc | 1018 | X<close> |
a0d0e21e | 1019 | |
6a518fbc TP |
1020 | =item close |
1021 | ||
c17cdb72 NC |
1022 | =for Pod::Functions close file (or pipe or socket) handle |
1023 | ||
3b10bc60 | 1024 | Closes the file or pipe associated with the filehandle, flushes the IO |
e0f13c26 | 1025 | buffers, and closes the system file descriptor. Returns true if those |
8f1da26d | 1026 | operations succeed and if no error was reported by any PerlIO |
e0f13c26 RGS |
1027 | layer. Closes the currently selected filehandle if the argument is |
1028 | omitted. | |
fb73857a | 1029 | |
1030 | You don't have to close FILEHANDLE if you are immediately going to do | |
3b10bc60 | 1031 | another C<open> on it, because C<open> closes it for you. (See |
01aa884e | 1032 | L<open|/open FILEHANDLE>.) However, an explicit C<close> on an input file resets the line |
19799a22 | 1033 | counter (C<$.>), while the implicit close done by C<open> does not. |
fb73857a | 1034 | |
3b10bc60 | 1035 | If the filehandle came from a piped open, C<close> returns false if one of |
1036 | the other syscalls involved fails or if its program exits with non-zero | |
1037 | status. If the only problem was that the program exited non-zero, C<$!> | |
1038 | will be set to C<0>. Closing a pipe also waits for the process executing | |
1039 | on the pipe to exit--in case you wish to look at the output of the pipe | |
1040 | afterwards--and implicitly puts the exit status value of that command into | |
1041 | C<$?> and C<${^CHILD_ERROR_NATIVE}>. | |
5a964f20 | 1042 | |
2e0cfa16 FC |
1043 | If there are multiple threads running, C<close> on a filehandle from a |
1044 | piped open returns true without waiting for the child process to terminate, | |
1045 | if the filehandle is still open in another thread. | |
1046 | ||
80d38338 TC |
1047 | Closing the read end of a pipe before the process writing to it at the |
1048 | other end is done writing results in the writer receiving a SIGPIPE. If | |
1049 | the other end can't handle that, be sure to read all the data before | |
1050 | closing the pipe. | |
73689b13 | 1051 | |
fb73857a | 1052 | Example: |
a0d0e21e | 1053 | |
fb73857a | 1054 | open(OUTPUT, '|sort >foo') # pipe to sort |
1055 | or die "Can't start sort: $!"; | |
5ed4f2ec | 1056 | #... # print stuff to output |
1057 | close OUTPUT # wait for sort to finish | |
fb73857a | 1058 | or warn $! ? "Error closing sort pipe: $!" |
1059 | : "Exit status $? from sort"; | |
5ed4f2ec | 1060 | open(INPUT, 'foo') # get sort's results |
fb73857a | 1061 | or die "Can't open 'foo' for input: $!"; |
a0d0e21e | 1062 | |
5a964f20 | 1063 | FILEHANDLE may be an expression whose value can be used as an indirect |
8f1da26d | 1064 | filehandle, usually the real filehandle name or an autovivified handle. |
a0d0e21e LW |
1065 | |
1066 | =item closedir DIRHANDLE | |
d74e8afc | 1067 | X<closedir> |
a0d0e21e | 1068 | |
c17cdb72 NC |
1069 | =for Pod::Functions close directory handle |
1070 | ||
19799a22 | 1071 | Closes a directory opened by C<opendir> and returns the success of that |
5a964f20 TC |
1072 | system call. |
1073 | ||
a0d0e21e | 1074 | =item connect SOCKET,NAME |
d74e8afc | 1075 | X<connect> |
a0d0e21e | 1076 | |
c17cdb72 NC |
1077 | =for Pod::Functions connect to a remote socket |
1078 | ||
80d38338 TC |
1079 | Attempts to connect to a remote socket, just like connect(2). |
1080 | Returns true if it succeeded, false otherwise. NAME should be a | |
4633a7c4 LW |
1081 | packed address of the appropriate type for the socket. See the examples in |
1082 | L<perlipc/"Sockets: Client/Server Communication">. | |
a0d0e21e | 1083 | |
cb1a09d0 | 1084 | =item continue BLOCK |
d74e8afc | 1085 | X<continue> |
cb1a09d0 | 1086 | |
0d863452 RH |
1087 | =item continue |
1088 | ||
c17cdb72 NC |
1089 | =for Pod::Functions optional trailing block in a while or foreach |
1090 | ||
4a904372 FC |
1091 | When followed by a BLOCK, C<continue> is actually a |
1092 | flow control statement rather than a function. If | |
cf264981 | 1093 | there is a C<continue> BLOCK attached to a BLOCK (typically in a C<while> or |
98293880 JH |
1094 | C<foreach>), it is always executed just before the conditional is about to |
1095 | be evaluated again, just like the third part of a C<for> loop in C. Thus | |
cb1a09d0 AD |
1096 | it can be used to increment a loop variable, even when the loop has been |
1097 | continued via the C<next> statement (which is similar to the C C<continue> | |
1098 | statement). | |
1099 | ||
98293880 | 1100 | C<last>, C<next>, or C<redo> may appear within a C<continue> |
3b10bc60 | 1101 | block; C<last> and C<redo> behave as if they had been executed within |
19799a22 | 1102 | the main block. So will C<next>, but since it will execute a C<continue> |
1d2dff63 GS |
1103 | block, it may be more entertaining. |
1104 | ||
1105 | while (EXPR) { | |
a9a5a0dc VP |
1106 | ### redo always comes here |
1107 | do_something; | |
1d2dff63 | 1108 | } continue { |
a9a5a0dc VP |
1109 | ### next always comes here |
1110 | do_something_else; | |
1111 | # then back the top to re-check EXPR | |
1d2dff63 GS |
1112 | } |
1113 | ### last always comes here | |
1114 | ||
3b10bc60 | 1115 | Omitting the C<continue> section is equivalent to using an |
1116 | empty one, logically enough, so C<next> goes directly back | |
1d2dff63 GS |
1117 | to check the condition at the top of the loop. |
1118 | ||
4a904372 | 1119 | When there is no BLOCK, C<continue> is a function that |
8f1da26d TC |
1120 | falls through the current C<when> or C<default> block instead of iterating |
1121 | a dynamically enclosing C<foreach> or exiting a lexically enclosing C<given>. | |
4a904372 FC |
1122 | In Perl 5.14 and earlier, this form of C<continue> was |
1123 | only available when the C<"switch"> feature was enabled. | |
48238296 | 1124 | See L<feature> and L<perlsyn/"Switch Statements"> for more |
8f1da26d | 1125 | information. |
0d863452 | 1126 | |
a0d0e21e | 1127 | =item cos EXPR |
d74e8afc | 1128 | X<cos> X<cosine> X<acos> X<arccosine> |
a0d0e21e | 1129 | |
d6217f1e GS |
1130 | =item cos |
1131 | ||
c17cdb72 NC |
1132 | =for Pod::Functions cosine function |
1133 | ||
5a964f20 | 1134 | Returns the cosine of EXPR (expressed in radians). If EXPR is omitted, |
34169887 | 1135 | takes the cosine of C<$_>. |
a0d0e21e | 1136 | |
ca6e1c26 | 1137 | For the inverse cosine operation, you may use the C<Math::Trig::acos()> |
28757baa | 1138 | function, or use this relation: |
1139 | ||
1140 | sub acos { atan2( sqrt(1 - $_[0] * $_[0]), $_[0] ) } | |
1141 | ||
a0d0e21e | 1142 | =item crypt PLAINTEXT,SALT |
d74e8afc | 1143 | X<crypt> X<digest> X<hash> X<salt> X<plaintext> X<password> |
f723aae1 | 1144 | X<decrypt> X<cryptography> X<passwd> X<encrypt> |
a0d0e21e | 1145 | |
c17cdb72 NC |
1146 | =for Pod::Functions one-way passwd-style encryption |
1147 | ||
ef2e6798 MS |
1148 | Creates a digest string exactly like the crypt(3) function in the C |
1149 | library (assuming that you actually have a version there that has not | |
bb23f8d1 | 1150 | been extirpated as a potential munition). |
ef2e6798 | 1151 | |
34169887 | 1152 | crypt() is a one-way hash function. The PLAINTEXT and SALT are turned |
ef2e6798 MS |
1153 | into a short string, called a digest, which is returned. The same |
1154 | PLAINTEXT and SALT will always return the same string, but there is no | |
1155 | (known) way to get the original PLAINTEXT from the hash. Small | |
1156 | changes in the PLAINTEXT or SALT will result in large changes in the | |
1157 | digest. | |
1158 | ||
1159 | There is no decrypt function. This function isn't all that useful for | |
1160 | cryptography (for that, look for F<Crypt> modules on your nearby CPAN | |
1161 | mirror) and the name "crypt" is a bit of a misnomer. Instead it is | |
1162 | primarily used to check if two pieces of text are the same without | |
1163 | having to transmit or store the text itself. An example is checking | |
1164 | if a correct password is given. The digest of the password is stored, | |
cf264981 | 1165 | not the password itself. The user types in a password that is |
ef2e6798 | 1166 | crypt()'d with the same salt as the stored digest. If the two digests |
34169887 | 1167 | match, the password is correct. |
ef2e6798 MS |
1168 | |
1169 | When verifying an existing digest string you should use the digest as | |
1170 | the salt (like C<crypt($plain, $digest) eq $digest>). The SALT used | |
cf264981 | 1171 | to create the digest is visible as part of the digest. This ensures |
ef2e6798 MS |
1172 | crypt() will hash the new string with the same salt as the digest. |
1173 | This allows your code to work with the standard L<crypt|/crypt> and | |
8f1da26d TC |
1174 | with more exotic implementations. In other words, assume |
1175 | nothing about the returned string itself nor about how many bytes | |
1176 | of SALT may matter. | |
85c16d83 JH |
1177 | |
1178 | Traditionally the result is a string of 13 bytes: two first bytes of | |
1179 | the salt, followed by 11 bytes from the set C<[./0-9A-Za-z]>, and only | |
391b733c | 1180 | the first eight bytes of PLAINTEXT mattered. But alternative |
ef2e6798 | 1181 | hashing schemes (like MD5), higher level security schemes (like C2), |
e1020413 | 1182 | and implementations on non-Unix platforms may produce different |
ef2e6798 | 1183 | strings. |
85c16d83 JH |
1184 | |
1185 | When choosing a new salt create a random two character string whose | |
1186 | characters come from the set C<[./0-9A-Za-z]> (like C<join '', ('.', | |
d3989d75 CW |
1187 | '/', 0..9, 'A'..'Z', 'a'..'z')[rand 64, rand 64]>). This set of |
1188 | characters is just a recommendation; the characters allowed in | |
1189 | the salt depend solely on your system's crypt library, and Perl can't | |
1190 | restrict what salts C<crypt()> accepts. | |
e71965be | 1191 | |
a0d0e21e | 1192 | Here's an example that makes sure that whoever runs this program knows |
cf264981 | 1193 | their password: |
a0d0e21e LW |
1194 | |
1195 | $pwd = (getpwuid($<))[1]; | |
a0d0e21e LW |
1196 | |
1197 | system "stty -echo"; | |
1198 | print "Password: "; | |
e71965be | 1199 | chomp($word = <STDIN>); |
a0d0e21e LW |
1200 | print "\n"; |
1201 | system "stty echo"; | |
1202 | ||
e71965be | 1203 | if (crypt($word, $pwd) ne $pwd) { |
a9a5a0dc | 1204 | die "Sorry...\n"; |
a0d0e21e | 1205 | } else { |
a9a5a0dc | 1206 | print "ok\n"; |
54310121 | 1207 | } |
a0d0e21e | 1208 | |
9f8f0c9d | 1209 | Of course, typing in your own password to whoever asks you |
748a9306 | 1210 | for it is unwise. |
a0d0e21e | 1211 | |
ef2e6798 | 1212 | The L<crypt|/crypt> function is unsuitable for hashing large quantities |
19799a22 | 1213 | of data, not least of all because you can't get the information |
ef2e6798 | 1214 | back. Look at the L<Digest> module for more robust algorithms. |
19799a22 | 1215 | |
f2791508 JH |
1216 | If using crypt() on a Unicode string (which I<potentially> has |
1217 | characters with codepoints above 255), Perl tries to make sense | |
34169887 | 1218 | of the situation by trying to downgrade (a copy of) |
f2791508 JH |
1219 | the string back to an eight-bit byte string before calling crypt() |
1220 | (on that copy). If that works, good. If not, crypt() dies with | |
1221 | C<Wide character in crypt>. | |
85c16d83 | 1222 | |
ea9eb35a BJ |
1223 | Portability issues: L<perlport/crypt>. |
1224 | ||
aa689395 | 1225 | =item dbmclose HASH |
d74e8afc | 1226 | X<dbmclose> |
a0d0e21e | 1227 | |
c17cdb72 NC |
1228 | =for Pod::Functions breaks binding on a tied dbm file |
1229 | ||
19799a22 | 1230 | [This function has been largely superseded by the C<untie> function.] |
a0d0e21e | 1231 | |
aa689395 | 1232 | Breaks the binding between a DBM file and a hash. |
a0d0e21e | 1233 | |
ea9eb35a BJ |
1234 | Portability issues: L<perlport/dbmclose>. |
1235 | ||
19799a22 | 1236 | =item dbmopen HASH,DBNAME,MASK |
d74e8afc | 1237 | X<dbmopen> X<dbm> X<ndbm> X<sdbm> X<gdbm> |
a0d0e21e | 1238 | |
c17cdb72 NC |
1239 | =for Pod::Functions create binding on a tied dbm file |
1240 | ||
01aa884e KW |
1241 | [This function has been largely superseded by the |
1242 | L<tie|/tie VARIABLE,CLASSNAME,LIST> function.] | |
a0d0e21e | 1243 | |
7b8d334a | 1244 | This binds a dbm(3), ndbm(3), sdbm(3), gdbm(3), or Berkeley DB file to a |
19799a22 GS |
1245 | hash. HASH is the name of the hash. (Unlike normal C<open>, the first |
1246 | argument is I<not> a filehandle, even though it looks like one). DBNAME | |
aa689395 | 1247 | is the name of the database (without the F<.dir> or F<.pag> extension if |
1248 | any). If the database does not exist, it is created with protection | |
1b3a6178 FC |
1249 | specified by MASK (as modified by the C<umask>). To prevent creation of |
1250 | the database if it doesn't exist, you may specify a MODE | |
1251 | of 0, and the function will return a false value if it | |
1252 | can't find an existing database. If your system supports | |
80d38338 | 1253 | only the older DBM functions, you may make only one C<dbmopen> call in your |
aa689395 | 1254 | program. In older versions of Perl, if your system had neither DBM nor |
19799a22 | 1255 | ndbm, calling C<dbmopen> produced a fatal error; it now falls back to |
aa689395 | 1256 | sdbm(3). |
1257 | ||
1258 | If you don't have write access to the DBM file, you can only read hash | |
1259 | variables, not set them. If you want to test whether you can write, | |
3b10bc60 | 1260 | either use file tests or try setting a dummy hash entry inside an C<eval> |
1261 | to trap the error. | |
a0d0e21e | 1262 | |
19799a22 GS |
1263 | Note that functions such as C<keys> and C<values> may return huge lists |
1264 | when used on large DBM files. You may prefer to use the C<each> | |
a0d0e21e LW |
1265 | function to iterate over large DBM files. Example: |
1266 | ||
1267 | # print out history file offsets | |
1268 | dbmopen(%HIST,'/usr/lib/news/history',0666); | |
1269 | while (($key,$val) = each %HIST) { | |
a9a5a0dc | 1270 | print $key, ' = ', unpack('L',$val), "\n"; |
a0d0e21e LW |
1271 | } |
1272 | dbmclose(%HIST); | |
1273 | ||
cb1a09d0 | 1274 | See also L<AnyDBM_File> for a more general description of the pros and |
184e9718 | 1275 | cons of the various dbm approaches, as well as L<DB_File> for a particularly |
cb1a09d0 | 1276 | rich implementation. |
4633a7c4 | 1277 | |
2b5ab1e7 TC |
1278 | You can control which DBM library you use by loading that library |
1279 | before you call dbmopen(): | |
1280 | ||
1281 | use DB_File; | |
1282 | dbmopen(%NS_Hist, "$ENV{HOME}/.netscape/history.db") | |
a9a5a0dc | 1283 | or die "Can't open netscape history file: $!"; |
2b5ab1e7 | 1284 | |
ea9eb35a BJ |
1285 | Portability issues: L<perlport/dbmopen>. |
1286 | ||
a0d0e21e | 1287 | =item defined EXPR |
d74e8afc | 1288 | X<defined> X<undef> X<undefined> |
a0d0e21e | 1289 | |
54310121 | 1290 | =item defined |
bbce6d69 | 1291 | |
c17cdb72 NC |
1292 | =for Pod::Functions test whether a value, variable, or function is defined |
1293 | ||
2f9daede | 1294 | Returns a Boolean value telling whether EXPR has a value other than |
3b10bc60 | 1295 | the undefined value C<undef>. If EXPR is not present, C<$_> is |
2f9daede TP |
1296 | checked. |
1297 | ||
1298 | Many operations return C<undef> to indicate failure, end of file, | |
1299 | system error, uninitialized variable, and other exceptional | |
1300 | conditions. This function allows you to distinguish C<undef> from | |
1301 | other values. (A simple Boolean test will not distinguish among | |
7660c0ab | 1302 | C<undef>, zero, the empty string, and C<"0">, which are all equally |
2f9daede | 1303 | false.) Note that since C<undef> is a valid scalar, its presence |
19799a22 | 1304 | doesn't I<necessarily> indicate an exceptional condition: C<pop> |
2f9daede TP |
1305 | returns C<undef> when its argument is an empty array, I<or> when the |
1306 | element to return happens to be C<undef>. | |
1307 | ||
f10b0346 GS |
1308 | You may also use C<defined(&func)> to check whether subroutine C<&func> |
1309 | has ever been defined. The return value is unaffected by any forward | |
80d38338 | 1310 | declarations of C<&func>. A subroutine that is not defined |
847c7ebe | 1311 | may still be callable: its package may have an C<AUTOLOAD> method that |
3b10bc60 | 1312 | makes it spring into existence the first time that it is called; see |
847c7ebe | 1313 | L<perlsub>. |
f10b0346 GS |
1314 | |
1315 | Use of C<defined> on aggregates (hashes and arrays) is deprecated. It | |
34169887 | 1316 | used to report whether memory for that aggregate had ever been |
f10b0346 GS |
1317 | allocated. This behavior may disappear in future versions of Perl. |
1318 | You should instead use a simple test for size: | |
1319 | ||
1320 | if (@an_array) { print "has array elements\n" } | |
1321 | if (%a_hash) { print "has hash members\n" } | |
2f9daede TP |
1322 | |
1323 | When used on a hash element, it tells you whether the value is defined, | |
dc848c6f | 1324 | not whether the key exists in the hash. Use L</exists> for the latter |
2f9daede | 1325 | purpose. |
a0d0e21e LW |
1326 | |
1327 | Examples: | |
1328 | ||
8f1da26d | 1329 | print if defined $switch{D}; |
a0d0e21e LW |
1330 | print "$val\n" while defined($val = pop(@ary)); |
1331 | die "Can't readlink $sym: $!" | |
a9a5a0dc | 1332 | unless defined($value = readlink $sym); |
a0d0e21e | 1333 | sub foo { defined &$bar ? &$bar(@_) : die "No bar"; } |
2f9daede | 1334 | $debugging = 0 unless defined $debugging; |
a0d0e21e | 1335 | |
8f1da26d | 1336 | Note: Many folks tend to overuse C<defined> and are then surprised to |
7660c0ab | 1337 | discover that the number C<0> and C<""> (the zero-length string) are, in fact, |
2f9daede | 1338 | defined values. For example, if you say |
a5f75d66 AD |
1339 | |
1340 | "ab" =~ /a(.*)b/; | |
1341 | ||
80d38338 | 1342 | The pattern match succeeds and C<$1> is defined, although it |
cf264981 | 1343 | matched "nothing". It didn't really fail to match anything. Rather, it |
2b5ab1e7 | 1344 | matched something that happened to be zero characters long. This is all |
a5f75d66 | 1345 | very above-board and honest. When a function returns an undefined value, |
2f9daede | 1346 | it's an admission that it couldn't give you an honest answer. So you |
3b10bc60 | 1347 | should use C<defined> only when questioning the integrity of what |
7660c0ab | 1348 | you're trying to do. At other times, a simple comparison to C<0> or C<""> is |
2f9daede TP |
1349 | what you want. |
1350 | ||
dc848c6f | 1351 | See also L</undef>, L</exists>, L</ref>. |
2f9daede | 1352 | |
a0d0e21e | 1353 | =item delete EXPR |
d74e8afc | 1354 | X<delete> |
a0d0e21e | 1355 | |
c17cdb72 NC |
1356 | =for Pod::Functions deletes a value from a hash |
1357 | ||
d0a76353 RS |
1358 | Given an expression that specifies an element or slice of a hash, C<delete> |
1359 | deletes the specified elements from that hash so that exists() on that element | |
1360 | no longer returns true. Setting a hash element to the undefined value does | |
1361 | not remove its key, but deleting it does; see L</exists>. | |
80d38338 | 1362 | |
8f1da26d | 1363 | In list context, returns the value or values deleted, or the last such |
80d38338 | 1364 | element in scalar context. The return list's length always matches that of |
d0a76353 RS |
1365 | the argument list: deleting non-existent elements returns the undefined value |
1366 | in their corresponding positions. | |
80d38338 | 1367 | |
d0a76353 RS |
1368 | delete() may also be used on arrays and array slices, but its behavior is less |
1369 | straightforward. Although exists() will return false for deleted entries, | |
1370 | deleting array elements never changes indices of existing values; use shift() | |
1371 | or splice() for that. However, if all deleted elements fall at the end of an | |
1372 | array, the array's size shrinks to the position of the highest element that | |
1373 | still tests true for exists(), or to 0 if none do. | |
1374 | ||
8f1da26d | 1375 | B<WARNING:> Calling delete on array values is deprecated and likely to |
d0a76353 | 1376 | be removed in a future version of Perl. |
80d38338 TC |
1377 | |
1378 | Deleting from C<%ENV> modifies the environment. Deleting from a hash tied to | |
1379 | a DBM file deletes the entry from the DBM file. Deleting from a C<tied> hash | |
1380 | or array may not necessarily return anything; it depends on the implementation | |
1381 | of the C<tied> package's DELETE method, which may do whatever it pleases. | |
a0d0e21e | 1382 | |
80d38338 TC |
1383 | The C<delete local EXPR> construct localizes the deletion to the current |
1384 | block at run time. Until the block exits, elements locally deleted | |
1385 | temporarily no longer exist. See L<perlsub/"Localized deletion of elements | |
1386 | of composite types">. | |
eba0920a EM |
1387 | |
1388 | %hash = (foo => 11, bar => 22, baz => 33); | |
f7051f2c FC |
1389 | $scalar = delete $hash{foo}; # $scalar is 11 |
1390 | $scalar = delete @hash{qw(foo bar)}; # $scalar is 22 | |
1391 | @array = delete @hash{qw(foo baz)}; # @array is (undef,33) | |
eba0920a | 1392 | |
01020589 | 1393 | The following (inefficiently) deletes all the values of %HASH and @ARRAY: |
a0d0e21e | 1394 | |
5f05dabc | 1395 | foreach $key (keys %HASH) { |
a9a5a0dc | 1396 | delete $HASH{$key}; |
a0d0e21e LW |
1397 | } |
1398 | ||
01020589 | 1399 | foreach $index (0 .. $#ARRAY) { |
a9a5a0dc | 1400 | delete $ARRAY[$index]; |
01020589 GS |
1401 | } |
1402 | ||
1403 | And so do these: | |
5f05dabc | 1404 | |
01020589 GS |
1405 | delete @HASH{keys %HASH}; |
1406 | ||
9740c838 | 1407 | delete @ARRAY[0 .. $#ARRAY]; |
5f05dabc | 1408 | |
80d38338 TC |
1409 | But both are slower than assigning the empty list |
1410 | or undefining %HASH or @ARRAY, which is the customary | |
1411 | way to empty out an aggregate: | |
01020589 | 1412 | |
5ed4f2ec | 1413 | %HASH = (); # completely empty %HASH |
1414 | undef %HASH; # forget %HASH ever existed | |
2b5ab1e7 | 1415 | |
5ed4f2ec | 1416 | @ARRAY = (); # completely empty @ARRAY |
1417 | undef @ARRAY; # forget @ARRAY ever existed | |
2b5ab1e7 | 1418 | |
80d38338 TC |
1419 | The EXPR can be arbitrarily complicated provided its |
1420 | final operation is an element or slice of an aggregate: | |
a0d0e21e LW |
1421 | |
1422 | delete $ref->[$x][$y]{$key}; | |
5f05dabc | 1423 | delete @{$ref->[$x][$y]}{$key1, $key2, @morekeys}; |
a0d0e21e | 1424 | |
01020589 GS |
1425 | delete $ref->[$x][$y][$index]; |
1426 | delete @{$ref->[$x][$y]}[$index1, $index2, @moreindices]; | |
1427 | ||
a0d0e21e | 1428 | =item die LIST |
d74e8afc | 1429 | X<die> X<throw> X<exception> X<raise> X<$@> X<abort> |
a0d0e21e | 1430 | |
c17cdb72 NC |
1431 | =for Pod::Functions raise an exception or bail out |
1432 | ||
391b733c | 1433 | C<die> raises an exception. Inside an C<eval> the error message is stuffed |
4c050ad5 NC |
1434 | into C<$@> and the C<eval> is terminated with the undefined value. |
1435 | If the exception is outside of all enclosing C<eval>s, then the uncaught | |
391b733c | 1436 | exception prints LIST to C<STDERR> and exits with a non-zero value. If you |
96090e4f | 1437 | need to exit the process with a specific exit code, see L</exit>. |
a0d0e21e LW |
1438 | |
1439 | Equivalent examples: | |
1440 | ||
1441 | die "Can't cd to spool: $!\n" unless chdir '/usr/spool/news'; | |
54310121 | 1442 | chdir '/usr/spool/news' or die "Can't cd to spool: $!\n" |
a0d0e21e | 1443 | |
ccac6780 | 1444 | If the last element of LIST does not end in a newline, the current |
df37ec69 WW |
1445 | script line number and input line number (if any) are also printed, |
1446 | and a newline is supplied. Note that the "input line number" (also | |
1447 | known as "chunk") is subject to whatever notion of "line" happens to | |
1448 | be currently in effect, and is also available as the special variable | |
1449 | C<$.>. See L<perlvar/"$/"> and L<perlvar/"$.">. | |
1450 | ||
1451 | Hint: sometimes appending C<", stopped"> to your message will cause it | |
1452 | to make better sense when the string C<"at foo line 123"> is appended. | |
1453 | Suppose you are running script "canasta". | |
a0d0e21e LW |
1454 | |
1455 | die "/etc/games is no good"; | |
1456 | die "/etc/games is no good, stopped"; | |
1457 | ||
1458 | produce, respectively | |
1459 | ||
1460 | /etc/games is no good at canasta line 123. | |
1461 | /etc/games is no good, stopped at canasta line 123. | |
1462 | ||
a96d0188 | 1463 | If the output is empty and C<$@> already contains a value (typically from a |
7660c0ab | 1464 | previous eval) that value is reused after appending C<"\t...propagated">. |
fb73857a | 1465 | This is useful for propagating exceptions: |
1466 | ||
1467 | eval { ... }; | |
1468 | die unless $@ =~ /Expected exception/; | |
1469 | ||
a96d0188 | 1470 | If the output is empty and C<$@> contains an object reference that has a |
ad216e65 JH |
1471 | C<PROPAGATE> method, that method will be called with additional file |
1472 | and line number parameters. The return value replaces the value in | |
34169887 | 1473 | C<$@>; i.e., as if C<< $@ = eval { $@->PROPAGATE(__FILE__, __LINE__) }; >> |
ad216e65 JH |
1474 | were called. |
1475 | ||
7660c0ab | 1476 | If C<$@> is empty then the string C<"Died"> is used. |
fb73857a | 1477 | |
4c050ad5 NC |
1478 | If an uncaught exception results in interpreter exit, the exit code is |
1479 | determined from the values of C<$!> and C<$?> with this pseudocode: | |
1480 | ||
1481 | exit $! if $!; # errno | |
1482 | exit $? >> 8 if $? >> 8; # child exit status | |
1483 | exit 255; # last resort | |
1484 | ||
1485 | The intent is to squeeze as much possible information about the likely cause | |
391b733c FC |
1486 | into the limited space of the system exit |
1487 | code. However, as C<$!> is the value | |
4c050ad5 NC |
1488 | of C's C<errno>, which can be set by any system call, this means that the value |
1489 | of the exit code used by C<die> can be non-predictable, so should not be relied | |
1490 | upon, other than to be non-zero. | |
1491 | ||
80d38338 TC |
1492 | You can also call C<die> with a reference argument, and if this is trapped |
1493 | within an C<eval>, C<$@> contains that reference. This permits more | |
1494 | elaborate exception handling using objects that maintain arbitrary state | |
1495 | about the exception. Such a scheme is sometimes preferable to matching | |
1496 | particular string values of C<$@> with regular expressions. Because C<$@> | |
1497 | is a global variable and C<eval> may be used within object implementations, | |
1498 | be careful that analyzing the error object doesn't replace the reference in | |
1499 | the global variable. It's easiest to make a local copy of the reference | |
1500 | before any manipulations. Here's an example: | |
52531d10 | 1501 | |
80d38338 | 1502 | use Scalar::Util "blessed"; |
da279afe | 1503 | |
52531d10 | 1504 | eval { ... ; die Some::Module::Exception->new( FOO => "bar" ) }; |
746d7dd7 | 1505 | if (my $ev_err = $@) { |
f7051f2c FC |
1506 | if (blessed($ev_err) |
1507 | && $ev_err->isa("Some::Module::Exception")) { | |
52531d10 GS |
1508 | # handle Some::Module::Exception |
1509 | } | |
1510 | else { | |
1511 | # handle all other possible exceptions | |
1512 | } | |
1513 | } | |
1514 | ||
3b10bc60 | 1515 | Because Perl stringifies uncaught exception messages before display, |
80d38338 | 1516 | you'll probably want to overload stringification operations on |
52531d10 GS |
1517 | exception objects. See L<overload> for details about that. |
1518 | ||
19799a22 GS |
1519 | You can arrange for a callback to be run just before the C<die> |
1520 | does its deed, by setting the C<$SIG{__DIE__}> hook. The associated | |
3b10bc60 | 1521 | handler is called with the error text and can change the error |
19799a22 | 1522 | message, if it sees fit, by calling C<die> again. See |
96090e4f | 1523 | L<perlvar/%SIG> for details on setting C<%SIG> entries, and |
cf264981 | 1524 | L<"eval BLOCK"> for some examples. Although this feature was |
19799a22 | 1525 | to be run only right before your program was to exit, this is not |
3b10bc60 | 1526 | currently so: the C<$SIG{__DIE__}> hook is currently called |
19799a22 GS |
1527 | even inside eval()ed blocks/strings! If one wants the hook to do |
1528 | nothing in such situations, put | |
fb73857a | 1529 | |
5ed4f2ec | 1530 | die @_ if $^S; |
fb73857a | 1531 | |
19799a22 GS |
1532 | as the first line of the handler (see L<perlvar/$^S>). Because |
1533 | this promotes strange action at a distance, this counterintuitive | |
b76cc8ba | 1534 | behavior may be fixed in a future release. |
774d564b | 1535 | |
4c050ad5 NC |
1536 | See also exit(), warn(), and the Carp module. |
1537 | ||
a0d0e21e | 1538 | =item do BLOCK |
d74e8afc | 1539 | X<do> X<block> |
a0d0e21e | 1540 | |
c17cdb72 NC |
1541 | =for Pod::Functions turn a BLOCK into a TERM |
1542 | ||
a0d0e21e | 1543 | Not really a function. Returns the value of the last command in the |
6b275a1f RGS |
1544 | sequence of commands indicated by BLOCK. When modified by the C<while> or |
1545 | C<until> loop modifier, executes the BLOCK once before testing the loop | |
391b733c | 1546 | condition. (On other statements the loop modifiers test the conditional |
6b275a1f | 1547 | first.) |
a0d0e21e | 1548 | |
4968c1e4 | 1549 | C<do BLOCK> does I<not> count as a loop, so the loop control statements |
2b5ab1e7 TC |
1550 | C<next>, C<last>, or C<redo> cannot be used to leave or restart the block. |
1551 | See L<perlsyn> for alternative strategies. | |
4968c1e4 | 1552 | |
a0d0e21e | 1553 | =item do EXPR |
d74e8afc | 1554 | X<do> |
a0d0e21e LW |
1555 | |
1556 | Uses the value of EXPR as a filename and executes the contents of the | |
ea63ef19 | 1557 | file as a Perl script. |
a0d0e21e LW |
1558 | |
1559 | do 'stat.pl'; | |
1560 | ||
c319391a | 1561 | is largely like |
a0d0e21e | 1562 | |
986b19de | 1563 | eval `cat stat.pl`; |
a0d0e21e | 1564 | |
c319391a AC |
1565 | except that it's more concise, runs no external processes, keeps track of |
1566 | the current | |
96090e4f LB |
1567 | filename for error messages, searches the C<@INC> directories, and updates |
1568 | C<%INC> if the file is found. See L<perlvar/@INC> and L<perlvar/%INC> for | |
1569 | these variables. It also differs in that code evaluated with C<do FILENAME> | |
2b5ab1e7 TC |
1570 | cannot see lexicals in the enclosing scope; C<eval STRING> does. It's the |
1571 | same, however, in that it does reparse the file every time you call it, | |
1572 | so you probably don't want to do this inside a loop. | |
a0d0e21e | 1573 | |
8f1da26d | 1574 | If C<do> can read the file but cannot compile it, it returns C<undef> and sets |
9dc513c5 DG |
1575 | an error message in C<$@>. If C<do> cannot read the file, it returns undef |
1576 | and sets C<$!> to the error. Always check C<$@> first, as compilation | |
1577 | could fail in a way that also sets C<$!>. If the file is successfully | |
1578 | compiled, C<do> returns the value of the last expression evaluated. | |
8e30cc93 | 1579 | |
80d38338 | 1580 | Inclusion of library modules is better done with the |
19799a22 | 1581 | C<use> and C<require> operators, which also do automatic error checking |
4633a7c4 | 1582 | and raise an exception if there's a problem. |
a0d0e21e | 1583 | |
5a964f20 TC |
1584 | You might like to use C<do> to read in a program configuration |
1585 | file. Manual error checking can be done this way: | |
1586 | ||
b76cc8ba | 1587 | # read in config files: system first, then user |
f86cebdf | 1588 | for $file ("/share/prog/defaults.rc", |
b76cc8ba | 1589 | "$ENV{HOME}/.someprogrc") |
a9a5a0dc VP |
1590 | { |
1591 | unless ($return = do $file) { | |
1592 | warn "couldn't parse $file: $@" if $@; | |
1593 | warn "couldn't do $file: $!" unless defined $return; | |
1594 | warn "couldn't run $file" unless $return; | |
1595 | } | |
5a964f20 TC |
1596 | } |
1597 | ||
a0d0e21e | 1598 | =item dump LABEL |
d74e8afc | 1599 | X<dump> X<core> X<undump> |
a0d0e21e | 1600 | |
8a7e748e FC |
1601 | =item dump EXPR |
1602 | ||
1614b0e3 JD |
1603 | =item dump |
1604 | ||
c17cdb72 NC |
1605 | =for Pod::Functions create an immediate core dump |
1606 | ||
19799a22 GS |
1607 | This function causes an immediate core dump. See also the B<-u> |
1608 | command-line switch in L<perlrun>, which does the same thing. | |
1609 | Primarily this is so that you can use the B<undump> program (not | |
1610 | supplied) to turn your core dump into an executable binary after | |
1611 | having initialized all your variables at the beginning of the | |
1612 | program. When the new binary is executed it will begin by executing | |
1613 | a C<goto LABEL> (with all the restrictions that C<goto> suffers). | |
1614 | Think of it as a goto with an intervening core dump and reincarnation. | |
8a7e748e FC |
1615 | If C<LABEL> is omitted, restarts the program from the top. The |
1616 | C<dump EXPR> form, available starting in Perl 5.18.0, allows a name to be | |
1617 | computed at run time, being otherwise identical to C<dump LABEL>. | |
19799a22 GS |
1618 | |
1619 | B<WARNING>: Any files opened at the time of the dump will I<not> | |
1620 | be open any more when the program is reincarnated, with possible | |
80d38338 | 1621 | resulting confusion by Perl. |
19799a22 | 1622 | |
59f521f4 | 1623 | This function is now largely obsolete, mostly because it's very hard to |
391b733c | 1624 | convert a core file into an executable. That's why you should now invoke |
59f521f4 | 1625 | it as C<CORE::dump()>, if you don't want to be warned against a possible |
ac206dc8 | 1626 | typo. |
19799a22 | 1627 | |
2ba1f20a FC |
1628 | Unlike most named operators, this has the same precedence as assignment. |
1629 | It is also exempt from the looks-like-a-function rule, so | |
1630 | C<dump ("foo")."bar"> will cause "bar" to be part of the argument to | |
1631 | C<dump>. | |
1632 | ||
ea9eb35a BJ |
1633 | Portability issues: L<perlport/dump>. |
1634 | ||
532eee96 | 1635 | =item each HASH |
d74e8afc | 1636 | X<each> X<hash, iterator> |
aa689395 | 1637 | |
532eee96 | 1638 | =item each ARRAY |
aeedbbed NC |
1639 | X<array, iterator> |
1640 | ||
f5a93a43 TC |
1641 | =item each EXPR |
1642 | ||
c17cdb72 NC |
1643 | =for Pod::Functions retrieve the next key/value pair from a hash |
1644 | ||
bade7fbc TC |
1645 | When called on a hash in list context, returns a 2-element list |
1646 | consisting of the key and value for the next element of a hash. In Perl | |
1647 | 5.12 and later only, it will also return the index and value for the next | |
1648 | element of an array so that you can iterate over it; older Perls consider | |
1649 | this a syntax error. When called in scalar context, returns only the key | |
1650 | (not the value) in a hash, or the index in an array. | |
2f9daede | 1651 | |
aeedbbed | 1652 | Hash entries are returned in an apparently random order. The actual random |
7bf59113 | 1653 | order is specific to a given hash; the exact same series of operations |
7161e5c2 | 1654 | on two hashes may result in a different order for each hash. Any insertion |
7bf59113 YO |
1655 | into the hash may change the order, as will any deletion, with the exception |
1656 | that the most recent key returned by C<each> or C<keys> may be deleted | |
7161e5c2 | 1657 | without changing the order. So long as a given hash is unmodified you may |
7bf59113 | 1658 | rely on C<keys>, C<values> and C<each> to repeatedly return the same order |
7161e5c2 FC |
1659 | as each other. See L<perlsec/"Algorithmic Complexity Attacks"> for |
1660 | details on why hash order is randomized. Aside from the guarantees | |
7bf59113 YO |
1661 | provided here the exact details of Perl's hash algorithm and the hash |
1662 | traversal order are subject to change in any release of Perl. | |
ab192400 | 1663 | |
80d38338 TC |
1664 | After C<each> has returned all entries from the hash or array, the next |
1665 | call to C<each> returns the empty list in list context and C<undef> in | |
bade7fbc TC |
1666 | scalar context; the next call following I<that> one restarts iteration. |
1667 | Each hash or array has its own internal iterator, accessed by C<each>, | |
1668 | C<keys>, and C<values>. The iterator is implicitly reset when C<each> has | |
1669 | reached the end as just described; it can be explicitly reset by calling | |
1670 | C<keys> or C<values> on the hash or array. If you add or delete a hash's | |
49daec89 DM |
1671 | elements while iterating over it, the effect on the iterator is |
1672 | unspecified; for example, entries may be skipped or duplicated--so don't | |
1673 | do that. Exception: In the current implementation, it is always safe to | |
1674 | delete the item most recently returned by C<each()>, so the following code | |
1675 | works properly: | |
74fc8b5f MJD |
1676 | |
1677 | while (($key, $value) = each %hash) { | |
1678 | print $key, "\n"; | |
1679 | delete $hash{$key}; # This is safe | |
1680 | } | |
aa689395 | 1681 | |
80d38338 | 1682 | This prints out your environment like the printenv(1) program, |
3b10bc60 | 1683 | but in a different order: |
a0d0e21e LW |
1684 | |
1685 | while (($key,$value) = each %ENV) { | |
a9a5a0dc | 1686 | print "$key=$value\n"; |
a0d0e21e LW |
1687 | } |
1688 | ||
f5a93a43 TC |
1689 | Starting with Perl 5.14, C<each> can take a scalar EXPR, which must hold |
1690 | reference to an unblessed hash or array. The argument will be dereferenced | |
1691 | automatically. This aspect of C<each> is considered highly experimental. | |
1692 | The exact behaviour may change in a future version of Perl. | |
cba5a3b0 DG |
1693 | |
1694 | while (($key,$value) = each $hashref) { ... } | |
1695 | ||
e6a0db3e FC |
1696 | As of Perl 5.18 you can use a bare C<each> in a C<while> loop, |
1697 | which will set C<$_> on every iteration. | |
1698 | ||
1699 | while(each %ENV) { | |
1700 | print "$_=$ENV{$_}\n"; | |
1701 | } | |
1702 | ||
bade7fbc TC |
1703 | To avoid confusing would-be users of your code who are running earlier |
1704 | versions of Perl with mysterious syntax errors, put this sort of thing at | |
1705 | the top of your file to signal that your code will work I<only> on Perls of | |
1706 | a recent vintage: | |
1707 | ||
1708 | use 5.012; # so keys/values/each work on arrays | |
1709 | use 5.014; # so keys/values/each work on scalars (experimental) | |
e6a0db3e | 1710 | use 5.018; # so each assigns to $_ in a lone while test |
bade7fbc | 1711 | |
8f1da26d | 1712 | See also C<keys>, C<values>, and C<sort>. |
a0d0e21e LW |
1713 | |
1714 | =item eof FILEHANDLE | |
d74e8afc ITB |
1715 | X<eof> |
1716 | X<end of file> | |
1717 | X<end-of-file> | |
a0d0e21e | 1718 | |
4633a7c4 LW |
1719 | =item eof () |
1720 | ||
a0d0e21e LW |
1721 | =item eof |
1722 | ||
c17cdb72 NC |
1723 | =for Pod::Functions test a filehandle for its end |
1724 | ||
8f1da26d | 1725 | Returns 1 if the next read on FILEHANDLE will return end of file I<or> if |
a0d0e21e | 1726 | FILEHANDLE is not open. FILEHANDLE may be an expression whose value |
5a964f20 | 1727 | gives the real filehandle. (Note that this function actually |
80d38338 | 1728 | reads a character and then C<ungetc>s it, so isn't useful in an |
748a9306 | 1729 | interactive context.) Do not read from a terminal file (or call |
19799a22 | 1730 | C<eof(FILEHANDLE)> on it) after end-of-file is reached. File types such |
748a9306 LW |
1731 | as terminals may lose the end-of-file condition if you do. |
1732 | ||
820475bd | 1733 | An C<eof> without an argument uses the last file read. Using C<eof()> |
80d38338 | 1734 | with empty parentheses is different. It refers to the pseudo file |
820475bd | 1735 | formed from the files listed on the command line and accessed via the |
61eff3bc JH |
1736 | C<< <> >> operator. Since C<< <> >> isn't explicitly opened, |
1737 | as a normal filehandle is, an C<eof()> before C<< <> >> has been | |
820475bd | 1738 | used will cause C<@ARGV> to be examined to determine if input is |
67408cae | 1739 | available. Similarly, an C<eof()> after C<< <> >> has returned |
efdd0218 RB |
1740 | end-of-file will assume you are processing another C<@ARGV> list, |
1741 | and if you haven't set C<@ARGV>, will read input from C<STDIN>; | |
1742 | see L<perlop/"I/O Operators">. | |
820475bd | 1743 | |
61eff3bc | 1744 | In a C<< while (<>) >> loop, C<eof> or C<eof(ARGV)> can be used to |
8f1da26d TC |
1745 | detect the end of each file, whereas C<eof()> will detect the end |
1746 | of the very last file only. Examples: | |
a0d0e21e | 1747 | |
748a9306 LW |
1748 | # reset line numbering on each input file |
1749 | while (<>) { | |
a9a5a0dc VP |
1750 | next if /^\s*#/; # skip comments |
1751 | print "$.\t$_"; | |
5a964f20 | 1752 | } continue { |
a9a5a0dc | 1753 | close ARGV if eof; # Not eof()! |
748a9306 LW |
1754 | } |
1755 | ||
a0d0e21e LW |
1756 | # insert dashes just before last line of last file |
1757 | while (<>) { | |
a9a5a0dc VP |
1758 | if (eof()) { # check for end of last file |
1759 | print "--------------\n"; | |
1760 | } | |
1761 | print; | |
f7051f2c | 1762 | last if eof(); # needed if we're reading from a terminal |
a0d0e21e LW |
1763 | } |
1764 | ||
a0d0e21e | 1765 | Practical hint: you almost never need to use C<eof> in Perl, because the |
8f1da26d TC |
1766 | input operators typically return C<undef> when they run out of data or |
1767 | encounter an error. | |
a0d0e21e LW |
1768 | |
1769 | =item eval EXPR | |
d74e8afc | 1770 | X<eval> X<try> X<catch> X<evaluate> X<parse> X<execute> |
f723aae1 | 1771 | X<error, handling> X<exception, handling> |
a0d0e21e LW |
1772 | |
1773 | =item eval BLOCK | |
1774 | ||
ce2984c3 PF |
1775 | =item eval |
1776 | ||
c17cdb72 NC |
1777 | =for Pod::Functions catch exceptions or compile and run code |
1778 | ||
798dc914 KW |
1779 | In the first form, often referred to as a "string eval", the return |
1780 | value of EXPR is parsed and executed as if it | |
c7cc6f1c | 1781 | were a little Perl program. The value of the expression (which is itself |
8f1da26d | 1782 | determined within scalar context) is first parsed, and if there were no |
2341804c | 1783 | errors, executed as a block within the lexical context of the current Perl |
df4833a8 | 1784 | program. This means, that in particular, any outer lexical variables are |
2341804c DM |
1785 | visible to it, and any package variable settings or subroutine and format |
1786 | definitions remain afterwards. | |
1787 | ||
1788 | Note that the value is parsed every time the C<eval> executes. | |
be3174d2 GS |
1789 | If EXPR is omitted, evaluates C<$_>. This form is typically used to |
1790 | delay parsing and subsequent execution of the text of EXPR until run time. | |
c7cc6f1c | 1791 | |
7289c5e6 FC |
1792 | If the C<unicode_eval> feature is enabled (which is the default under a |
1793 | C<use 5.16> or higher declaration), EXPR or C<$_> is treated as a string of | |
1794 | characters, so C<use utf8> declarations have no effect, and source filters | |
1795 | are forbidden. In the absence of the C<unicode_eval> feature, the string | |
1796 | will sometimes be treated as characters and sometimes as bytes, depending | |
1797 | on the internal encoding, and source filters activated within the C<eval> | |
1798 | exhibit the erratic, but historical, behaviour of affecting some outer file | |
1799 | scope that is still compiling. See also the L</evalbytes> keyword, which | |
1800 | always treats its input as a byte stream and works properly with source | |
1801 | filters, and the L<feature> pragma. | |
1802 | ||
798dc914 KW |
1803 | Problems can arise if the string expands a scalar containing a floating |
1804 | point number. That scalar can expand to letters, such as C<"NaN"> or | |
1805 | C<"Infinity">; or, within the scope of a C<use locale>, the decimal | |
1806 | point character may be something other than a dot (such as a comma). | |
1807 | None of these are likely to parse as you are likely expecting. | |
1808 | ||
c7cc6f1c | 1809 | In the second form, the code within the BLOCK is parsed only once--at the |
cf264981 | 1810 | same time the code surrounding the C<eval> itself was parsed--and executed |
c7cc6f1c GS |
1811 | within the context of the current Perl program. This form is typically |
1812 | used to trap exceptions more efficiently than the first (see below), while | |
1813 | also providing the benefit of checking the code within BLOCK at compile | |
1814 | time. | |
1815 | ||
1816 | The final semicolon, if any, may be omitted from the value of EXPR or within | |
1817 | the BLOCK. | |
1818 | ||
1819 | In both forms, the value returned is the value of the last expression | |
5a964f20 | 1820 | evaluated inside the mini-program; a return statement may be also used, just |
c7cc6f1c | 1821 | as with subroutines. The expression providing the return value is evaluated |
cf264981 SP |
1822 | in void, scalar, or list context, depending on the context of the C<eval> |
1823 | itself. See L</wantarray> for more on how the evaluation context can be | |
1824 | determined. | |
a0d0e21e | 1825 | |
19799a22 | 1826 | If there is a syntax error or runtime error, or a C<die> statement is |
8f1da26d | 1827 | executed, C<eval> returns C<undef> in scalar context |
774b80e8 FC |
1828 | or an empty list in list context, and C<$@> is set to the error |
1829 | message. (Prior to 5.16, a bug caused C<undef> to be returned | |
1830 | in list context for syntax errors, but not for runtime errors.) | |
1831 | If there was no error, C<$@> is set to the empty string. A | |
9cc672d4 FC |
1832 | control flow operator like C<last> or C<goto> can bypass the setting of |
1833 | C<$@>. Beware that using C<eval> neither silences Perl from printing | |
c7cc6f1c | 1834 | warnings to STDERR, nor does it stuff the text of warning messages into C<$@>. |
d9984052 A |
1835 | To do either of those, you have to use the C<$SIG{__WARN__}> facility, or |
1836 | turn off warnings inside the BLOCK or EXPR using S<C<no warnings 'all'>>. | |
1837 | See L</warn>, L<perlvar>, L<warnings> and L<perllexwarn>. | |
a0d0e21e | 1838 | |
19799a22 GS |
1839 | Note that, because C<eval> traps otherwise-fatal errors, it is useful for |
1840 | determining whether a particular feature (such as C<socket> or C<symlink>) | |
82bcec1b | 1841 | is implemented. It is also Perl's exception-trapping mechanism, where |
a0d0e21e LW |
1842 | the die operator is used to raise exceptions. |
1843 | ||
5f1da31c NT |
1844 | If you want to trap errors when loading an XS module, some problems with |
1845 | the binary interface (such as Perl version skew) may be fatal even with | |
df4833a8 | 1846 | C<eval> unless C<$ENV{PERL_DL_NONLAZY}> is set. See L<perlrun>. |
5f1da31c | 1847 | |
a0d0e21e LW |
1848 | If the code to be executed doesn't vary, you may use the eval-BLOCK |
1849 | form to trap run-time errors without incurring the penalty of | |
1850 | recompiling each time. The error, if any, is still returned in C<$@>. | |
1851 | Examples: | |
1852 | ||
54310121 | 1853 | # make divide-by-zero nonfatal |
a0d0e21e LW |
1854 | eval { $answer = $a / $b; }; warn $@ if $@; |
1855 | ||
1856 | # same thing, but less efficient | |
1857 | eval '$answer = $a / $b'; warn $@ if $@; | |
1858 | ||
1859 | # a compile-time error | |
5ed4f2ec | 1860 | eval { $answer = }; # WRONG |
a0d0e21e LW |
1861 | |
1862 | # a run-time error | |
5ed4f2ec | 1863 | eval '$answer ='; # sets $@ |
a0d0e21e | 1864 | |
cf264981 SP |
1865 | Using the C<eval{}> form as an exception trap in libraries does have some |
1866 | issues. Due to the current arguably broken state of C<__DIE__> hooks, you | |
1867 | may wish not to trigger any C<__DIE__> hooks that user code may have installed. | |
2b5ab1e7 | 1868 | You can use the C<local $SIG{__DIE__}> construct for this purpose, |
80d38338 | 1869 | as this example shows: |
774d564b | 1870 | |
80d38338 | 1871 | # a private exception trap for divide-by-zero |
f86cebdf GS |
1872 | eval { local $SIG{'__DIE__'}; $answer = $a / $b; }; |
1873 | warn $@ if $@; | |
774d564b | 1874 | |
1875 | This is especially significant, given that C<__DIE__> hooks can call | |
19799a22 | 1876 | C<die> again, which has the effect of changing their error messages: |
774d564b | 1877 | |
1878 | # __DIE__ hooks may modify error messages | |
1879 | { | |
f86cebdf GS |
1880 | local $SIG{'__DIE__'} = |
1881 | sub { (my $x = $_[0]) =~ s/foo/bar/g; die $x }; | |
c7cc6f1c GS |
1882 | eval { die "foo lives here" }; |
1883 | print $@ if $@; # prints "bar lives here" | |
774d564b | 1884 | } |
1885 | ||
19799a22 | 1886 | Because this promotes action at a distance, this counterintuitive behavior |
2b5ab1e7 TC |
1887 | may be fixed in a future release. |
1888 | ||
19799a22 | 1889 | With an C<eval>, you should be especially careful to remember what's |
a0d0e21e LW |
1890 | being looked at when: |
1891 | ||
5ed4f2ec | 1892 | eval $x; # CASE 1 |
1893 | eval "$x"; # CASE 2 | |
a0d0e21e | 1894 | |
5ed4f2ec | 1895 | eval '$x'; # CASE 3 |
1896 | eval { $x }; # CASE 4 | |
a0d0e21e | 1897 | |
5ed4f2ec | 1898 | eval "\$$x++"; # CASE 5 |
1899 | $$x++; # CASE 6 | |
a0d0e21e | 1900 | |
2f9daede | 1901 | Cases 1 and 2 above behave identically: they run the code contained in |
19799a22 | 1902 | the variable $x. (Although case 2 has misleading double quotes making |
2f9daede | 1903 | the reader wonder what else might be happening (nothing is).) Cases 3 |
7660c0ab | 1904 | and 4 likewise behave in the same way: they run the code C<'$x'>, which |
19799a22 | 1905 | does nothing but return the value of $x. (Case 4 is preferred for |
2f9daede TP |
1906 | purely visual reasons, but it also has the advantage of compiling at |
1907 | compile-time instead of at run-time.) Case 5 is a place where | |
19799a22 | 1908 | normally you I<would> like to use double quotes, except that in this |
2f9daede TP |
1909 | particular situation, you can just use symbolic references instead, as |
1910 | in case 6. | |
a0d0e21e | 1911 | |
b6538e4f | 1912 | Before Perl 5.14, the assignment to C<$@> occurred before restoration |
bade7fbc | 1913 | of localized variables, which means that for your code to run on older |
b208c909 | 1914 | versions, a temporary is required if you want to mask some but not all |
8a5a710d DN |
1915 | errors: |
1916 | ||
1917 | # alter $@ on nefarious repugnancy only | |
1918 | { | |
1919 | my $e; | |
1920 | { | |
f7051f2c FC |
1921 | local $@; # protect existing $@ |
1922 | eval { test_repugnancy() }; | |
1923 | # $@ =~ /nefarious/ and die $@; # Perl 5.14 and higher only | |
1924 | $@ =~ /nefarious/ and $e = $@; | |
8a5a710d DN |
1925 | } |
1926 | die $e if defined $e | |
1927 | } | |
1928 | ||
4968c1e4 | 1929 | C<eval BLOCK> does I<not> count as a loop, so the loop control statements |
2b5ab1e7 | 1930 | C<next>, C<last>, or C<redo> cannot be used to leave or restart the block. |
4968c1e4 | 1931 | |
4f00fc7e FC |
1932 | An C<eval ''> executed within a subroutine defined |
1933 | in the C<DB> package doesn't see the usual | |
3b10bc60 | 1934 | surrounding lexical scope, but rather the scope of the first non-DB piece |
df4833a8 | 1935 | of code that called it. You don't normally need to worry about this unless |
3b10bc60 | 1936 | you are writing a Perl debugger. |
d819b83a | 1937 | |
7289c5e6 FC |
1938 | =item evalbytes EXPR |
1939 | X<evalbytes> | |
1940 | ||
1941 | =item evalbytes | |
1942 | ||
d9b04284 | 1943 | =for Pod::Functions +evalbytes similar to string eval, but intend to parse a bytestream |
c17cdb72 | 1944 | |
7289c5e6 FC |
1945 | This function is like L</eval> with a string argument, except it always |
1946 | parses its argument, or C<$_> if EXPR is omitted, as a string of bytes. A | |
1947 | string containing characters whose ordinal value exceeds 255 results in an | |
1948 | error. Source filters activated within the evaluated code apply to the | |
1949 | code itself. | |
1950 | ||
1951 | This function is only available under the C<evalbytes> feature, a | |
1952 | C<use v5.16> (or higher) declaration, or with a C<CORE::> prefix. See | |
1953 | L<feature> for more information. | |
1954 | ||
a0d0e21e | 1955 | =item exec LIST |
d74e8afc | 1956 | X<exec> X<execute> |
a0d0e21e | 1957 | |
8bf3b016 GS |
1958 | =item exec PROGRAM LIST |
1959 | ||
c17cdb72 NC |
1960 | =for Pod::Functions abandon this program to run another |
1961 | ||
3b10bc60 | 1962 | The C<exec> function executes a system command I<and never returns>; |
19799a22 GS |
1963 | use C<system> instead of C<exec> if you want it to return. It fails and |
1964 | returns false only if the command does not exist I<and> it is executed | |
fb73857a | 1965 | directly instead of via your system's command shell (see below). |
a0d0e21e | 1966 | |
19799a22 | 1967 | Since it's a common mistake to use C<exec> instead of C<system>, Perl |
4642e50d EB |
1968 | warns you if C<exec> is called in void context and if there is a following |
1969 | statement that isn't C<die>, C<warn>, or C<exit> (if C<-w> is set--but | |
1970 | you always do that, right?). If you I<really> want to follow an C<exec> | |
1971 | with some other statement, you can use one of these styles to avoid the warning: | |
55d729e4 | 1972 | |
5a964f20 TC |
1973 | exec ('foo') or print STDERR "couldn't exec foo: $!"; |
1974 | { exec ('foo') }; print STDERR "couldn't exec foo: $!"; | |
55d729e4 | 1975 | |
667eac0c RS |
1976 | If there is more than one argument in LIST, this calls execvp(3) with the |
1977 | arguments in LIST. If there is only one element in LIST, the argument is | |
1978 | checked for shell metacharacters, and if there are any, the entire | |
1979 | argument is passed to the system's command shell for parsing (this is | |
1980 | C</bin/sh -c> on Unix platforms, but varies on other platforms). If | |
1981 | there are no shell metacharacters in the argument, it is split into words | |
1982 | and passed directly to C<execvp>, which is more efficient. Examples: | |
a0d0e21e | 1983 | |
19799a22 GS |
1984 | exec '/bin/echo', 'Your arguments are: ', @ARGV; |
1985 | exec "sort $outfile | uniq"; | |
a0d0e21e LW |
1986 | |
1987 | If you don't really want to execute the first argument, but want to lie | |
1988 | to the program you are executing about its own name, you can specify | |
1989 | the program you actually want to run as an "indirect object" (without a | |
1990 | comma) in front of the LIST. (This always forces interpretation of the | |
54310121 | 1991 | LIST as a multivalued list, even if there is only a single scalar in |
a0d0e21e LW |
1992 | the list.) Example: |
1993 | ||
1994 | $shell = '/bin/csh'; | |
5ed4f2ec | 1995 | exec $shell '-sh'; # pretend it's a login shell |
a0d0e21e LW |
1996 | |
1997 | or, more directly, | |
1998 | ||
5ed4f2ec | 1999 | exec {'/bin/csh'} '-sh'; # pretend it's a login shell |
a0d0e21e | 2000 | |
3b10bc60 | 2001 | When the arguments get executed via the system shell, results are |
2002 | subject to its quirks and capabilities. See L<perlop/"`STRING`"> | |
bb32b41a GS |
2003 | for details. |
2004 | ||
19799a22 GS |
2005 | Using an indirect object with C<exec> or C<system> is also more |
2006 | secure. This usage (which also works fine with system()) forces | |
2007 | interpretation of the arguments as a multivalued list, even if the | |
2008 | list had just one argument. That way you're safe from the shell | |
2009 | expanding wildcards or splitting up words with whitespace in them. | |
5a964f20 TC |
2010 | |
2011 | @args = ( "echo surprise" ); | |
2012 | ||
2b5ab1e7 | 2013 | exec @args; # subject to shell escapes |
f86cebdf | 2014 | # if @args == 1 |
2b5ab1e7 | 2015 | exec { $args[0] } @args; # safe even with one-arg list |
5a964f20 TC |
2016 | |
2017 | The first version, the one without the indirect object, ran the I<echo> | |
80d38338 TC |
2018 | program, passing it C<"surprise"> an argument. The second version didn't; |
2019 | it tried to run a program named I<"echo surprise">, didn't find it, and set | |
2020 | C<$?> to a non-zero value indicating failure. | |
5a964f20 | 2021 | |
e9fa405d BF |
2022 | Perl attempts to flush all files opened for output before the exec, |
2023 | but this may not be supported on some platforms (see L<perlport>). | |
2024 | To be safe, you may need to set C<$|> ($AUTOFLUSH in English) or | |
2025 | call the C<autoflush()> method of C<IO::Handle> on any open handles | |
2026 | to avoid lost output. | |
0f897271 | 2027 | |
80d38338 TC |
2028 | Note that C<exec> will not call your C<END> blocks, nor will it invoke |
2029 | C<DESTROY> methods on your objects. | |
7660c0ab | 2030 | |
ea9eb35a BJ |
2031 | Portability issues: L<perlport/exec>. |
2032 | ||
a0d0e21e | 2033 | =item exists EXPR |
d74e8afc | 2034 | X<exists> X<autovivification> |
a0d0e21e | 2035 | |
c17cdb72 NC |
2036 | =for Pod::Functions test whether a hash key is present |
2037 | ||
d0a76353 RS |
2038 | Given an expression that specifies an element of a hash, returns true if the |
2039 | specified element in the hash has ever been initialized, even if the | |
2040 | corresponding value is undefined. | |
a0d0e21e | 2041 | |
5ed4f2ec | 2042 | print "Exists\n" if exists $hash{$key}; |
2043 | print "Defined\n" if defined $hash{$key}; | |
01020589 GS |
2044 | print "True\n" if $hash{$key}; |
2045 | ||
d0a76353 | 2046 | exists may also be called on array elements, but its behavior is much less |
8f1da26d | 2047 | obvious and is strongly tied to the use of L</delete> on arrays. B<Be aware> |
d0a76353 RS |
2048 | that calling exists on array values is deprecated and likely to be removed in |
2049 | a future version of Perl. | |
2050 | ||
5ed4f2ec | 2051 | print "Exists\n" if exists $array[$index]; |
2052 | print "Defined\n" if defined $array[$index]; | |
01020589 | 2053 | print "True\n" if $array[$index]; |
a0d0e21e | 2054 | |
8f1da26d | 2055 | A hash or array element can be true only if it's defined and defined only if |
a0d0e21e LW |
2056 | it exists, but the reverse doesn't necessarily hold true. |
2057 | ||
afebc493 GS |
2058 | Given an expression that specifies the name of a subroutine, |
2059 | returns true if the specified subroutine has ever been declared, even | |
2060 | if it is undefined. Mentioning a subroutine name for exists or defined | |
80d38338 | 2061 | does not count as declaring it. Note that a subroutine that does not |
847c7ebe DD |
2062 | exist may still be callable: its package may have an C<AUTOLOAD> |
2063 | method that makes it spring into existence the first time that it is | |
3b10bc60 | 2064 | called; see L<perlsub>. |
afebc493 | 2065 | |
5ed4f2ec | 2066 | print "Exists\n" if exists &subroutine; |
2067 | print "Defined\n" if defined &subroutine; | |
afebc493 | 2068 | |
a0d0e21e | 2069 | Note that the EXPR can be arbitrarily complicated as long as the final |
afebc493 | 2070 | operation is a hash or array key lookup or subroutine name: |
a0d0e21e | 2071 | |
5ed4f2ec | 2072 | if (exists $ref->{A}->{B}->{$key}) { } |
2073 | if (exists $hash{A}{B}{$key}) { } | |
2b5ab1e7 | 2074 | |
5ed4f2ec | 2075 | if (exists $ref->{A}->{B}->[$ix]) { } |
2076 | if (exists $hash{A}{B}[$ix]) { } | |
01020589 | 2077 | |
afebc493 GS |
2078 | if (exists &{$ref->{A}{B}{$key}}) { } |
2079 | ||
9590a7cd | 2080 | Although the most deeply nested array or hash element will not spring into |
3b10bc60 | 2081 | existence just because its existence was tested, any intervening ones will. |
61eff3bc | 2082 | Thus C<< $ref->{"A"} >> and C<< $ref->{"A"}->{"B"} >> will spring |
01020589 | 2083 | into existence due to the existence test for the $key element above. |
3b10bc60 | 2084 | This happens anywhere the arrow operator is used, including even here: |
5a964f20 | 2085 | |
2b5ab1e7 | 2086 | undef $ref; |
5ed4f2ec | 2087 | if (exists $ref->{"Some key"}) { } |
2088 | print $ref; # prints HASH(0x80d3d5c) | |
2b5ab1e7 TC |
2089 | |
2090 | This surprising autovivification in what does not at first--or even | |
2091 | second--glance appear to be an lvalue context may be fixed in a future | |
5a964f20 | 2092 | release. |
a0d0e21e | 2093 | |
afebc493 GS |
2094 | Use of a subroutine call, rather than a subroutine name, as an argument |
2095 | to exists() is an error. | |
2096 | ||
5ed4f2ec | 2097 | exists ⊂ # OK |
2098 | exists &sub(); # Error | |
afebc493 | 2099 | |
a0d0e21e | 2100 | =item exit EXPR |
d74e8afc | 2101 | X<exit> X<terminate> X<abort> |
a0d0e21e | 2102 | |
ce2984c3 PF |
2103 | =item exit |
2104 | ||
c17cdb72 NC |
2105 | =for Pod::Functions terminate this program |
2106 | ||
2b5ab1e7 | 2107 | Evaluates EXPR and exits immediately with that value. Example: |
a0d0e21e LW |
2108 | |
2109 | $ans = <STDIN>; | |
2110 | exit 0 if $ans =~ /^[Xx]/; | |
2111 | ||
19799a22 | 2112 | See also C<die>. If EXPR is omitted, exits with C<0> status. The only |
2b5ab1e7 TC |
2113 | universally recognized values for EXPR are C<0> for success and C<1> |
2114 | for error; other values are subject to interpretation depending on the | |
2115 | environment in which the Perl program is running. For example, exiting | |
2116 | 69 (EX_UNAVAILABLE) from a I<sendmail> incoming-mail filter will cause | |
2117 | the mailer to return the item undelivered, but that's not true everywhere. | |
a0d0e21e | 2118 | |
19799a22 GS |
2119 | Don't use C<exit> to abort a subroutine if there's any chance that |
2120 | someone might want to trap whatever error happened. Use C<die> instead, | |
2121 | which can be trapped by an C<eval>. | |
28757baa | 2122 | |
19799a22 | 2123 | The exit() function does not always exit immediately. It calls any |
2b5ab1e7 | 2124 | defined C<END> routines first, but these C<END> routines may not |
19799a22 | 2125 | themselves abort the exit. Likewise any object destructors that need to |
60275626 | 2126 | be called are called before the real exit. C<END> routines and destructors |
391b733c | 2127 | can change the exit status by modifying C<$?>. If this is a problem, you |
fae6f8fa | 2128 | can call C<POSIX::_exit($status)> to avoid END and destructor processing. |
87275199 | 2129 | See L<perlmod> for details. |
5a964f20 | 2130 | |
ea9eb35a BJ |
2131 | Portability issues: L<perlport/exit>. |
2132 | ||
a0d0e21e | 2133 | =item exp EXPR |
d74e8afc | 2134 | X<exp> X<exponential> X<antilog> X<antilogarithm> X<e> |
a0d0e21e | 2135 | |
54310121 | 2136 | =item exp |
bbce6d69 | 2137 | |
c17cdb72 NC |
2138 | =for Pod::Functions raise I<e> to a power |
2139 | ||
b76cc8ba | 2140 | Returns I<e> (the natural logarithm base) to the power of EXPR. |
a0d0e21e LW |
2141 | If EXPR is omitted, gives C<exp($_)>. |
2142 | ||
628253b8 BF |
2143 | =item fc EXPR |
2144 | X<fc> X<foldcase> X<casefold> X<fold-case> X<case-fold> | |
2145 | ||
2146 | =item fc | |
2147 | ||
d9b04284 | 2148 | =for Pod::Functions +fc return casefolded version of a string |
c17cdb72 | 2149 | |
628253b8 BF |
2150 | Returns the casefolded version of EXPR. This is the internal function |
2151 | implementing the C<\F> escape in double-quoted strings. | |
2152 | ||
2153 | Casefolding is the process of mapping strings to a form where case | |
2154 | differences are erased; comparing two strings in their casefolded | |
2155 | form is effectively a way of asking if two strings are equal, | |
2156 | regardless of case. | |
2157 | ||
2158 | Roughly, if you ever found yourself writing this | |
2159 | ||
f6c6dcb6 | 2160 | lc($this) eq lc($that) # Wrong! |
628253b8 | 2161 | # or |
f6c6dcb6 | 2162 | uc($this) eq uc($that) # Also wrong! |
628253b8 | 2163 | # or |
f6c6dcb6 | 2164 | $this =~ /^\Q$that\E\z/i # Right! |
628253b8 BF |
2165 | |
2166 | Now you can write | |
2167 | ||
2168 | fc($this) eq fc($that) | |
2169 | ||
2170 | And get the correct results. | |
2171 | ||
fc39a31f KW |
2172 | Perl only implements the full form of casefolding, |
2173 | but you can access the simple folds using L<Unicode::UCD/casefold()> and | |
2174 | L<Unicode::UCD/prop_invmap()>. | |
628253b8 BF |
2175 | For further information on casefolding, refer to |
2176 | the Unicode Standard, specifically sections 3.13 C<Default Case Operations>, | |
2177 | 4.2 C<Case-Normative>, and 5.18 C<Case Mappings>, | |
2178 | available at L<http://www.unicode.org/versions/latest/>, as well as the | |
2179 | Case Charts available at L<http://www.unicode.org/charts/case/>. | |
2180 | ||
2181 | If EXPR is omitted, uses C<$_>. | |
2182 | ||
1ca267a5 KW |
2183 | This function behaves the same way under various pragma, such as within |
2184 | S<C<"use feature 'unicode_strings">>, as L</lc> does, with the single | |
2185 | exception of C<fc> of LATIN CAPITAL LETTER SHARP S (U+1E9E) within the | |
2186 | scope of S<C<use locale>>. The foldcase of this character would | |
2187 | normally be C<"ss">, but as explained in the L</lc> section, case | |
2188 | changes that cross the 255/256 boundary are problematic under locales, | |
2189 | and are hence prohibited. Therefore, this function under locale returns | |
2190 | instead the string C<"\x{17F}\x{17F}">, which is the LATIN SMALL LETTER | |
2191 | LONG S. Since that character itself folds to C<"s">, the string of two | |
2192 | of them together should be equivalent to a single U+1E9E when foldcased. | |
628253b8 BF |
2193 | |
2194 | While the Unicode Standard defines two additional forms of casefolding, | |
2195 | one for Turkic languages and one that never maps one character into multiple | |
2196 | characters, these are not provided by the Perl core; However, the CPAN module | |
2197 | C<Unicode::Casing> may be used to provide an implementation. | |
2198 | ||
2199 | This keyword is available only when the C<"fc"> feature is enabled, | |
7161e5c2 | 2200 | or when prefixed with C<CORE::>; See L<feature>. Alternately, |
628253b8 BF |
2201 | include a C<use v5.16> or later to the current scope. |
2202 | ||
a0d0e21e | 2203 | =item fcntl FILEHANDLE,FUNCTION,SCALAR |
d74e8afc | 2204 | X<fcntl> |
a0d0e21e | 2205 | |
c17cdb72 NC |
2206 | =for Pod::Functions file control system call |
2207 | ||
f86cebdf | 2208 | Implements the fcntl(2) function. You'll probably have to say |
a0d0e21e LW |
2209 | |
2210 | use Fcntl; | |
2211 | ||
0ade1984 | 2212 | first to get the correct constant definitions. Argument processing and |
3b10bc60 | 2213 | value returned work just like C<ioctl> below. |
a0d0e21e LW |
2214 | For example: |
2215 | ||
2216 | use Fcntl; | |
5a964f20 | 2217 | fcntl($filehandle, F_GETFL, $packed_return_buffer) |
a9a5a0dc | 2218 | or die "can't fcntl F_GETFL: $!"; |
5a964f20 | 2219 | |
554ad1fc | 2220 | You don't have to check for C<defined> on the return from C<fcntl>. |
951ba7fe GS |
2221 | Like C<ioctl>, it maps a C<0> return from the system call into |
2222 | C<"0 but true"> in Perl. This string is true in boolean context and C<0> | |
2b5ab1e7 TC |
2223 | in numeric context. It is also exempt from the normal B<-w> warnings |
2224 | on improper numeric conversions. | |
5a964f20 | 2225 | |
3b10bc60 | 2226 | Note that C<fcntl> raises an exception if used on a machine that |
2b5ab1e7 TC |
2227 | doesn't implement fcntl(2). See the Fcntl module or your fcntl(2) |
2228 | manpage to learn what functions are available on your system. | |
a0d0e21e | 2229 | |
be2f7487 TH |
2230 | Here's an example of setting a filehandle named C<REMOTE> to be |
2231 | non-blocking at the system level. You'll have to negotiate C<$|> | |
2232 | on your own, though. | |
2233 | ||
2234 | use Fcntl qw(F_GETFL F_SETFL O_NONBLOCK); | |
2235 | ||
2236 | $flags = fcntl(REMOTE, F_GETFL, 0) | |
2237 | or die "Can't get flags for the socket: $!\n"; | |
2238 | ||
2239 | $flags = fcntl(REMOTE, F_SETFL, $flags | O_NONBLOCK) | |
2240 | or die "Can't set flags for the socket: $!\n"; | |
2241 | ||
ea9eb35a BJ |
2242 | Portability issues: L<perlport/fcntl>. |
2243 | ||
cfa52385 FC |
2244 | =item __FILE__ |
2245 | X<__FILE__> | |
2246 | ||
c17cdb72 NC |
2247 | =for Pod::Functions the name of the current source file |
2248 | ||
cfa52385 FC |
2249 | A special token that returns the name of the file in which it occurs. |
2250 | ||
a0d0e21e | 2251 | =item fileno FILEHANDLE |
d74e8afc | 2252 | X<fileno> |
a0d0e21e | 2253 | |
c17cdb72 NC |
2254 | =for Pod::Functions return file descriptor from filehandle |
2255 | ||
2b5ab1e7 | 2256 | Returns the file descriptor for a filehandle, or undefined if the |
a7c1632d FC |
2257 | filehandle is not open. If there is no real file descriptor at the OS |
2258 | level, as can happen with filehandles connected to memory objects via | |
2259 | C<open> with a reference for the third argument, -1 is returned. | |
2260 | ||
2261 | This is mainly useful for constructing | |
19799a22 | 2262 | bitmaps for C<select> and low-level POSIX tty-handling operations. |
2b5ab1e7 TC |
2263 | If FILEHANDLE is an expression, the value is taken as an indirect |
2264 | filehandle, generally its name. | |
5a964f20 | 2265 | |
b76cc8ba | 2266 | You can use this to find out whether two handles refer to the |
5a964f20 TC |
2267 | same underlying descriptor: |
2268 | ||
3231d257 | 2269 | if (fileno(THIS) != -1 && fileno(THIS) == fileno(THAT)) { |
a9a5a0dc | 2270 | print "THIS and THAT are dups\n"; |
3231d257 | 2271 | } elsif (fileno(THIS) != -1 && fileno(THAT) != -1) { |
555bd962 BG |
2272 | print "THIS and THAT have different " . |
2273 | "underlying file descriptors\n"; | |
3231d257 | 2274 | } else { |
555bd962 BG |
2275 | print "At least one of THIS and THAT does " . |
2276 | "not have a real file descriptor\n"; | |
b76cc8ba NIS |
2277 | } |
2278 | ||
a0d0e21e | 2279 | =item flock FILEHANDLE,OPERATION |
d74e8afc | 2280 | X<flock> X<lock> X<locking> |
a0d0e21e | 2281 | |
c17cdb72 NC |
2282 | =for Pod::Functions lock an entire file with an advisory lock |
2283 | ||
19799a22 GS |
2284 | Calls flock(2), or an emulation of it, on FILEHANDLE. Returns true |
2285 | for success, false on failure. Produces a fatal error if used on a | |
2b5ab1e7 | 2286 | machine that doesn't implement flock(2), fcntl(2) locking, or lockf(3). |
dbfe1e81 | 2287 | C<flock> is Perl's portable file-locking interface, although it locks |
3b10bc60 | 2288 | entire files only, not records. |
2b5ab1e7 TC |
2289 | |
2290 | Two potentially non-obvious but traditional C<flock> semantics are | |
2291 | that it waits indefinitely until the lock is granted, and that its locks | |
dbfe1e81 FC |
2292 | are B<merely advisory>. Such discretionary locks are more flexible, but |
2293 | offer fewer guarantees. This means that programs that do not also use | |
2294 | C<flock> may modify files locked with C<flock>. See L<perlport>, | |
8f1da26d | 2295 | your port's specific documentation, and your system-specific local manpages |
2b5ab1e7 TC |
2296 | for details. It's best to assume traditional behavior if you're writing |
2297 | portable programs. (But if you're not, you should as always feel perfectly | |
2298 | free to write for your own system's idiosyncrasies (sometimes called | |
2299 | "features"). Slavish adherence to portability concerns shouldn't get | |
2300 | in the way of your getting your job done.) | |
a3cb178b | 2301 | |
8ebc5c01 | 2302 | OPERATION is one of LOCK_SH, LOCK_EX, or LOCK_UN, possibly combined with |
2303 | LOCK_NB. These constants are traditionally valued 1, 2, 8 and 4, but | |
8f1da26d TC |
2304 | you can use the symbolic names if you import them from the L<Fcntl> module, |
2305 | either individually, or as a group using the C<:flock> tag. LOCK_SH | |
68dc0745 | 2306 | requests a shared lock, LOCK_EX requests an exclusive lock, and LOCK_UN |
ea3105be | 2307 | releases a previously requested lock. If LOCK_NB is bitwise-or'ed with |
8f1da26d | 2308 | LOCK_SH or LOCK_EX, then C<flock> returns immediately rather than blocking |
3b10bc60 | 2309 | waiting for the lock; check the return status to see if you got it. |
68dc0745 | 2310 | |
2b5ab1e7 TC |
2311 | To avoid the possibility of miscoordination, Perl now flushes FILEHANDLE |
2312 | before locking or unlocking it. | |
8ebc5c01 | 2313 | |
f86cebdf | 2314 | Note that the emulation built with lockf(3) doesn't provide shared |
8ebc5c01 | 2315 | locks, and it requires that FILEHANDLE be open with write intent. These |
2b5ab1e7 | 2316 | are the semantics that lockf(3) implements. Most if not all systems |
f86cebdf | 2317 | implement lockf(3) in terms of fcntl(2) locking, though, so the |
8ebc5c01 | 2318 | differing semantics shouldn't bite too many people. |
2319 | ||
becacb53 TM |
2320 | Note that the fcntl(2) emulation of flock(3) requires that FILEHANDLE |
2321 | be open with read intent to use LOCK_SH and requires that it be open | |
2322 | with write intent to use LOCK_EX. | |
2323 | ||
19799a22 GS |
2324 | Note also that some versions of C<flock> cannot lock things over the |
2325 | network; you would need to use the more system-specific C<fcntl> for | |
f86cebdf GS |
2326 | that. If you like you can force Perl to ignore your system's flock(2) |
2327 | function, and so provide its own fcntl(2)-based emulation, by passing | |
8ebc5c01 | 2328 | the switch C<-Ud_flock> to the F<Configure> program when you configure |
8f1da26d | 2329 | and build a new Perl. |
4633a7c4 LW |
2330 | |
2331 | Here's a mailbox appender for BSD systems. | |
a0d0e21e | 2332 | |
f7051f2c FC |
2333 | # import LOCK_* and SEEK_END constants |
2334 | use Fcntl qw(:flock SEEK_END); | |
a0d0e21e LW |
2335 | |
2336 | sub lock { | |
a9a5a0dc VP |
2337 | my ($fh) = @_; |
2338 | flock($fh, LOCK_EX) or die "Cannot lock mailbox - $!\n"; | |
7ed5353d | 2339 | |
a9a5a0dc VP |
2340 | # and, in case someone appended while we were waiting... |
2341 | seek($fh, 0, SEEK_END) or die "Cannot seek - $!\n"; | |
a0d0e21e LW |
2342 | } |
2343 | ||
2344 | sub unlock { | |
a9a5a0dc VP |
2345 | my ($fh) = @_; |
2346 | flock($fh, LOCK_UN) or die "Cannot unlock mailbox - $!\n"; | |
a0d0e21e LW |
2347 | } |
2348 | ||
b0169937 | 2349 | open(my $mbox, ">>", "/usr/spool/mail/$ENV{'USER'}") |
5ed4f2ec | 2350 | or die "Can't open mailbox: $!"; |
a0d0e21e | 2351 | |
7ed5353d | 2352 | lock($mbox); |
b0169937 | 2353 | print $mbox $msg,"\n\n"; |
7ed5353d | 2354 | unlock($mbox); |
a0d0e21e | 2355 | |
3b10bc60 | 2356 | On systems that support a real flock(2), locks are inherited across fork() |
2357 | calls, whereas those that must resort to the more capricious fcntl(2) | |
2358 | function lose their locks, making it seriously harder to write servers. | |
2b5ab1e7 | 2359 | |
cb1a09d0 | 2360 | See also L<DB_File> for other flock() examples. |
a0d0e21e | 2361 | |
ea9eb35a BJ |
2362 | Portability issues: L<perlport/flock>. |
2363 | ||
a0d0e21e | 2364 | =item fork |
d74e8afc | 2365 | X<fork> X<child> X<parent> |
a0d0e21e | 2366 | |
c17cdb72 NC |
2367 | =for Pod::Functions create a new process just like this one |
2368 | ||
2b5ab1e7 TC |
2369 | Does a fork(2) system call to create a new process running the |
2370 | same program at the same point. It returns the child pid to the | |
2371 | parent process, C<0> to the child process, or C<undef> if the fork is | |
2372 | unsuccessful. File descriptors (and sometimes locks on those descriptors) | |
2373 | are shared, while everything else is copied. On most systems supporting | |
2374 | fork(), great care has gone into making it extremely efficient (for | |
2375 | example, using copy-on-write technology on data pages), making it the | |
2376 | dominant paradigm for multitasking over the last few decades. | |
5a964f20 | 2377 | |
e9fa405d | 2378 | Perl attempts to flush all files opened for |
0f897271 GS |
2379 | output before forking the child process, but this may not be supported |
2380 | on some platforms (see L<perlport>). To be safe, you may need to set | |
2381 | C<$|> ($AUTOFLUSH in English) or call the C<autoflush()> method of | |
80d38338 | 2382 | C<IO::Handle> on any open handles to avoid duplicate output. |
a0d0e21e | 2383 | |
19799a22 | 2384 | If you C<fork> without ever waiting on your children, you will |
2b5ab1e7 TC |
2385 | accumulate zombies. On some systems, you can avoid this by setting |
2386 | C<$SIG{CHLD}> to C<"IGNORE">. See also L<perlipc> for more examples of | |
2387 | forking and reaping moribund children. | |
cb1a09d0 | 2388 | |
28757baa | 2389 | Note that if your forked child inherits system file descriptors like |
2390 | STDIN and STDOUT that are actually connected by a pipe or socket, even | |
2b5ab1e7 | 2391 | if you exit, then the remote server (such as, say, a CGI script or a |
19799a22 | 2392 | backgrounded job launched from a remote shell) won't think you're done. |
2b5ab1e7 | 2393 | You should reopen those to F</dev/null> if it's any issue. |
28757baa | 2394 | |
ea9eb35a | 2395 | On some platforms such as Windows, where the fork() system call is not available, |
391b733c FC |
2396 | Perl can be built to emulate fork() in the Perl interpreter. |
2397 | The emulation is designed, at the level of the Perl program, | |
2398 | to be as compatible as possible with the "Unix" fork(). | |
6d17f725 | 2399 | However it has limitations that have to be considered in code intended to be portable. |
ea9eb35a BJ |
2400 | See L<perlfork> for more details. |
2401 | ||
2402 | Portability issues: L<perlport/fork>. | |
2403 | ||
cb1a09d0 | 2404 | =item format |
d74e8afc | 2405 | X<format> |
cb1a09d0 | 2406 | |
c17cdb72 NC |
2407 | =for Pod::Functions declare a picture format with use by the write() function |
2408 | ||
19799a22 | 2409 | Declare a picture format for use by the C<write> function. For |
cb1a09d0 AD |
2410 | example: |
2411 | ||
54310121 | 2412 | format Something = |
a9a5a0dc VP |
2413 | Test: @<<<<<<<< @||||| @>>>>> |
2414 | $str, $%, '$' . int($num) | |
cb1a09d0 AD |
2415 | . |
2416 | ||
2417 | $str = "widget"; | |
184e9718 | 2418 | $num = $cost/$quantity; |
cb1a09d0 AD |
2419 | $~ = 'Something'; |
2420 | write; | |
2421 | ||
2422 | See L<perlform> for many details and examples. | |
2423 | ||
8903cb82 | 2424 | =item formline PICTURE,LIST |
d74e8afc | 2425 | X<formline> |
a0d0e21e | 2426 | |
c17cdb72 NC |
2427 | =for Pod::Functions internal function used for formats |
2428 | ||
5a964f20 | 2429 | This is an internal function used by C<format>s, though you may call it, |
a0d0e21e LW |
2430 | too. It formats (see L<perlform>) a list of values according to the |
2431 | contents of PICTURE, placing the output into the format output | |
7660c0ab | 2432 | accumulator, C<$^A> (or C<$ACCUMULATOR> in English). |
19799a22 | 2433 | Eventually, when a C<write> is done, the contents of |
cf264981 SP |
2434 | C<$^A> are written to some filehandle. You could also read C<$^A> |
2435 | and then set C<$^A> back to C<"">. Note that a format typically | |
19799a22 | 2436 | does one C<formline> per line of form, but the C<formline> function itself |
748a9306 | 2437 | doesn't care how many newlines are embedded in the PICTURE. This means |
3b10bc60 | 2438 | that the C<~> and C<~~> tokens treat the entire PICTURE as a single line. |
748a9306 | 2439 | You may therefore need to use multiple formlines to implement a single |
3b10bc60 | 2440 | record format, just like the C<format> compiler. |
748a9306 | 2441 | |
19799a22 | 2442 | Be careful if you put double quotes around the picture, because an C<@> |
748a9306 | 2443 | character may be taken to mean the beginning of an array name. |
19799a22 | 2444 | C<formline> always returns true. See L<perlform> for other examples. |
a0d0e21e | 2445 | |
445b09e5 FC |
2446 | If you are trying to use this instead of C<write> to capture the output, |
2447 | you may find it easier to open a filehandle to a scalar | |
2448 | (C<< open $fh, ">", \$output >>) and write to that instead. | |
2449 | ||
a0d0e21e | 2450 | =item getc FILEHANDLE |
f723aae1 | 2451 | X<getc> X<getchar> X<character> X<file, read> |
a0d0e21e LW |
2452 | |
2453 | =item getc | |
2454 | ||
c17cdb72 NC |
2455 | =for Pod::Functions get the next character from the filehandle |
2456 | ||
a0d0e21e | 2457 | Returns the next character from the input file attached to FILEHANDLE, |
3b10bc60 | 2458 | or the undefined value at end of file or if there was an error (in |
b5fe5ca2 SR |
2459 | the latter case C<$!> is set). If FILEHANDLE is omitted, reads from |
2460 | STDIN. This is not particularly efficient. However, it cannot be | |
2461 | used by itself to fetch single characters without waiting for the user | |
2462 | to hit enter. For that, try something more like: | |
4633a7c4 LW |
2463 | |
2464 | if ($BSD_STYLE) { | |
a9a5a0dc | 2465 | system "stty cbreak </dev/tty >/dev/tty 2>&1"; |
4633a7c4 LW |
2466 | } |
2467 | else { | |
a9a5a0dc | 2468 | system "stty", '-icanon', 'eol', "\001"; |
4633a7c4 LW |
2469 | } |
2470 | ||
2471 | $key = getc(STDIN); | |
2472 | ||
2473 | if ($BSD_STYLE) { | |
a9a5a0dc | 2474 | system "stty -cbreak </dev/tty >/dev/tty 2>&1"; |
4633a7c4 LW |
2475 | } |
2476 | else { | |
3b10bc60 | 2477 | system 'stty', 'icanon', 'eol', '^@'; # ASCII NUL |
4633a7c4 LW |
2478 | } |
2479 | print "\n"; | |
2480 | ||
54310121 | 2481 | Determination of whether $BSD_STYLE should be set |
2482 | is left as an exercise to the reader. | |
cb1a09d0 | 2483 | |
19799a22 | 2484 | The C<POSIX::getattr> function can do this more portably on |
2b5ab1e7 | 2485 | systems purporting POSIX compliance. See also the C<Term::ReadKey> |
3d6c5fec | 2486 | module from your nearest L<CPAN|http://www.cpan.org> site. |
a0d0e21e LW |
2487 | |
2488 | =item getlogin | |
d74e8afc | 2489 | X<getlogin> X<login> |
a0d0e21e | 2490 | |
c17cdb72 NC |
2491 | =for Pod::Functions return who logged in at this tty |
2492 | ||
cf264981 | 2493 | This implements the C library function of the same name, which on most |
3b10bc60 | 2494 | systems returns the current login from F</etc/utmp>, if any. If it |
2495 | returns the empty string, use C<getpwuid>. | |
a0d0e21e | 2496 | |
f86702cc | 2497 | $login = getlogin || getpwuid($<) || "Kilroy"; |
a0d0e21e | 2498 | |
19799a22 GS |
2499 | Do not consider C<getlogin> for authentication: it is not as |
2500 | secure as C<getpwuid>. | |
4633a7c4 | 2501 | |
ea9eb35a BJ |
2502 | Portability issues: L<perlport/getlogin>. |
2503 | ||
a0d0e21e | 2504 | =item getpeername SOCKET |
d74e8afc | 2505 | X<getpeername> X<peer> |
a0d0e21e | 2506 | |
c17cdb72 NC |
2507 | =for Pod::Functions find the other end of a socket connection |
2508 | ||
a3390c9f FC |
2509 | Returns the packed sockaddr address of the other end of the SOCKET |
2510 | connection. | |
a0d0e21e | 2511 | |
4633a7c4 LW |
2512 | use Socket; |
2513 | $hersockaddr = getpeername(SOCK); | |
19799a22 | 2514 | ($port, $iaddr) = sockaddr_in($hersockaddr); |
4633a7c4 LW |
2515 | $herhostname = gethostbyaddr($iaddr, AF_INET); |
2516 | $herstraddr = inet_ntoa($iaddr); | |
a0d0e21e LW |
2517 | |
2518 | =item getpgrp PID | |
d74e8afc | 2519 | X<getpgrp> X<group> |
a0d0e21e | 2520 | |
c17cdb72 NC |
2521 | =for Pod::Functions get process group |
2522 | ||
47e29363 | 2523 | Returns the current process group for the specified PID. Use |
7660c0ab | 2524 | a PID of C<0> to get the current process group for the |
4633a7c4 | 2525 | current process. Will raise an exception if used on a machine that |
a3390c9f FC |
2526 | doesn't implement getpgrp(2). If PID is omitted, returns the process |
2527 | group of the current process. Note that the POSIX version of C<getpgrp> | |
7660c0ab | 2528 | does not accept a PID argument, so only C<PID==0> is truly portable. |
a0d0e21e | 2529 | |
ea9eb35a BJ |
2530 | Portability issues: L<perlport/getpgrp>. |
2531 | ||
a0d0e21e | 2532 | =item getppid |
d74e8afc | 2533 | X<getppid> X<parent> X<pid> |
a0d0e21e | 2534 | |
c17cdb72 NC |
2535 | =for Pod::Functions get parent process ID |
2536 | ||
a0d0e21e LW |
2537 | Returns the process id of the parent process. |
2538 | ||
d7c042c9 AB |
2539 | Note for Linux users: Between v5.8.1 and v5.16.0 Perl would work |
2540 | around non-POSIX thread semantics the minority of Linux systems (and | |
2541 | Debian GNU/kFreeBSD systems) that used LinuxThreads, this emulation | |
7161e5c2 | 2542 | has since been removed. See the documentation for L<$$|perlvar/$$> for |
d7c042c9 | 2543 | details. |
4d76a344 | 2544 | |
ea9eb35a BJ |
2545 | Portability issues: L<perlport/getppid>. |
2546 | ||
a0d0e21e | 2547 | =item getpriority WHICH,WHO |
d74e8afc | 2548 | X<getpriority> X<priority> X<nice> |
a0d0e21e | 2549 | |
c17cdb72 NC |
2550 | =for Pod::Functions get current nice value |
2551 | ||
4633a7c4 | 2552 | Returns the current priority for a process, a process group, or a user. |
01aa884e | 2553 | (See L<getpriority(2)>.) Will raise a fatal exception if used on a |
f86cebdf | 2554 | machine that doesn't implement getpriority(2). |
a0d0e21e | 2555 | |
ea9eb35a BJ |
2556 | Portability issues: L<perlport/getpriority>. |
2557 | ||
a0d0e21e | 2558 | =item getpwnam NAME |
d74e8afc ITB |
2559 | X<getpwnam> X<getgrnam> X<gethostbyname> X<getnetbyname> X<getprotobyname> |
2560 | X<getpwuid> X<getgrgid> X<getservbyname> X<gethostbyaddr> X<getnetbyaddr> | |
2561 | X<getprotobynumber> X<getservbyport> X<getpwent> X<getgrent> X<gethostent> | |
2562 | X<getnetent> X<getprotoent> X<getservent> X<setpwent> X<setgrent> X<sethostent> | |
2563 | X<setnetent> X<setprotoent> X<setservent> X<endpwent> X<endgrent> X<endhostent> | |
2564 | X<endnetent> X<endprotoent> X<endservent> | |
a0d0e21e | 2565 | |
c17cdb72 NC |
2566 | =for Pod::Functions get passwd record given user login name |
2567 | ||
a0d0e21e LW |
2568 | =item getgrnam NAME |
2569 | ||
c17cdb72 NC |
2570 | =for Pod::Functions get group record given group name |
2571 | ||
a0d0e21e LW |
2572 | =item gethostbyname NAME |
2573 | ||
c17cdb72 NC |
2574 | =for Pod::Functions get host record given name |
2575 | ||
a0d0e21e LW |
2576 | =item getnetbyname NAME |
2577 | ||
c17cdb72 NC |
2578 | =for Pod::Functions get networks record given name |
2579 | ||
a0d0e21e LW |
2580 | =item getprotobyname NAME |
2581 | ||
c17cdb72 NC |
2582 | =for Pod::Functions get protocol record given name |
2583 | ||
a0d0e21e LW |
2584 | =item getpwuid UID |
2585 | ||
c17cdb72 NC |
2586 | =for Pod::Functions get passwd record given user ID |
2587 | ||
a0d0e21e LW |
2588 | =item getgrgid GID |
2589 | ||
c17cdb72 NC |
2590 | =for Pod::Functions get group record given group user ID |
2591 | ||
a0d0e21e LW |
2592 | =item getservbyname NAME,PROTO |
2593 | ||
c17cdb72 NC |
2594 | =for Pod::Functions get services record given its name |
2595 | ||
a0d0e21e LW |
2596 | =item gethostbyaddr ADDR,ADDRTYPE |
2597 | ||
c17cdb72 NC |
2598 | =for Pod::Functions get host record given its address |
2599 | ||
a0d0e21e LW |
2600 | =item getnetbyaddr ADDR,ADDRTYPE |
2601 | ||
c17cdb72 NC |
2602 | =for Pod::Functions get network record given its address |
2603 | ||
a0d0e21e LW |
2604 | =item getprotobynumber NUMBER |
2605 | ||
c17cdb72 NC |
2606 | =for Pod::Functions get protocol record numeric protocol |
2607 | ||
a0d0e21e LW |
2608 | =item getservbyport PORT,PROTO |
2609 | ||
c17cdb72 NC |
2610 | =for Pod::Functions get services record given numeric port |
2611 | ||
a0d0e21e LW |
2612 | =item getpwent |
2613 | ||
c17cdb72 NC |
2614 | =for Pod::Functions get next passwd record |
2615 | ||
a0d0e21e LW |
2616 | =item getgrent |
2617 | ||
c17cdb72 NC |
2618 | =for Pod::Functions get next group record |
2619 | ||
a0d0e21e LW |
2620 | =item gethostent |
2621 | ||
c17cdb72 NC |
2622 | =for Pod::Functions get next hosts record |
2623 | ||
a0d0e21e LW |
2624 | =item getnetent |
2625 | ||
c17cdb72 NC |
2626 | =for Pod::Functions get next networks record |
2627 | ||
a0d0e21e LW |
2628 | =item getprotoent |
2629 | ||
c17cdb72 NC |
2630 | =for Pod::Functions get next protocols record |
2631 | ||
a0d0e21e LW |
2632 | =item getservent |
2633 | ||
c17cdb72 NC |
2634 | =for Pod::Functions get next services record |
2635 | ||
a0d0e21e LW |
2636 | =item setpwent |
2637 | ||
c17cdb72 NC |
2638 | =for Pod::Functions prepare passwd file for use |
2639 | ||
a0d0e21e LW |
2640 | =item setgrent |
2641 | ||
c17cdb72 NC |
2642 | =for Pod::Functions prepare group file for use |
2643 | ||
a0d0e21e LW |
2644 | =item sethostent STAYOPEN |
2645 | ||
c17cdb72 NC |
2646 | =for Pod::Functions prepare hosts file for use |
2647 | ||
a0d0e21e LW |
2648 | =item setnetent STAYOPEN |
2649 | ||
c17cdb72 NC |
2650 | =for Pod::Functions prepare networks file for use |
2651 | ||
a0d0e21e LW |
2652 | =item setprotoent STAYOPEN |
2653 | ||
c17cdb72 NC |
2654 | =for Pod::Functions prepare protocols file for use |
2655 | ||
a0d0e21e LW |
2656 | =item setservent STAYOPEN |
2657 | ||
c17cdb72 NC |
2658 | =for Pod::Functions prepare services file for use |
2659 | ||
a0d0e21e LW |
2660 | =item endpwent |
2661 | ||
c17cdb72 NC |
2662 | =for Pod::Functions be done using passwd file |
2663 | ||
a0d0e21e LW |
2664 | =item endgrent |
2665 | ||
c17cdb72 NC |
2666 | =for Pod::Functions be done using group file |
2667 | ||
a0d0e21e LW |
2668 | =item endhostent |
2669 | ||
c17cdb72 NC |
2670 | =for Pod::Functions be done using hosts file |
2671 | ||
a0d0e21e LW |
2672 | =item endnetent |
2673 | ||
c17cdb72 NC |
2674 | =for Pod::Functions be done using networks file |
2675 | ||
a0d0e21e LW |
2676 | =item endprotoent |
2677 | ||
c17cdb72 NC |
2678 | =for Pod::Functions be done using protocols file |
2679 | ||
a0d0e21e LW |
2680 | =item endservent |
2681 | ||
c17cdb72 NC |
2682 | =for Pod::Functions be done using services file |
2683 | ||
80d38338 TC |
2684 | These routines are the same as their counterparts in the |
2685 | system C library. In list context, the return values from the | |
a0d0e21e LW |
2686 | various get routines are as follows: |
2687 | ||
2688 | ($name,$passwd,$uid,$gid, | |
6ee623d5 | 2689 | $quota,$comment,$gcos,$dir,$shell,$expire) = getpw* |
a0d0e21e LW |
2690 | ($name,$passwd,$gid,$members) = getgr* |
2691 | ($name,$aliases,$addrtype,$length,@addrs) = gethost* | |
2692 | ($name,$aliases,$addrtype,$net) = getnet* | |
2693 | ($name,$aliases,$proto) = getproto* | |
2694 | ($name,$aliases,$port,$proto) = getserv* | |
2695 | ||
3b10bc60 | 2696 | (If the entry doesn't exist you get an empty list.) |
a0d0e21e | 2697 | |
4602f195 JH |
2698 | The exact meaning of the $gcos field varies but it usually contains |
2699 | the real name of the user (as opposed to the login name) and other | |
2700 | information pertaining to the user. Beware, however, that in many | |
2701 | system users are able to change this information and therefore it | |
106325ad | 2702 | cannot be trusted and therefore the $gcos is tainted (see |
2959b6e3 | 2703 | L<perlsec>). The $passwd and $shell, user's encrypted password and |
a3390c9f | 2704 | login shell, are also tainted, for the same reason. |
4602f195 | 2705 | |
5a964f20 | 2706 | In scalar context, you get the name, unless the function was a |
a0d0e21e LW |
2707 | lookup by name, in which case you get the other thing, whatever it is. |
2708 | (If the entry doesn't exist you get the undefined value.) For example: | |
2709 | ||
5a964f20 TC |
2710 | $uid = getpwnam($name); |
2711 | $name = getpwuid($num); | |
2712 | $name = getpwent(); | |
2713 | $gid = getgrnam($name); | |
08a33e13 | 2714 | $name = getgrgid($num); |
5a964f20 TC |
2715 | $name = getgrent(); |
2716 | #etc. | |
a0d0e21e | 2717 | |
4602f195 | 2718 | In I<getpw*()> the fields $quota, $comment, and $expire are special |
80d38338 | 2719 | in that they are unsupported on many systems. If the |
4602f195 JH |
2720 | $quota is unsupported, it is an empty scalar. If it is supported, it |
2721 | usually encodes the disk quota. If the $comment field is unsupported, | |
2722 | it is an empty scalar. If it is supported it usually encodes some | |
2723 | administrative comment about the user. In some systems the $quota | |
2724 | field may be $change or $age, fields that have to do with password | |
2725 | aging. In some systems the $comment field may be $class. The $expire | |
2726 | field, if present, encodes the expiration period of the account or the | |
2727 | password. For the availability and the exact meaning of these fields | |
8f1da26d | 2728 | in your system, please consult getpwnam(3) and your system's |
4602f195 JH |
2729 | F<pwd.h> file. You can also find out from within Perl what your |
2730 | $quota and $comment fields mean and whether you have the $expire field | |
2731 | by using the C<Config> module and the values C<d_pwquota>, C<d_pwage>, | |
2732 | C<d_pwchange>, C<d_pwcomment>, and C<d_pwexpire>. Shadow password | |
3b10bc60 | 2733 | files are supported only if your vendor has implemented them in the |
4602f195 | 2734 | intuitive fashion that calling the regular C library routines gets the |
5d3a0a3b | 2735 | shadow versions if you're running under privilege or if there exists |
cf264981 | 2736 | the shadow(3) functions as found in System V (this includes Solaris |
a3390c9f | 2737 | and Linux). Those systems that implement a proprietary shadow password |
5d3a0a3b | 2738 | facility are unlikely to be supported. |
6ee623d5 | 2739 | |
a3390c9f | 2740 | The $members value returned by I<getgr*()> is a space-separated list of |
a0d0e21e LW |
2741 | the login names of the members of the group. |
2742 | ||
2743 | For the I<gethost*()> functions, if the C<h_errno> variable is supported in | |
2744 | C, it will be returned to you via C<$?> if the function call fails. The | |
3b10bc60 | 2745 | C<@addrs> value returned by a successful call is a list of raw |
2746 | addresses returned by the corresponding library call. In the | |
2747 | Internet domain, each address is four bytes long; you can unpack it | |
a0d0e21e LW |
2748 | by saying something like: |
2749 | ||
f337b084 | 2750 | ($a,$b,$c,$d) = unpack('W4',$addr[0]); |
a0d0e21e | 2751 | |
2b5ab1e7 TC |
2752 | The Socket library makes this slightly easier: |
2753 | ||
2754 | use Socket; | |
2755 | $iaddr = inet_aton("127.1"); # or whatever address | |
2756 | $name = gethostbyaddr($iaddr, AF_INET); | |
2757 | ||
2758 | # or going the other way | |
19799a22 | 2759 | $straddr = inet_ntoa($iaddr); |
2b5ab1e7 | 2760 | |
d760c846 GS |
2761 | In the opposite way, to resolve a hostname to the IP address |
2762 | you can write this: | |
2763 | ||
2764 | use Socket; | |
2765 | $packed_ip = gethostbyname("www.perl.org"); | |
2766 | if (defined $packed_ip) { | |
2767 | $ip_address = inet_ntoa($packed_ip); | |
2768 | } | |
2769 | ||
b018eaf1 | 2770 | Make sure C<gethostbyname()> is called in SCALAR context and that |
d760c846 GS |
2771 | its return value is checked for definedness. |
2772 | ||
0d043efa FC |
2773 | The C<getprotobynumber> function, even though it only takes one argument, |
2774 | has the precedence of a list operator, so beware: | |
2775 | ||
2776 | getprotobynumber $number eq 'icmp' # WRONG | |
2777 | getprotobynumber($number eq 'icmp') # actually means this | |
2778 | getprotobynumber($number) eq 'icmp' # better this way | |
2779 | ||
19799a22 GS |
2780 | If you get tired of remembering which element of the return list |
2781 | contains which return value, by-name interfaces are provided | |
2782 | in standard modules: C<File::stat>, C<Net::hostent>, C<Net::netent>, | |
2783 | C<Net::protoent>, C<Net::servent>, C<Time::gmtime>, C<Time::localtime>, | |
2784 | and C<User::grent>. These override the normal built-ins, supplying | |
2785 | versions that return objects with the appropriate names | |
2786 | for each field. For example: | |
5a964f20 TC |
2787 | |
2788 | use File::stat; | |
2789 | use User::pwent; | |
2790 | $is_his = (stat($filename)->uid == pwent($whoever)->uid); | |
2791 | ||
a3390c9f | 2792 | Even though it looks as though they're the same method calls (uid), |
b76cc8ba | 2793 | they aren't, because a C<File::stat> object is different from |
19799a22 | 2794 | a C<User::pwent> object. |
5a964f20 | 2795 | |
ea9eb35a BJ |
2796 | Portability issues: L<perlport/getpwnam> to L<perlport/endservent>. |
2797 | ||
a0d0e21e | 2798 | =item getsockname SOCKET |
d74e8afc | 2799 | X<getsockname> |
a0d0e21e | 2800 | |
c17cdb72 NC |
2801 | =for Pod::Functions retrieve the sockaddr for a given socket |
2802 | ||
19799a22 GS |
2803 | Returns the packed sockaddr address of this end of the SOCKET connection, |
2804 | in case you don't know the address because you have several different | |
2805 | IPs that the connection might have come in on. | |
a0d0e21e | 2806 | |
4633a7c4 LW |
2807 | use Socket; |
2808 | $mysockaddr = getsockname(SOCK); | |
19799a22 | 2809 | ($port, $myaddr) = sockaddr_in($mysockaddr); |
b76cc8ba | 2810 | printf "Connect to %s [%s]\n", |
19799a22 GS |
2811 | scalar gethostbyaddr($myaddr, AF_INET), |
2812 | inet_ntoa($myaddr); | |
a0d0e21e LW |
2813 | |
2814 | =item getsockopt SOCKET,LEVEL,OPTNAME | |
d74e8afc | 2815 | X<getsockopt> |
a0d0e21e | 2816 | |
c17cdb72 NC |
2817 | =for Pod::Functions get socket options on a given socket |
2818 | ||
636e6b1f TH |
2819 | Queries the option named OPTNAME associated with SOCKET at a given LEVEL. |
2820 | Options may exist at multiple protocol levels depending on the socket | |
2821 | type, but at least the uppermost socket level SOL_SOCKET (defined in the | |
391b733c | 2822 | C<Socket> module) will exist. To query options at another level the |
636e6b1f | 2823 | protocol number of the appropriate protocol controlling the option |
391b733c | 2824 | should be supplied. For example, to indicate that an option is to be |
636e6b1f | 2825 | interpreted by the TCP protocol, LEVEL should be set to the protocol |
80d38338 | 2826 | number of TCP, which you can get using C<getprotobyname>. |
636e6b1f | 2827 | |
80d38338 | 2828 | The function returns a packed string representing the requested socket |
3b10bc60 | 2829 | option, or C<undef> on error, with the reason for the error placed in |
391b733c | 2830 | C<$!>. Just what is in the packed string depends on LEVEL and OPTNAME; |
80d38338 TC |
2831 | consult getsockopt(2) for details. A common case is that the option is an |
2832 | integer, in which case the result is a packed integer, which you can decode | |
2833 | using C<unpack> with the C<i> (or C<I>) format. | |
636e6b1f | 2834 | |
8f1da26d | 2835 | Here's an example to test whether Nagle's algorithm is enabled on a socket: |
636e6b1f | 2836 | |
4852725b | 2837 | use Socket qw(:all); |
636e6b1f TH |
2838 | |
2839 | defined(my $tcp = getprotobyname("tcp")) | |
a9a5a0dc | 2840 | or die "Could not determine the protocol number for tcp"; |
4852725b DD |
2841 | # my $tcp = IPPROTO_TCP; # Alternative |
2842 | my $packed = getsockopt($socket, $tcp, TCP_NODELAY) | |
80d38338 | 2843 | or die "getsockopt TCP_NODELAY: $!"; |
636e6b1f | 2844 | my $nodelay = unpack("I", $packed); |
f7051f2c FC |
2845 | print "Nagle's algorithm is turned ", |
2846 | $nodelay ? "off\n" : "on\n"; | |
636e6b1f | 2847 | |
ea9eb35a | 2848 | Portability issues: L<perlport/getsockopt>. |
a0d0e21e LW |
2849 | |
2850 | =item glob EXPR | |
d74e8afc | 2851 | X<glob> X<wildcard> X<filename, expansion> X<expand> |
a0d0e21e | 2852 | |
0a753a76 | 2853 | =item glob |
2854 | ||
c17cdb72 NC |
2855 | =for Pod::Functions expand filenames using wildcards |
2856 | ||
d9a9d457 | 2857 | In list context, returns a (possibly empty) list of filename expansions on |
391b733c | 2858 | the value of EXPR such as the standard Unix shell F</bin/csh> would do. In |
d9a9d457 | 2859 | scalar context, glob iterates through such filename expansions, returning |
391b733c FC |
2860 | undef when the list is exhausted. This is the internal function |
2861 | implementing the C<< <*.c> >> operator, but you can use it directly. If | |
d9a9d457 JL |
2862 | EXPR is omitted, C<$_> is used. The C<< <*.c> >> operator is discussed in |
2863 | more detail in L<perlop/"I/O Operators">. | |
a0d0e21e | 2864 | |
80d38338 TC |
2865 | Note that C<glob> splits its arguments on whitespace and treats |
2866 | each segment as separate pattern. As such, C<glob("*.c *.h")> | |
2867 | matches all files with a F<.c> or F<.h> extension. The expression | |
b474a1b1 | 2868 | C<glob(".* *")> matches all files in the current working directory. |
a91bb7b1 TC |
2869 | If you want to glob filenames that might contain whitespace, you'll |
2870 | have to use extra quotes around the spacey filename to protect it. | |
2871 | For example, to glob filenames that have an C<e> followed by a space | |
2872 | followed by an C<f>, use either of: | |
2873 | ||
2874 | @spacies = <"*e f*">; | |
2875 | @spacies = glob '"*e f*"'; | |
2876 | @spacies = glob q("*e f*"); | |
2877 | ||
2878 | If you had to get a variable through, you could do this: | |
2879 | ||
2880 | @spacies = glob "'*${var}e f*'"; | |
2881 | @spacies = glob qq("*${var}e f*"); | |
80d38338 TC |
2882 | |
2883 | If non-empty braces are the only wildcard characters used in the | |
2884 | C<glob>, no filenames are matched, but potentially many strings | |
2885 | are returned. For example, this produces nine strings, one for | |
2886 | each pairing of fruits and colors: | |
2887 | ||
2888 | @many = glob "{apple,tomato,cherry}={green,yellow,red}"; | |
5c0c9249 | 2889 | |
e9fa405d | 2890 | This operator is implemented using the standard |
5c0c9249 PF |
2891 | C<File::Glob> extension. See L<File::Glob> for details, including |
2892 | C<bsd_glob> which does not treat whitespace as a pattern separator. | |
3a4b19e4 | 2893 | |
ea9eb35a BJ |
2894 | Portability issues: L<perlport/glob>. |
2895 | ||
a0d0e21e | 2896 | =item gmtime EXPR |
d74e8afc | 2897 | X<gmtime> X<UTC> X<Greenwich> |
a0d0e21e | 2898 | |
ce2984c3 PF |
2899 | =item gmtime |
2900 | ||
c17cdb72 NC |
2901 | =for Pod::Functions convert UNIX time into record or string using Greenwich time |
2902 | ||
4509d391 | 2903 | Works just like L</localtime> but the returned values are |
435fbc73 | 2904 | localized for the standard Greenwich time zone. |
a0d0e21e | 2905 | |
a3390c9f FC |
2906 | Note: When called in list context, $isdst, the last value |
2907 | returned by gmtime, is always C<0>. There is no | |
435fbc73 | 2908 | Daylight Saving Time in GMT. |
0a753a76 | 2909 | |
ea9eb35a | 2910 | Portability issues: L<perlport/gmtime>. |
62aa5637 | 2911 | |
a0d0e21e | 2912 | =item goto LABEL |
d74e8afc | 2913 | X<goto> X<jump> X<jmp> |
a0d0e21e | 2914 | |
748a9306 LW |
2915 | =item goto EXPR |
2916 | ||
a0d0e21e LW |
2917 | =item goto &NAME |
2918 | ||
c17cdb72 NC |
2919 | =for Pod::Functions create spaghetti code |
2920 | ||
5a5b79a3 | 2921 | The C<goto LABEL> form finds the statement labeled with LABEL and |
391b733c | 2922 | resumes execution there. It can't be used to get out of a block or |
b500e03b GG |
2923 | subroutine given to C<sort>. It can be used to go almost anywhere |
2924 | else within the dynamic scope, including out of subroutines, but it's | |
2925 | usually better to use some other construct such as C<last> or C<die>. | |
2926 | The author of Perl has never felt the need to use this form of C<goto> | |
3b10bc60 | 2927 | (in Perl, that is; C is another matter). (The difference is that C |
b500e03b GG |
2928 | does not offer named loops combined with loop control. Perl does, and |
2929 | this replaces most structured uses of C<goto> in other languages.) | |
a0d0e21e | 2930 | |
5a5b79a3 | 2931 | The C<goto EXPR> form expects to evaluate C<EXPR> to a code reference or |
3e8a6370 | 2932 | a label name. If it evaluates to a code reference, it will be handled |
5a5b79a3 | 2933 | like C<goto &NAME>, below. This is especially useful for implementing |
3e8a6370 RS |
2934 | tail recursion via C<goto __SUB__>. |
2935 | ||
2936 | If the expression evaluates to a label name, its scope will be resolved | |
7660c0ab | 2937 | dynamically. This allows for computed C<goto>s per FORTRAN, but isn't |
748a9306 LW |
2938 | necessarily recommended if you're optimizing for maintainability: |
2939 | ||
2940 | goto ("FOO", "BAR", "GLARCH")[$i]; | |
2941 | ||
5a5b79a3 | 2942 | As shown in this example, C<goto EXPR> is exempt from the "looks like a |
391b733c FC |
2943 | function" rule. A pair of parentheses following it does not (necessarily) |
2944 | delimit its argument. C<goto("NE")."XT"> is equivalent to C<goto NEXT>. | |
8a7e748e FC |
2945 | Also, unlike most named operators, this has the same precedence as |
2946 | assignment. | |
887d89fd | 2947 | |
5a5b79a3 | 2948 | Use of C<goto LABEL> or C<goto EXPR> to jump into a construct is |
0b98bec9 | 2949 | deprecated and will issue a warning. Even then, it may not be used to |
b500e03b GG |
2950 | go into any construct that requires initialization, such as a |
2951 | subroutine or a C<foreach> loop. It also can't be used to go into a | |
0b98bec9 | 2952 | construct that is optimized away. |
b500e03b | 2953 | |
5a5b79a3 | 2954 | The C<goto &NAME> form is quite different from the other forms of |
1b6921cb BT |
2955 | C<goto>. In fact, it isn't a goto in the normal sense at all, and |
2956 | doesn't have the stigma associated with other gotos. Instead, it | |
2957 | exits the current subroutine (losing any changes set by local()) and | |
2958 | immediately calls in its place the named subroutine using the current | |
2959 | value of @_. This is used by C<AUTOLOAD> subroutines that wish to | |
2960 | load another subroutine and then pretend that the other subroutine had | |
2961 | been called in the first place (except that any modifications to C<@_> | |
6cb9131c GS |
2962 | in the current subroutine are propagated to the other subroutine.) |
2963 | After the C<goto>, not even C<caller> will be able to tell that this | |
2964 | routine was called first. | |
2965 | ||
2966 | NAME needn't be the name of a subroutine; it can be a scalar variable | |
8f1da26d | 2967 | containing a code reference or a block that evaluates to a code |
6cb9131c | 2968 | reference. |
a0d0e21e LW |
2969 | |
2970 | =item grep BLOCK LIST | |
d74e8afc | 2971 | X<grep> |
a0d0e21e LW |
2972 | |
2973 | =item grep EXPR,LIST | |
2974 | ||
c17cdb72 NC |
2975 | =for Pod::Functions locate elements in a list test true against a given criterion |
2976 | ||
2b5ab1e7 TC |
2977 | This is similar in spirit to, but not the same as, grep(1) and its |
2978 | relatives. In particular, it is not limited to using regular expressions. | |
2f9daede | 2979 | |
a0d0e21e | 2980 | Evaluates the BLOCK or EXPR for each element of LIST (locally setting |
7660c0ab | 2981 | C<$_> to each element) and returns the list value consisting of those |
19799a22 GS |
2982 | elements for which the expression evaluated to true. In scalar |
2983 | context, returns the number of times the expression was true. | |
a0d0e21e LW |
2984 | |
2985 | @foo = grep(!/^#/, @bar); # weed out comments | |
2986 | ||
2987 | or equivalently, | |
2988 | ||
2989 | @foo = grep {!/^#/} @bar; # weed out comments | |
2990 | ||
be3174d2 GS |
2991 | Note that C<$_> is an alias to the list value, so it can be used to |
2992 | modify the elements of the LIST. While this is useful and supported, | |
2993 | it can cause bizarre results if the elements of LIST are not variables. | |
2b5ab1e7 TC |
2994 | Similarly, grep returns aliases into the original list, much as a for |
2995 | loop's index variable aliases the list elements. That is, modifying an | |
19799a22 GS |
2996 | element of a list returned by grep (for example, in a C<foreach>, C<map> |
2997 | or another C<grep>) actually modifies the element in the original list. | |
2b5ab1e7 | 2998 | This is usually something to be avoided when writing clear code. |
a0d0e21e | 2999 | |
a4fb8298 | 3000 | If C<$_> is lexical in the scope where the C<grep> appears (because it has |
c071e214 FC |
3001 | been declared with the deprecated C<my $_> construct) |
3002 | then, in addition to being locally aliased to | |
80d38338 | 3003 | the list elements, C<$_> keeps being lexical inside the block; i.e., it |
a4fb8298 RGS |
3004 | can't be seen from the outside, avoiding any potential side-effects. |
3005 | ||
19799a22 | 3006 | See also L</map> for a list composed of the results of the BLOCK or EXPR. |
38325410 | 3007 | |
a0d0e21e | 3008 | =item hex EXPR |
d74e8afc | 3009 | X<hex> X<hexadecimal> |
a0d0e21e | 3010 | |
54310121 | 3011 | =item hex |
bbce6d69 | 3012 | |
c17cdb72 NC |
3013 | =for Pod::Functions convert a string to a hexadecimal number |
3014 | ||
2b5ab1e7 | 3015 | Interprets EXPR as a hex string and returns the corresponding value. |
38366c11 | 3016 | (To convert strings that might start with either C<0>, C<0x>, or C<0b>, see |
2b5ab1e7 | 3017 | L</oct>.) If EXPR is omitted, uses C<$_>. |
2f9daede TP |
3018 | |
3019 | print hex '0xAf'; # prints '175' | |
3020 | print hex 'aF'; # same | |
a0d0e21e | 3021 | |
19799a22 | 3022 | Hex strings may only represent integers. Strings that would cause |
53305cf1 | 3023 | integer overflow trigger a warning. Leading whitespace is not stripped, |
391b733c | 3024 | unlike oct(). To present something as hex, look into L</printf>, |
8f1da26d | 3025 | L</sprintf>, and L</unpack>. |
19799a22 | 3026 | |
ce2984c3 | 3027 | =item import LIST |
d74e8afc | 3028 | X<import> |
a0d0e21e | 3029 | |
c17cdb72 NC |
3030 | =for Pod::Functions patch a module's namespace into your own |
3031 | ||
19799a22 | 3032 | There is no builtin C<import> function. It is just an ordinary |
4633a7c4 | 3033 | method (subroutine) defined (or inherited) by modules that wish to export |
19799a22 | 3034 | names to another module. The C<use> function calls the C<import> method |
cea6626f | 3035 | for the package used. See also L</use>, L<perlmod>, and L<Exporter>. |
a0d0e21e LW |
3036 | |
3037 | =item index STR,SUBSTR,POSITION | |
d74e8afc | 3038 | X<index> X<indexOf> X<InStr> |
a0d0e21e LW |
3039 | |
3040 | =item index STR,SUBSTR | |
3041 | ||
c17cdb72 NC |
3042 | =for Pod::Functions find a substring within a string |
3043 | ||
2b5ab1e7 TC |
3044 | The index function searches for one string within another, but without |
3045 | the wildcard-like behavior of a full regular-expression pattern match. | |
3046 | It returns the position of the first occurrence of SUBSTR in STR at | |
3047 | or after POSITION. If POSITION is omitted, starts searching from the | |
26f149de YST |
3048 | beginning of the string. POSITION before the beginning of the string |
3049 | or after its end is treated as if it were the beginning or the end, | |
e1dccc0d Z |
3050 | respectively. POSITION and the return value are based at zero. |
3051 | If the substring is not found, C<index> returns -1. | |
a0d0e21e LW |
3052 | |
3053 | =item int EXPR | |
f723aae1 | 3054 | X<int> X<integer> X<truncate> X<trunc> X<floor> |
a0d0e21e | 3055 | |
54310121 | 3056 | =item int |
bbce6d69 | 3057 | |
c17cdb72 NC |
3058 | =for Pod::Functions get the integer portion of a number |
3059 | ||
7660c0ab | 3060 | Returns the integer portion of EXPR. If EXPR is omitted, uses C<$_>. |
2b5ab1e7 | 3061 | You should not use this function for rounding: one because it truncates |
3b10bc60 | 3062 | towards C<0>, and two because machine representations of floating-point |
2b5ab1e7 TC |
3063 | numbers can sometimes produce counterintuitive results. For example, |
3064 | C<int(-6.725/0.025)> produces -268 rather than the correct -269; that's | |
3065 | because it's really more like -268.99999999999994315658 instead. Usually, | |
19799a22 | 3066 | the C<sprintf>, C<printf>, or the C<POSIX::floor> and C<POSIX::ceil> |
2b5ab1e7 | 3067 | functions will serve you better than will int(). |
a0d0e21e LW |
3068 | |
3069 | =item ioctl FILEHANDLE,FUNCTION,SCALAR | |
d74e8afc | 3070 | X<ioctl> |
a0d0e21e | 3071 | |
c17cdb72 NC |
3072 | =for Pod::Functions system-dependent device control system call |
3073 | ||
2b5ab1e7 | 3074 | Implements the ioctl(2) function. You'll probably first have to say |
a0d0e21e | 3075 | |
f7051f2c FC |
3076 | require "sys/ioctl.ph"; # probably in |
3077 | # $Config{archlib}/sys/ioctl.ph | |
a0d0e21e | 3078 | |
a11c483f | 3079 | to get the correct function definitions. If F<sys/ioctl.ph> doesn't |
a0d0e21e | 3080 | exist or doesn't have the correct definitions you'll have to roll your |
61eff3bc | 3081 | own, based on your C header files such as F<< <sys/ioctl.h> >>. |
5a964f20 | 3082 | (There is a Perl script called B<h2ph> that comes with the Perl kit that |
54310121 | 3083 | may help you in this, but it's nontrivial.) SCALAR will be read and/or |
3b10bc60 | 3084 | written depending on the FUNCTION; a C pointer to the string value of SCALAR |
19799a22 | 3085 | will be passed as the third argument of the actual C<ioctl> call. (If SCALAR |
4633a7c4 LW |
3086 | has no string value but does have a numeric value, that value will be |
3087 | passed rather than a pointer to the string value. To guarantee this to be | |
19799a22 GS |
3088 | true, add a C<0> to the scalar before using it.) The C<pack> and C<unpack> |
3089 | functions may be needed to manipulate the values of structures used by | |
b76cc8ba | 3090 | C<ioctl>. |
a0d0e21e | 3091 | |
19799a22 | 3092 | The return value of C<ioctl> (and C<fcntl>) is as follows: |
a0d0e21e | 3093 | |
5ed4f2ec | 3094 | if OS returns: then Perl returns: |
3095 | -1 undefined value | |
3096 | 0 string "0 but true" | |
3097 | anything else that number | |
a0d0e21e | 3098 | |
19799a22 | 3099 | Thus Perl returns true on success and false on failure, yet you can |
a0d0e21e LW |
3100 | still easily determine the actual value returned by the operating |
3101 | system: | |
3102 | ||
2b5ab1e7 | 3103 | $retval = ioctl(...) || -1; |
a0d0e21e LW |
3104 | printf "System returned %d\n", $retval; |
3105 | ||
be2f7487 | 3106 | The special string C<"0 but true"> is exempt from B<-w> complaints |
5a964f20 TC |
3107 | about improper numeric conversions. |
3108 | ||
ea9eb35a BJ |
3109 | Portability issues: L<perlport/ioctl>. |
3110 | ||
a0d0e21e | 3111 | =item join EXPR,LIST |
d74e8afc | 3112 | X<join> |
a0d0e21e | 3113 | |
c17cdb72 NC |
3114 | =for Pod::Functions join a list into a string using a separator |
3115 | ||
2b5ab1e7 TC |
3116 | Joins the separate strings of LIST into a single string with fields |
3117 | separated by the value of EXPR, and returns that new string. Example: | |
a0d0e21e | 3118 | |
2b5ab1e7 | 3119 | $rec = join(':', $login,$passwd,$uid,$gid,$gcos,$home,$shell); |
a0d0e21e | 3120 | |
eb6e2d6f GS |
3121 | Beware that unlike C<split>, C<join> doesn't take a pattern as its |
3122 | first argument. Compare L</split>. | |
a0d0e21e | 3123 | |
532eee96 | 3124 | =item keys HASH |
d74e8afc | 3125 | X<keys> X<key> |
aa689395 | 3126 | |
532eee96 | 3127 | =item keys ARRAY |
aeedbbed | 3128 | |
f5a93a43 TC |
3129 | =item keys EXPR |
3130 | ||
c17cdb72 NC |
3131 | =for Pod::Functions retrieve list of indices from a hash |
3132 | ||
bade7fbc TC |
3133 | Called in list context, returns a list consisting of all the keys of the |
3134 | named hash, or in Perl 5.12 or later only, the indices of an array. Perl | |
3135 | releases prior to 5.12 will produce a syntax error if you try to use an | |
3136 | array argument. In scalar context, returns the number of keys or indices. | |
504f80c1 | 3137 | |
7bf59113 YO |
3138 | Hash entries are returned in an apparently random order. The actual random |
3139 | order is specific to a given hash; the exact same series of operations | |
7161e5c2 | 3140 | on two hashes may result in a different order for each hash. Any insertion |
7bf59113 YO |
3141 | into the hash may change the order, as will any deletion, with the exception |
3142 | that the most recent key returned by C<each> or C<keys> may be deleted | |
7161e5c2 | 3143 | without changing the order. So long as a given hash is unmodified you may |
7bf59113 | 3144 | rely on C<keys>, C<values> and C<each> to repeatedly return the same order |
7161e5c2 FC |
3145 | as each other. See L<perlsec/"Algorithmic Complexity Attacks"> for |
3146 | details on why hash order is randomized. Aside from the guarantees | |
7bf59113 YO |
3147 | provided here the exact details of Perl's hash algorithm and the hash |
3148 | traversal order are subject to change in any release of Perl. | |
504f80c1 | 3149 | |
a02807f8 JK |
3150 | As a side effect, calling keys() resets the internal iterator of the HASH or |
3151 | ARRAY (see L</each>). In particular, calling keys() in void context resets | |
cf264981 | 3152 | the iterator with no other overhead. |
a0d0e21e | 3153 | |
aa689395 | 3154 | Here is yet another way to print your environment: |
a0d0e21e LW |
3155 | |
3156 | @keys = keys %ENV; | |
3157 | @values = values %ENV; | |
b76cc8ba | 3158 | while (@keys) { |
a9a5a0dc | 3159 | print pop(@keys), '=', pop(@values), "\n"; |
a0d0e21e LW |
3160 | } |
3161 | ||
3162 | or how about sorted by key: | |
3163 | ||
3164 | foreach $key (sort(keys %ENV)) { | |
a9a5a0dc | 3165 | print $key, '=', $ENV{$key}, "\n"; |
a0d0e21e LW |
3166 | } |
3167 | ||
8ea1e5d4 GS |
3168 | The returned values are copies of the original keys in the hash, so |
3169 | modifying them will not affect the original hash. Compare L</values>. | |
3170 | ||
19799a22 | 3171 | To sort a hash by value, you'll need to use a C<sort> function. |
aa689395 | 3172 | Here's a descending numeric sort of a hash by its values: |
4633a7c4 | 3173 | |
5a964f20 | 3174 | foreach $key (sort { $hash{$b} <=> $hash{$a} } keys %hash) { |
a9a5a0dc | 3175 | printf "%4d %s\n", $hash{$key}, $key; |
4633a7c4 LW |
3176 | } |
3177 | ||
3b10bc60 | 3178 | Used as an lvalue, C<keys> allows you to increase the number of hash buckets |
aa689395 | 3179 | allocated for the given hash. This can gain you a measure of efficiency if |
3180 | you know the hash is going to get big. (This is similar to pre-extending | |
3181 | an array by assigning a larger number to $#array.) If you say | |
55497cff | 3182 | |
3183 | keys %hash = 200; | |
3184 | ||
ab192400 GS |
3185 | then C<%hash> will have at least 200 buckets allocated for it--256 of them, |
3186 | in fact, since it rounds up to the next power of two. These | |
55497cff | 3187 | buckets will be retained even if you do C<%hash = ()>, use C<undef |
3188 | %hash> if you want to free the storage while C<%hash> is still in scope. | |
3189 | You can't shrink the number of buckets allocated for the hash using | |
19799a22 | 3190 | C<keys> in this way (but you needn't worry about doing this by accident, |
0d3e3823 | 3191 | as trying has no effect). C<keys @array> in an lvalue context is a syntax |
aeedbbed | 3192 | error. |
55497cff | 3193 | |
f5a93a43 TC |
3194 | Starting with Perl 5.14, C<keys> can take a scalar EXPR, which must contain |
3195 | a reference to an unblessed hash or array. The argument will be | |
3196 | dereferenced automatically. This aspect of C<keys> is considered highly | |
3197 | experimental. The exact behaviour may change in a future version of Perl. | |
cba5a3b0 DG |
3198 | |
3199 | for (keys $hashref) { ... } | |
3200 | for (keys $obj->get_arrayref) { ... } | |
3201 | ||
bade7fbc TC |
3202 | To avoid confusing would-be users of your code who are running earlier |
3203 | versions of Perl with mysterious syntax errors, put this sort of thing at | |
3204 | the top of your file to signal that your code will work I<only> on Perls of | |
3205 | a recent vintage: | |
3206 | ||
3207 | use 5.012; # so keys/values/each work on arrays | |
3208 | use 5.014; # so keys/values/each work on scalars (experimental) | |
3209 | ||
8f1da26d | 3210 | See also C<each>, C<values>, and C<sort>. |
ab192400 | 3211 | |
b350dd2f | 3212 | =item kill SIGNAL, LIST |
9c7e4b76 KW |
3213 | |
3214 | =item kill SIGNAL | |
d74e8afc | 3215 | X<kill> X<signal> |
a0d0e21e | 3216 | |
c17cdb72 NC |
3217 | =for Pod::Functions send a signal to a process or process group |
3218 | ||
b350dd2f | 3219 | Sends a signal to a list of processes. Returns the number of |
517db077 GS |
3220 | processes successfully signaled (which is not necessarily the |
3221 | same as the number actually killed). | |
a0d0e21e | 3222 | |
1ac81c06 LM |
3223 | $cnt = kill 'HUP', $child1, $child2; |
3224 | kill 'KILL', @goners; | |
3225 | ||
3226 | SIGNAL may be either a signal name (a string) or a signal number. A signal | |
16bf540f | 3227 | name may start with a C<SIG> prefix, thus C<FOO> and C<SIGFOO> refer to the |
1ac81c06 LM |
3228 | same signal. The string form of SIGNAL is recommended for portability because |
3229 | the same signal may have different numbers in different operating systems. | |
3230 | ||
3231 | A list of signal names supported by the current platform can be found in | |
7161e5c2 | 3232 | C<$Config{sig_name}>, which is provided by the C<Config> module. See L<Config> |
1ac81c06 LM |
3233 | for more details. |
3234 | ||
3235 | A negative signal name is the same as a negative signal number, killing process | |
3236 | groups instead of processes. For example, C<kill '-KILL', $pgrp> and | |
7161e5c2 FC |
3237 | C<kill -9, $pgrp> will send C<SIGKILL> to |
3238 | the entire process group specified. That | |
1ac81c06 LM |
3239 | means you usually want to use positive not negative signals. |
3240 | ||
3875f14c | 3241 | If SIGNAL is either the number 0 or the string C<ZERO> (or C<SIGZERO>), |
16bf540f | 3242 | no signal is sent to |
1ac81c06 LM |
3243 | the process, but C<kill> checks whether it's I<possible> to send a signal to it |
3244 | (that means, to be brief, that the process is owned by the same user, or we are | |
3b10bc60 | 3245 | the super-user). This is useful to check that a child process is still |
81fd35db DN |
3246 | alive (even if only as a zombie) and hasn't changed its UID. See |
3247 | L<perlport> for notes on the portability of this construct. | |
b350dd2f | 3248 | |
e2c0f81f DG |
3249 | The behavior of kill when a I<PROCESS> number is zero or negative depends on |
3250 | the operating system. For example, on POSIX-conforming systems, zero will | |
c2fd40cb DM |
3251 | signal the current process group, -1 will signal all processes, and any |
3252 | other negative PROCESS number will act as a negative signal number and | |
3253 | kill the entire process group specified. | |
3254 | ||
3255 | If both the SIGNAL and the PROCESS are negative, the results are undefined. | |
3256 | A warning may be produced in a future version. | |
1e9c1022 JL |
3257 | |
3258 | See L<perlipc/"Signals"> for more details. | |
a0d0e21e | 3259 | |
ea9eb35a BJ |
3260 | On some platforms such as Windows where the fork() system call is not available. |
3261 | Perl can be built to emulate fork() at the interpreter level. | |
6d17f725 | 3262 | This emulation has limitations related to kill that have to be considered, |
ea9eb35a BJ |
3263 | for code running on Windows and in code intended to be portable. |
3264 | ||
3265 | See L<perlfork> for more details. | |
3266 | ||
9c7e4b76 KW |
3267 | If there is no I<LIST> of processes, no signal is sent, and the return |
3268 | value is 0. This form is sometimes used, however, because it causes | |
3269 | tainting checks to be run. But see | |
3270 | L<perlsec/Laundering and Detecting Tainted Data>. | |
3271 | ||
ea9eb35a BJ |
3272 | Portability issues: L<perlport/kill>. |
3273 | ||
a0d0e21e | 3274 | =item last LABEL |
d74e8afc | 3275 | X<last> X<break> |
a0d0e21e | 3276 | |
8a7e748e FC |
3277 | =item last EXPR |
3278 | ||
a0d0e21e LW |
3279 | =item last |
3280 | ||
c17cdb72 NC |
3281 | =for Pod::Functions exit a block prematurely |
3282 | ||
a0d0e21e LW |
3283 | The C<last> command is like the C<break> statement in C (as used in |
3284 | loops); it immediately exits the loop in question. If the LABEL is | |
8a7e748e FC |
3285 | omitted, the command refers to the innermost enclosing |
3286 | loop. The C<last EXPR> form, available starting in Perl | |
3287 | 5.18.0, allows a label name to be computed at run time, | |
3288 | and is otherwise identical to C<last LABEL>. The | |
a0d0e21e LW |
3289 | C<continue> block, if any, is not executed: |
3290 | ||
4633a7c4 | 3291 | LINE: while (<STDIN>) { |
a9a5a0dc VP |
3292 | last LINE if /^$/; # exit when done with header |
3293 | #... | |
a0d0e21e LW |
3294 | } |
3295 | ||
80d38338 | 3296 | C<last> cannot be used to exit a block that returns a value such as |
8f1da26d | 3297 | C<eval {}>, C<sub {}>, or C<do {}>, and should not be used to exit |
2b5ab1e7 | 3298 | a grep() or map() operation. |
4968c1e4 | 3299 | |
6c1372ed GS |
3300 | Note that a block by itself is semantically identical to a loop |
3301 | that executes once. Thus C<last> can be used to effect an early | |
3302 | exit out of such a block. | |
3303 | ||
98293880 JH |
3304 | See also L</continue> for an illustration of how C<last>, C<next>, and |
3305 | C<redo> work. | |
1d2dff63 | 3306 | |
2ba1f20a FC |
3307 | Unlike most named operators, this has the same precedence as assignment. |
3308 | It is also exempt from the looks-like-a-function rule, so | |
3309 | C<last ("foo")."bar"> will cause "bar" to be part of the argument to | |
3310 | C<last>. | |
3311 | ||
a0d0e21e | 3312 | =item lc EXPR |
d74e8afc | 3313 | X<lc> X<lowercase> |
a0d0e21e | 3314 | |
54310121 | 3315 | =item lc |
bbce6d69 | 3316 | |
c17cdb72 NC |
3317 | =for Pod::Functions return lower-case version of a string |
3318 | ||
d1be9408 | 3319 | Returns a lowercased version of EXPR. This is the internal function |
3980dc9c | 3320 | implementing the C<\L> escape in double-quoted strings. |
a0d0e21e | 3321 | |
7660c0ab | 3322 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 3323 | |
3980dc9c KW |
3324 | What gets returned depends on several factors: |
3325 | ||
3326 | =over | |
3327 | ||
3328 | =item If C<use bytes> is in effect: | |
3329 | ||
a93e23f1 KW |
3330 | The results follow ASCII semantics. Only the characters C<A-Z> change, |
3331 | to C<a-z> respectively. | |
3980dc9c | 3332 | |
66cbab2c | 3333 | =item Otherwise, if C<use locale> (but not C<use locale ':not_characters'>) is in effect: |
3980dc9c | 3334 | |
094a2f8c KW |
3335 | Respects current LC_CTYPE locale for code points < 256; and uses Unicode |
3336 | semantics for the remaining code points (this last can only happen if | |
3337 | the UTF8 flag is also set). See L<perllocale>. | |
3980dc9c | 3338 | |
31f05a37 KW |
3339 | Starting in v5.20, Perl wil use full Unicode rules if the locale is |
3340 | UTF-8. Otherwise, there is a deficiency in this scheme, which is that | |
3341 | case changes that cross the 255/256 | |
094a2f8c KW |
3342 | boundary are not well-defined. For example, the lower case of LATIN CAPITAL |
3343 | LETTER SHARP S (U+1E9E) in Unicode semantics is U+00DF (on ASCII | |
31f05a37 KW |
3344 | platforms). But under C<use locale> (prior to v5.20 or not a UTF-8 |
3345 | locale), the lower case of U+1E9E is | |
094a2f8c KW |
3346 | itself, because 0xDF may not be LATIN SMALL LETTER SHARP S in the |
3347 | current locale, and Perl has no way of knowing if that character even | |
3348 | exists in the locale, much less what code point it is. Perl returns | |
3349 | the input character unchanged, for all instances (and there aren't | |
3350 | many) where the 255/256 boundary would otherwise be crossed. | |
3980dc9c | 3351 | |
66cbab2c | 3352 | =item Otherwise, If EXPR has the UTF8 flag set: |
094a2f8c KW |
3353 | |
3354 | Unicode semantics are used for the case change. | |
3980dc9c | 3355 | |
48cbae4f | 3356 | =item Otherwise, if C<use feature 'unicode_strings'> or C<use locale ':not_characters'> is in effect: |
3980dc9c | 3357 | |
5d1892be | 3358 | Unicode semantics are used for the case change. |
3980dc9c KW |
3359 | |
3360 | =item Otherwise: | |
3361 | ||
3980dc9c KW |
3362 | ASCII semantics are used for the case change. The lowercase of any character |
3363 | outside the ASCII range is the character itself. | |
3364 | ||
3365 | =back | |
3366 | ||
a0d0e21e | 3367 | =item lcfirst EXPR |
d74e8afc | 3368 | X<lcfirst> X<lowercase> |
a0d0e21e | 3369 | |
54310121 | 3370 | =item lcfirst |
bbce6d69 | 3371 | |
c17cdb72 NC |
3372 | =for Pod::Functions return a string with just the next letter in lower case |
3373 | ||
ad0029c4 JH |
3374 | Returns the value of EXPR with the first character lowercased. This |
3375 | is the internal function implementing the C<\l> escape in | |
3980dc9c | 3376 | double-quoted strings. |
a0d0e21e | 3377 | |
7660c0ab | 3378 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 3379 | |
15dbbbab | 3380 | This function behaves the same way under various pragmata, such as in a locale, |
3980dc9c KW |
3381 | as L</lc> does. |
3382 | ||
a0d0e21e | 3383 | =item length EXPR |
d74e8afc | 3384 | X<length> X<size> |
a0d0e21e | 3385 | |
54310121 | 3386 | =item length |
bbce6d69 | 3387 | |
c52f983f | 3388 | =for Pod::Functions return the number of characters in a string |
c17cdb72 | 3389 | |
974da8e5 | 3390 | Returns the length in I<characters> of the value of EXPR. If EXPR is |
15dbbbab FC |
3391 | omitted, returns the length of C<$_>. If EXPR is undefined, returns |
3392 | C<undef>. | |
3b10bc60 | 3393 | |
3394 | This function cannot be used on an entire array or hash to find out how | |
3395 | many elements these have. For that, use C<scalar @array> and C<scalar keys | |
3396 | %hash>, respectively. | |
3397 | ||
3398 | Like all Perl character operations, length() normally deals in logical | |
3399 | characters, not physical bytes. For how many bytes a string encoded as | |
3400 | UTF-8 would take up, use C<length(Encode::encode_utf8(EXPR))> (you'll have | |
3401 | to C<use Encode> first). See L<Encode> and L<perlunicode>. | |
974da8e5 | 3402 | |
cfa52385 FC |
3403 | =item __LINE__ |
3404 | X<__LINE__> | |
3405 | ||
c17cdb72 NC |
3406 | =for Pod::Functions the current source line number |
3407 | ||
cfa52385 FC |
3408 | A special token that compiles to the current line number. |
3409 | ||
a0d0e21e | 3410 | =item link OLDFILE,NEWFILE |
d74e8afc | 3411 | X<link> |
a0d0e21e | 3412 | |
c17cdb72 NC |
3413 | =for Pod::Functions create a hard link in the filesystem |
3414 | ||
19799a22 | 3415 | Creates a new filename linked to the old filename. Returns true for |
b76cc8ba | 3416 | success, false otherwise. |
a0d0e21e | 3417 | |
ea9eb35a BJ |
3418 | Portability issues: L<perlport/link>. |
3419 | ||
a0d0e21e | 3420 | =item listen SOCKET,QUEUESIZE |
d74e8afc | 3421 | X<listen> |
a0d0e21e | 3422 | |
c17cdb72 NC |
3423 | =for Pod::Functions register your socket as a server |
3424 | ||
3b10bc60 | 3425 | Does the same thing that the listen(2) system call does. Returns true if |
b76cc8ba | 3426 | it succeeded, false otherwise. See the example in |
cea6626f | 3427 | L<perlipc/"Sockets: Client/Server Communication">. |
a0d0e21e LW |
3428 | |
3429 | =item local EXPR | |
d74e8afc | 3430 | X<local> |
a0d0e21e | 3431 | |
c17cdb72 NC |
3432 | =for Pod::Functions create a temporary value for a global variable (dynamic scoping) |
3433 | ||
19799a22 | 3434 | You really probably want to be using C<my> instead, because C<local> isn't |
b76cc8ba | 3435 | what most people think of as "local". See |
13a2d996 | 3436 | L<perlsub/"Private Variables via my()"> for details. |
2b5ab1e7 | 3437 | |
5a964f20 TC |
3438 | A local modifies the listed variables to be local to the enclosing |
3439 | block, file, or eval. If more than one value is listed, the list must | |
3440 | be placed in parentheses. See L<perlsub/"Temporary Values via local()"> | |
3441 | for details, including issues with tied arrays and hashes. | |
a0d0e21e | 3442 | |
d361fafa VP |
3443 | The C<delete local EXPR> construct can also be used to localize the deletion |
3444 | of array/hash elements to the current block. | |
3445 | See L<perlsub/"Localized deletion of elements of composite types">. | |
3446 | ||
a0d0e21e | 3447 | =item localtime EXPR |
435fbc73 | 3448 | X<localtime> X<ctime> |
a0d0e21e | 3449 | |
ba053783 AL |
3450 | =item localtime |
3451 | ||
c17cdb72 NC |
3452 | =for Pod::Functions convert UNIX time into record or string using local time |
3453 | ||
19799a22 | 3454 | Converts a time as returned by the time function to a 9-element list |
5f05dabc | 3455 | with the time analyzed for the local time zone. Typically used as |
a0d0e21e LW |
3456 | follows: |
3457 | ||
54310121 | 3458 | # 0 1 2 3 4 5 6 7 8 |
a0d0e21e | 3459 | ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = |
ba053783 | 3460 | localtime(time); |
a0d0e21e | 3461 | |
8f1da26d | 3462 | All list elements are numeric and come straight out of the C `struct |
ba053783 AL |
3463 | tm'. C<$sec>, C<$min>, and C<$hour> are the seconds, minutes, and hours |
3464 | of the specified time. | |
48a26b3a | 3465 | |
8f1da26d TC |
3466 | C<$mday> is the day of the month and C<$mon> the month in |
3467 | the range C<0..11>, with 0 indicating January and 11 indicating December. | |
ba053783 | 3468 | This makes it easy to get a month name from a list: |
54310121 | 3469 | |
f7051f2c | 3470 | my @abbr = qw(Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec); |
ba053783 AL |
3471 | print "$abbr[$mon] $mday"; |
3472 | # $mon=9, $mday=18 gives "Oct 18" | |
abd75f24 | 3473 | |
0d3e3823 | 3474 | C<$year> contains the number of years since 1900. To get a 4-digit |
570b1bb1 | 3475 | year write: |
abd75f24 | 3476 | |
ba053783 | 3477 | $year += 1900; |
abd75f24 | 3478 | |
8f1da26d | 3479 | To get the last two digits of the year (e.g., "01" in 2001) do: |
ba053783 AL |
3480 | |
3481 | $year = sprintf("%02d", $year % 100); | |
3482 | ||
3483 | C<$wday> is the day of the week, with 0 indicating Sunday and 3 indicating | |
3484 | Wednesday. C<$yday> is the day of the year, in the range C<0..364> | |
3485 | (or C<0..365> in leap years.) | |
3486 | ||
3487 | C<$isdst> is true if the specified time occurs during Daylight Saving | |
3488 | Time, false otherwise. | |
abd75f24 | 3489 | |
e1998452 | 3490 | If EXPR is omitted, C<localtime()> uses the current time (as returned |
e3176d09 | 3491 | by time(3)). |
a0d0e21e | 3492 | |
48a26b3a | 3493 | In scalar context, C<localtime()> returns the ctime(3) value: |
a0d0e21e | 3494 | |
5f05dabc | 3495 | $now_string = localtime; # e.g., "Thu Oct 13 04:54:34 1994" |
a0d0e21e | 3496 | |
391b733c FC |
3497 | The format of this scalar value is B<not> locale-dependent |
3498 | but built into Perl. For GMT instead of local | |
3499 | time use the L</gmtime> builtin. See also the | |
8f1da26d | 3500 | C<Time::Local> module (for converting seconds, minutes, hours, and such back to |
fe86afc2 NC |
3501 | the integer value returned by time()), and the L<POSIX> module's strftime(3) |
3502 | and mktime(3) functions. | |
3503 | ||
15dbbbab | 3504 | To get somewhat similar but locale-dependent date strings, set up your |
fe86afc2 NC |
3505 | locale environment variables appropriately (please see L<perllocale>) and |
3506 | try for example: | |
a3cb178b | 3507 | |
5a964f20 | 3508 | use POSIX qw(strftime); |
2b5ab1e7 | 3509 | $now_string = strftime "%a %b %e %H:%M:%S %Y", localtime; |
fe86afc2 NC |
3510 | # or for GMT formatted appropriately for your locale: |
3511 | $now_string = strftime "%a %b %e %H:%M:%S %Y", gmtime; | |
a3cb178b GS |
3512 | |
3513 | Note that the C<%a> and C<%b>, the short forms of the day of the week | |
3514 | and the month of the year, may not necessarily be three characters wide. | |
a0d0e21e | 3515 | |
15dbbbab | 3516 | The L<Time::gmtime> and L<Time::localtime> modules provide a convenient, |
435fbc73 GS |
3517 | by-name access mechanism to the gmtime() and localtime() functions, |
3518 | respectively. | |
3519 | ||
3520 | For a comprehensive date and time representation look at the | |
3521 | L<DateTime> module on CPAN. | |
3522 | ||
ea9eb35a BJ |
3523 | Portability issues: L<perlport/localtime>. |
3524 | ||
07698885 | 3525 | =item lock THING |
d74e8afc | 3526 | X<lock> |
19799a22 | 3527 | |
d9b04284 | 3528 | =for Pod::Functions +5.005 get a thread lock on a variable, subroutine, or method |
c17cdb72 | 3529 | |
15dbbbab | 3530 | This function places an advisory lock on a shared variable or referenced |
03730085 | 3531 | object contained in I<THING> until the lock goes out of scope. |
a6d5524e | 3532 | |
904028df | 3533 | The value returned is the scalar itself, if the argument is a scalar, or a |
f79aa60b | 3534 | reference, if the argument is a hash, array or subroutine. |
904028df | 3535 | |
f3a23afb | 3536 | lock() is a "weak keyword" : this means that if you've defined a function |
67408cae | 3537 | by this name (before any calls to it), that function will be called |
7b043ca5 RGS |
3538 | instead. If you are not under C<use threads::shared> this does nothing. |
3539 | See L<threads::shared>. | |
19799a22 | 3540 | |
a0d0e21e | 3541 | =item log EXPR |
d74e8afc | 3542 | X<log> X<logarithm> X<e> X<ln> X<base> |
a0d0e21e | 3543 | |
54310121 | 3544 | =item log |
bbce6d69 | 3545 | |
c17cdb72 NC |
3546 | =for Pod::Functions retrieve the natural logarithm for a number |
3547 | ||
2b5ab1e7 | 3548 | Returns the natural logarithm (base I<e>) of EXPR. If EXPR is omitted, |
15dbbbab FC |
3549 | returns the log of C<$_>. To get the |
3550 | log of another base, use basic algebra: | |
19799a22 | 3551 | The base-N log of a number is equal to the natural log of that number |
2b5ab1e7 TC |
3552 | divided by the natural log of N. For example: |
3553 | ||
3554 | sub log10 { | |
a9a5a0dc VP |
3555 | my $n = shift; |
3556 | return log($n)/log(10); | |
b76cc8ba | 3557 | } |
2b5ab1e7 TC |
3558 | |
3559 | See also L</exp> for the inverse operation. | |
a0d0e21e | 3560 | |
7ded94be | 3561 | =item lstat FILEHANDLE |
d74e8afc | 3562 | X<lstat> |
a0d0e21e | 3563 | |
7ded94be FC |
3564 | =item lstat EXPR |
3565 | ||
3566 | =item lstat DIRHANDLE | |
3567 | ||
54310121 | 3568 | =item lstat |
bbce6d69 | 3569 | |
c17cdb72 NC |
3570 | =for Pod::Functions stat a symbolic link |
3571 | ||
19799a22 | 3572 | Does the same thing as the C<stat> function (including setting the |
5a964f20 TC |
3573 | special C<_> filehandle) but stats a symbolic link instead of the file |
3574 | the symbolic link points to. If symbolic links are unimplemented on | |
c837d5b4 DP |
3575 | your system, a normal C<stat> is done. For much more detailed |
3576 | information, please see the documentation for C<stat>. | |
a0d0e21e | 3577 | |
7660c0ab | 3578 | If EXPR is omitted, stats C<$_>. |
bbce6d69 | 3579 | |
ea9eb35a BJ |
3580 | Portability issues: L<perlport/lstat>. |
3581 | ||
a0d0e21e LW |
3582 | =item m// |
3583 | ||
c17cdb72 NC |
3584 | =for Pod::Functions match a string with a regular expression pattern |
3585 | ||
9f4b9cd0 | 3586 | The match operator. See L<perlop/"Regexp Quote-Like Operators">. |
a0d0e21e LW |
3587 | |
3588 | =item map BLOCK LIST | |
d74e8afc | 3589 | X<map> |
a0d0e21e LW |
3590 | |
3591 | =item map EXPR,LIST | |
3592 | ||
c17cdb72 NC |
3593 | =for Pod::Functions apply a change to a list to get back a new list with the changes |
3594 | ||
19799a22 GS |
3595 | Evaluates the BLOCK or EXPR for each element of LIST (locally setting |
3596 | C<$_> to each element) and returns the list value composed of the | |
3597 | results of each such evaluation. In scalar context, returns the | |
3598 | total number of elements so generated. Evaluates BLOCK or EXPR in | |
3599 | list context, so each element of LIST may produce zero, one, or | |
3600 | more elements in the returned value. | |
dd99ebda | 3601 | |
f9476272 | 3602 | @chars = map(chr, @numbers); |
a0d0e21e | 3603 | |
f9476272 AH |
3604 | translates a list of numbers to the corresponding characters. |
3605 | ||
3606 | my @squares = map { $_ * $_ } @numbers; | |
3607 | ||
3608 | translates a list of numbers to their squared values. | |
3609 | ||
3610 | my @squares = map { $_ > 5 ? ($_ * $_) : () } @numbers; | |
3611 | ||
3612 | shows that number of returned elements can differ from the number of | |
391b733c | 3613 | input elements. To omit an element, return an empty list (). |
f9476272 AH |
3614 | This could also be achieved by writing |
3615 | ||
3616 | my @squares = map { $_ * $_ } grep { $_ > 5 } @numbers; | |
3617 | ||
3618 | which makes the intention more clear. | |
3619 | ||
15dbbbab FC |
3620 | Map always returns a list, which can be |
3621 | assigned to a hash such that the elements | |
391b733c | 3622 | become key/value pairs. See L<perldata> for more details. |
a0d0e21e | 3623 | |
d8216f19 | 3624 | %hash = map { get_a_key_for($_) => $_ } @array; |
a0d0e21e LW |
3625 | |
3626 | is just a funny way to write | |
3627 | ||
3628 | %hash = (); | |
d8216f19 | 3629 | foreach (@array) { |
a9a5a0dc | 3630 | $hash{get_a_key_for($_)} = $_; |
a0d0e21e LW |
3631 | } |
3632 | ||
be3174d2 GS |
3633 | Note that C<$_> is an alias to the list value, so it can be used to |
3634 | modify the elements of the LIST. While this is useful and supported, | |
3635 | it can cause bizarre results if the elements of LIST are not variables. | |
2b5ab1e7 TC |
3636 | Using a regular C<foreach> loop for this purpose would be clearer in |
3637 | most cases. See also L</grep> for an array composed of those items of | |
3638 | the original list for which the BLOCK or EXPR evaluates to true. | |
fb73857a | 3639 | |
a4fb8298 | 3640 | If C<$_> is lexical in the scope where the C<map> appears (because it has |
c071e214 FC |
3641 | been declared with the deprecated C<my $_> construct), |
3642 | then, in addition to being locally aliased to | |
d8216f19 | 3643 | the list elements, C<$_> keeps being lexical inside the block; that is, it |
a4fb8298 RGS |
3644 | can't be seen from the outside, avoiding any potential side-effects. |
3645 | ||
205fdb4d | 3646 | C<{> starts both hash references and blocks, so C<map { ...> could be either |
391b733c | 3647 | the start of map BLOCK LIST or map EXPR, LIST. Because Perl doesn't look |
80d38338 | 3648 | ahead for the closing C<}> it has to take a guess at which it's dealing with |
391b733c FC |
3649 | based on what it finds just after the |
3650 | C<{>. Usually it gets it right, but if it | |
205fdb4d | 3651 | doesn't it won't realize something is wrong until it gets to the C<}> and |
391b733c | 3652 | encounters the missing (or unexpected) comma. The syntax error will be |
80d38338 | 3653 | reported close to the C<}>, but you'll need to change something near the C<{> |
3b10bc60 | 3654 | such as using a unary C<+> to give Perl some help: |
205fdb4d | 3655 | |
f7051f2c FC |
3656 | %hash = map { "\L$_" => 1 } @array # perl guesses EXPR. wrong |
3657 | %hash = map { +"\L$_" => 1 } @array # perl guesses BLOCK. right | |
3658 | %hash = map { ("\L$_" => 1) } @array # this also works | |
3659 | %hash = map { lc($_) => 1 } @array # as does this. | |
3660 | %hash = map +( lc($_) => 1 ), @array # this is EXPR and works! | |
cea6626f | 3661 | |
f7051f2c | 3662 | %hash = map ( lc($_), 1 ), @array # evaluates to (1, @array) |
205fdb4d | 3663 | |
d8216f19 | 3664 | or to force an anon hash constructor use C<+{>: |
205fdb4d | 3665 | |
f7051f2c FC |
3666 | @hashes = map +{ lc($_) => 1 }, @array # EXPR, so needs |
3667 | # comma at end | |
205fdb4d | 3668 | |
3b10bc60 | 3669 | to get a list of anonymous hashes each with only one entry apiece. |
205fdb4d | 3670 | |
19799a22 | 3671 | =item mkdir FILENAME,MASK |
d74e8afc | 3672 | X<mkdir> X<md> X<directory, create> |
a0d0e21e | 3673 | |
5a211162 GS |
3674 | =item mkdir FILENAME |
3675 | ||
491873e5 RGS |
3676 | =item mkdir |
3677 | ||
c17cdb72 NC |
3678 | =for Pod::Functions create a directory |
3679 | ||
0591cd52 | 3680 | Creates the directory specified by FILENAME, with permissions |
19799a22 | 3681 | specified by MASK (as modified by C<umask>). If it succeeds it |
8f1da26d TC |
3682 | returns true; otherwise it returns false and sets C<$!> (errno). |
3683 | MASK defaults to 0777 if omitted, and FILENAME defaults | |
3684 | to C<$_> if omitted. | |
0591cd52 | 3685 | |
8f1da26d TC |
3686 | In general, it is better to create directories with a permissive MASK |
3687 | and let the user modify that with their C<umask> than it is to supply | |
19799a22 | 3688 | a restrictive MASK and give the user no way to be more permissive. |
0591cd52 NT |
3689 | The exceptions to this rule are when the file or directory should be |
3690 | kept private (mail files, for instance). The perlfunc(1) entry on | |
19799a22 | 3691 | C<umask> discusses the choice of MASK in more detail. |
a0d0e21e | 3692 | |
cc1852e8 JH |
3693 | Note that according to the POSIX 1003.1-1996 the FILENAME may have any |
3694 | number of trailing slashes. Some operating and filesystems do not get | |
3695 | this right, so Perl automatically removes all trailing slashes to keep | |
3696 | everyone happy. | |
3697 | ||
80d38338 | 3698 | To recursively create a directory structure, look at |
a22ececd | 3699 | the C<make_path> function of the L<File::Path> module. |
dd184578 | 3700 | |
a0d0e21e | 3701 | =item msgctl ID,CMD,ARG |
d74e8afc | 3702 | X<msgctl> |
a0d0e21e | 3703 | |
c17cdb72 NC |
3704 | =for Pod::Functions SysV IPC message control operations |
3705 | ||
f86cebdf | 3706 | Calls the System V IPC function msgctl(2). You'll probably have to say |
0ade1984 JH |
3707 | |
3708 | use IPC::SysV; | |
3709 | ||
7660c0ab | 3710 | first to get the correct constant definitions. If CMD is C<IPC_STAT>, |
cf264981 | 3711 | then ARG must be a variable that will hold the returned C<msqid_ds> |
951ba7fe GS |
3712 | structure. Returns like C<ioctl>: the undefined value for error, |
3713 | C<"0 but true"> for zero, or the actual return value otherwise. See also | |
15dbbbab FC |
3714 | L<perlipc/"SysV IPC"> and the documentation for C<IPC::SysV> and |
3715 | C<IPC::Semaphore>. | |
a0d0e21e | 3716 | |
ea9eb35a BJ |
3717 | Portability issues: L<perlport/msgctl>. |
3718 | ||
a0d0e21e | 3719 | =item msgget KEY,FLAGS |
d74e8afc | 3720 | X<msgget> |
a0d0e21e | 3721 | |
c17cdb72 NC |
3722 | =for Pod::Functions get SysV IPC message queue |
3723 | ||
f86cebdf | 3724 | Calls the System V IPC function msgget(2). Returns the message queue |
8f1da26d | 3725 | id, or C<undef> on error. See also |
15dbbbab FC |
3726 | L<perlipc/"SysV IPC"> and the documentation for C<IPC::SysV> and |
3727 | C<IPC::Msg>. | |
a0d0e21e | 3728 | |
ea9eb35a BJ |
3729 | Portability issues: L<perlport/msgget>. |
3730 | ||
a0d0e21e | 3731 | =item msgrcv ID,VAR,SIZE,TYPE,FLAGS |
d74e8afc | 3732 | X<msgrcv> |
a0d0e21e | 3733 | |
c17cdb72 NC |
3734 | =for Pod::Functions receive a SysV IPC message from a message queue |
3735 | ||
a0d0e21e LW |
3736 | Calls the System V IPC function msgrcv to receive a message from |
3737 | message queue ID into variable VAR with a maximum message size of | |
41d6edb2 JH |
3738 | SIZE. Note that when a message is received, the message type as a |
3739 | native long integer will be the first thing in VAR, followed by the | |
3740 | actual message. This packing may be opened with C<unpack("l! a*")>. | |
8f1da26d TC |
3741 | Taints the variable. Returns true if successful, false |
3742 | on error. See also L<perlipc/"SysV IPC"> and the documentation for | |
15dbbbab | 3743 | C<IPC::SysV> and C<IPC::SysV::Msg>. |
41d6edb2 | 3744 | |
ea9eb35a BJ |
3745 | Portability issues: L<perlport/msgrcv>. |
3746 | ||
41d6edb2 | 3747 | =item msgsnd ID,MSG,FLAGS |
d74e8afc | 3748 | X<msgsnd> |
41d6edb2 | 3749 | |
c17cdb72 NC |
3750 | =for Pod::Functions send a SysV IPC message to a message queue |
3751 | ||
41d6edb2 JH |
3752 | Calls the System V IPC function msgsnd to send the message MSG to the |
3753 | message queue ID. MSG must begin with the native long integer message | |
8f1da26d | 3754 | type, be followed by the length of the actual message, and then finally |
41d6edb2 JH |
3755 | the message itself. This kind of packing can be achieved with |
3756 | C<pack("l! a*", $type, $message)>. Returns true if successful, | |
8f1da26d | 3757 | false on error. See also the C<IPC::SysV> |
41d6edb2 | 3758 | and C<IPC::SysV::Msg> documentation. |
a0d0e21e | 3759 | |
ea9eb35a BJ |
3760 | Portability issues: L<perlport/msgsnd>. |
3761 | ||
672208d2 | 3762 | =item my VARLIST |
d74e8afc | 3763 | X<my> |
a0d0e21e | 3764 | |
672208d2 | 3765 | =item my TYPE VARLIST |
307ea6df | 3766 | |
672208d2 | 3767 | =item my VARLIST : ATTRS |
09bef843 | 3768 | |
672208d2 | 3769 | =item my TYPE VARLIST : ATTRS |
307ea6df | 3770 | |
c17cdb72 NC |
3771 | =for Pod::Functions declare and assign a local variable (lexical scoping) |
3772 | ||
19799a22 | 3773 | A C<my> declares the listed variables to be local (lexically) to the |
672208d2 | 3774 | enclosing block, file, or C<eval>. If more than one variable is listed, |
1d2de774 | 3775 | the list must be placed in parentheses. |
307ea6df | 3776 | |
1d2de774 | 3777 | The exact semantics and interface of TYPE and ATTRS are still |
ab461de4 FC |
3778 | evolving. TYPE may be a bareword, a constant declared |
3779 | with C<use constant>, or C<__PACKAGE__>. It is | |
3780 | currently bound to the use of the C<fields> pragma, | |
307ea6df JH |
3781 | and attributes are handled using the C<attributes> pragma, or starting |
3782 | from Perl 5.8.0 also via the C<Attribute::Handlers> module. See | |
3783 | L<perlsub/"Private Variables via my()"> for details, and L<fields>, | |
3784 | L<attributes>, and L<Attribute::Handlers>. | |
4633a7c4 | 3785 | |
672208d2 JV |
3786 | Note that with a parenthesised list, C<undef> can be used as a dummy |
3787 | placeholder, for example to skip assignment of initial values: | |
3788 | ||
3789 | my ( undef, $min, $hour ) = localtime; | |
3790 | ||
a0d0e21e | 3791 | =item next LABEL |
d74e8afc | 3792 | X<next> X<continue> |
a0d0e21e | 3793 | |
8a7e748e FC |
3794 | =item next EXPR |
3795 | ||
a0d0e21e LW |
3796 | =item next |
3797 | ||
c17cdb72 NC |
3798 | =for Pod::Functions iterate a block prematurely |
3799 | ||
a0d0e21e LW |
3800 | The C<next> command is like the C<continue> statement in C; it starts |
3801 | the next iteration of the loop: | |
3802 | ||
4633a7c4 | 3803 | LINE: while (<STDIN>) { |
a9a5a0dc VP |
3804 | next LINE if /^#/; # discard comments |
3805 | #... | |
a0d0e21e LW |
3806 | } |
3807 | ||
3808 | Note that if there were a C<continue> block on the above, it would get | |
3b10bc60 | 3809 | executed even on discarded lines. If LABEL is omitted, the command |
8a7e748e FC |
3810 | refers to the innermost enclosing loop. The C<next EXPR> form, available |
3811 | as of Perl 5.18.0, allows a label name to be computed at run time, being | |
3812 | otherwise identical to C<next LABEL>. | |
a0d0e21e | 3813 | |
4968c1e4 | 3814 | C<next> cannot be used to exit a block which returns a value such as |
8f1da26d | 3815 | C<eval {}>, C<sub {}>, or C<do {}>, and should not be used to exit |
2b5ab1e7 | 3816 | a grep() or map() operation. |
4968c1e4 | 3817 | |
6c1372ed GS |
3818 | Note that a block by itself is semantically identical to a loop |
3819 | that executes once. Thus C<next> will exit such a block early. | |
3820 | ||
98293880 JH |
3821 | See also L</continue> for an illustration of how C<last>, C<next>, and |
3822 | C<redo> work. | |
1d2dff63 | 3823 | |
2ba1f20a FC |
3824 | Unlike most named operators, this has the same precedence as assignment. |
3825 | It is also exempt from the looks-like-a-function rule, so | |
3826 | C<next ("foo")."bar"> will cause "bar" to be part of the argument to | |
3827 | C<next>. | |
3828 | ||
3b10bc60 | 3829 | =item no MODULE VERSION LIST |
3830 | X<no declarations> | |
3831 | X<unimporting> | |
4a66ea5a | 3832 | |
3b10bc60 | 3833 | =item no MODULE VERSION |
4a66ea5a | 3834 | |
3b10bc60 | 3835 | =item no MODULE LIST |
a0d0e21e | 3836 | |
3b10bc60 | 3837 | =item no MODULE |
4a66ea5a | 3838 | |
c986422f RGS |
3839 | =item no VERSION |
3840 | ||
c17cdb72 NC |
3841 | =for Pod::Functions unimport some module symbols or semantics at compile time |
3842 | ||
593b9c14 | 3843 | See the C<use> function, of which C<no> is the opposite. |
a0d0e21e LW |
3844 | |
3845 | =item oct EXPR | |
d74e8afc | 3846 | X<oct> X<octal> X<hex> X<hexadecimal> X<binary> X<bin> |
a0d0e21e | 3847 | |
54310121 | 3848 | =item oct |
bbce6d69 | 3849 | |
c17cdb72 NC |
3850 | =for Pod::Functions convert a string to an octal number |
3851 | ||
4633a7c4 | 3852 | Interprets EXPR as an octal string and returns the corresponding |
4f19785b WSI |
3853 | value. (If EXPR happens to start off with C<0x>, interprets it as a |
3854 | hex string. If EXPR starts off with C<0b>, it is interpreted as a | |
53305cf1 | 3855 | binary string. Leading whitespace is ignored in all three cases.) |
3b10bc60 | 3856 | The following will handle decimal, binary, octal, and hex in standard |
3857 | Perl notation: | |
a0d0e21e LW |
3858 | |
3859 | $val = oct($val) if $val =~ /^0/; | |
3860 | ||
19799a22 GS |
3861 | If EXPR is omitted, uses C<$_>. To go the other way (produce a number |
3862 | in octal), use sprintf() or printf(): | |
3863 | ||
3b10bc60 | 3864 | $dec_perms = (stat("filename"))[2] & 07777; |
3865 | $oct_perm_str = sprintf "%o", $perms; | |
19799a22 GS |
3866 | |
3867 | The oct() function is commonly used when a string such as C<644> needs | |
3b10bc60 | 3868 | to be converted into a file mode, for example. Although Perl |
3869 | automatically converts strings into numbers as needed, this automatic | |
3870 | conversion assumes base 10. | |
3871 | ||
3872 | Leading white space is ignored without warning, as too are any trailing | |
3873 | non-digits, such as a decimal point (C<oct> only handles non-negative | |
3874 | integers, not negative integers or floating point). | |
a0d0e21e LW |
3875 | |
3876 | =item open FILEHANDLE,EXPR | |
d74e8afc | 3877 | X<open> X<pipe> X<file, open> X<fopen> |
a0d0e21e | 3878 | |
68bd7414 NIS |
3879 | =item open FILEHANDLE,MODE,EXPR |
3880 | ||
3881 | =item open FILEHANDLE,MODE,EXPR,LIST | |
3882 | ||
ba964c95 T |
3883 | =item open FILEHANDLE,MODE,REFERENCE |
3884 | ||
a0d0e21e LW |
3885 | =item open FILEHANDLE |
3886 | ||
c17cdb72 NC |
3887 | =for Pod::Functions open a file, pipe, or descriptor |
3888 | ||
a0d0e21e | 3889 | Opens the file whose filename is given by EXPR, and associates it with |
ed53a2bb JH |
3890 | FILEHANDLE. |
3891 | ||
460b70c2 GS |
3892 | Simple examples to open a file for reading: |
3893 | ||
8f1da26d TC |
3894 | open(my $fh, "<", "input.txt") |
3895 | or die "cannot open < input.txt: $!"; | |
460b70c2 GS |
3896 | |
3897 | and for writing: | |
3898 | ||
8f1da26d TC |
3899 | open(my $fh, ">", "output.txt") |
3900 | or die "cannot open > output.txt: $!"; | |
460b70c2 | 3901 | |
ed53a2bb JH |
3902 | (The following is a comprehensive reference to open(): for a gentler |
3903 | introduction you may consider L<perlopentut>.) | |
3904 | ||
8f1da26d TC |
3905 | If FILEHANDLE is an undefined scalar variable (or array or hash element), a |
3906 | new filehandle is autovivified, meaning that the variable is assigned a | |
3907 | reference to a newly allocated anonymous filehandle. Otherwise if | |
3908 | FILEHANDLE is an expression, its value is the real filehandle. (This is | |
3909 | considered a symbolic reference, so C<use strict "refs"> should I<not> be | |
3910 | in effect.) | |
3911 | ||
8f1da26d TC |
3912 | If three (or more) arguments are specified, the open mode (including |
3913 | optional encoding) in the second argument are distinct from the filename in | |
3914 | the third. If MODE is C<< < >> or nothing, the file is opened for input. | |
3915 | If MODE is C<< > >>, the file is opened for output, with existing files | |
3916 | first being truncated ("clobbered") and nonexisting files newly created. | |
3917 | If MODE is C<<< >> >>>, the file is opened for appending, again being | |
3918 | created if necessary. | |
3919 | ||
3920 | You can put a C<+> in front of the C<< > >> or C<< < >> to | |
ed53a2bb | 3921 | indicate that you want both read and write access to the file; thus |
8f1da26d | 3922 | C<< +< >> is almost always preferred for read/write updates--the |
1dfd3418 | 3923 | C<< +> >> mode would clobber the file first. You can't usually use |
ed53a2bb | 3924 | either read-write mode for updating textfiles, since they have |
bea6df1c | 3925 | variable-length records. See the B<-i> switch in L<perlrun> for a |
ed53a2bb | 3926 | better approach. The file is created with permissions of C<0666> |
e1020413 | 3927 | modified by the process's C<umask> value. |
ed53a2bb | 3928 | |
8f1da26d TC |
3929 | These various prefixes correspond to the fopen(3) modes of C<r>, |
3930 | C<r+>, C<w>, C<w+>, C<a>, and C<a+>. | |
5f05dabc | 3931 | |
8f1da26d TC |
3932 | In the one- and two-argument forms of the call, the mode and filename |
3933 | should be concatenated (in that order), preferably separated by white | |
3934 | space. You can--but shouldn't--omit the mode in these forms when that mode | |
3935 | is C<< < >>. It is always safe to use the two-argument form of C<open> if | |
3936 | the filename argument is a known literal. | |
6170680b | 3937 | |
8f1da26d | 3938 | For three or more arguments if MODE is C<|->, the filename is |
ed53a2bb | 3939 | interpreted as a command to which output is to be piped, and if MODE |
8f1da26d | 3940 | is C<-|>, the filename is interpreted as a command that pipes |
3b10bc60 | 3941 | output to us. In the two-argument (and one-argument) form, one should |
8f1da26d | 3942 | replace dash (C<->) with the command. |
ed53a2bb JH |
3943 | See L<perlipc/"Using open() for IPC"> for more examples of this. |
3944 | (You are not allowed to C<open> to a command that pipes both in I<and> | |
3945 | out, but see L<IPC::Open2>, L<IPC::Open3>, and | |
96090e4f LB |
3946 | L<perlipc/"Bidirectional Communication with Another Process"> for |
3947 | alternatives.) | |
ed53a2bb | 3948 | |
3b10bc60 | 3949 | In the form of pipe opens taking three or more arguments, if LIST is specified |
ed53a2bb JH |
3950 | (extra arguments after the command name) then LIST becomes arguments |
3951 | to the command invoked if the platform supports it. The meaning of | |
3952 | C<open> with more than three arguments for non-pipe modes is not yet | |
3b10bc60 | 3953 | defined, but experimental "layers" may give extra LIST arguments |
ed53a2bb | 3954 | meaning. |
6170680b | 3955 | |
8f1da26d TC |
3956 | In the two-argument (and one-argument) form, opening C<< <- >> |
3957 | or C<-> opens STDIN and opening C<< >- >> opens STDOUT. | |
6170680b | 3958 | |
8f1da26d TC |
3959 | You may (and usually should) use the three-argument form of open to specify |
3960 | I/O layers (sometimes referred to as "disciplines") to apply to the handle | |
fae2c0fb | 3961 | that affect how the input and output are processed (see L<open> and |
391b733c | 3962 | L<PerlIO> for more details). For example: |
7207e29d | 3963 | |
3b10bc60 | 3964 | open(my $fh, "<:encoding(UTF-8)", "filename") |
3965 | || die "can't open UTF-8 encoded filename: $!"; | |
9124316e | 3966 | |
8f1da26d | 3967 | opens the UTF8-encoded file containing Unicode characters; |
391b733c | 3968 | see L<perluniintro>. Note that if layers are specified in the |
3b10bc60 | 3969 | three-argument form, then default layers stored in ${^OPEN} (see L<perlvar>; |
6d5e88a0 | 3970 | usually set by the B<open> pragma or the switch B<-CioD>) are ignored. |
c0fd9d21 FC |
3971 | Those layers will also be ignored if you specifying a colon with no name |
3972 | following it. In that case the default layer for the operating system | |
3973 | (:raw on Unix, :crlf on Windows) is used. | |
ed53a2bb | 3974 | |
80d38338 | 3975 | Open returns nonzero on success, the undefined value otherwise. If |
ed53a2bb JH |
3976 | the C<open> involved a pipe, the return value happens to be the pid of |
3977 | the subprocess. | |
cb1a09d0 | 3978 | |
ed53a2bb JH |
3979 | If you're running Perl on a system that distinguishes between text |
3980 | files and binary files, then you should check out L</binmode> for tips | |
3981 | for dealing with this. The key distinction between systems that need | |
3982 | C<binmode> and those that don't is their text file formats. Systems | |
80d38338 TC |
3983 | like Unix, Mac OS, and Plan 9, that end lines with a single |
3984 | character and encode that character in C as C<"\n"> do not | |
ed53a2bb | 3985 | need C<binmode>. The rest need it. |
cb1a09d0 | 3986 | |
80d38338 TC |
3987 | When opening a file, it's seldom a good idea to continue |
3988 | if the request failed, so C<open> is frequently used with | |
19799a22 | 3989 | C<die>. Even if C<die> won't do what you want (say, in a CGI script, |
80d38338 TC |
3990 | where you want to format a suitable error message (but there are |
3991 | modules that can help with that problem)) always check | |
3992 | the return value from opening a file. | |
fb73857a | 3993 | |
1578dcc9 EA |
3994 | The filehandle will be closed when its reference count reaches zero. |
3995 | If it is a lexically scoped variable declared with C<my>, that usually | |
3996 | means the end of the enclosing scope. However, this automatic close | |
3997 | does not check for errors, so it is better to explicitly close | |
3998 | filehandles, especially those used for writing: | |
3999 | ||
4000 | close($handle) | |
4001 | || warn "close failed: $!"; | |
4002 | ||
4003 | An older style is to use a bareword as the filehandle, as | |
4004 | ||
4005 | open(FH, "<", "input.txt") | |
4006 | or die "cannot open < input.txt: $!"; | |
4007 | ||
4008 | Then you can use C<FH> as the filehandle, in C<< close FH >> and C<< | |
4009 | <FH> >> and so on. Note that it's a global variable, so this form is | |
4010 | not recommended in new code. | |
4011 | ||
4012 | As a shortcut a one-argument call takes the filename from the global | |
4013 | scalar variable of the same name as the filehandle: | |
4014 | ||
4015 | $ARTICLE = 100; | |
4016 | open(ARTICLE) or die "Can't find article $ARTICLE: $!\n"; | |
4017 | ||
4018 | Here C<$ARTICLE> must be a global (package) scalar variable - not one | |
4019 | declared with C<my> or C<state>. | |
4020 | ||
8f1da26d | 4021 | As a special case the three-argument form with a read/write mode and the third |
ed53a2bb | 4022 | argument being C<undef>: |
b76cc8ba | 4023 | |
460b70c2 | 4024 | open(my $tmp, "+>", undef) or die ... |
b76cc8ba | 4025 | |
8f1da26d | 4026 | opens a filehandle to an anonymous temporary file. Also using C<< +< >> |
f253e835 JH |
4027 | works for symmetry, but you really should consider writing something |
4028 | to the temporary file first. You will need to seek() to do the | |
4029 | reading. | |
b76cc8ba | 4030 | |
e9fa405d | 4031 | Perl is built using PerlIO by default; Unless you've |
8f1da26d TC |
4032 | changed this (such as building Perl with C<Configure -Uuseperlio>), you can |
4033 | open filehandles directly to Perl scalars via: | |
ba964c95 | 4034 | |
8f1da26d | 4035 | open($fh, ">", \$variable) || .. |
b996200f | 4036 | |
3b10bc60 | 4037 | To (re)open C<STDOUT> or C<STDERR> as an in-memory file, close it first: |
b996200f SB |
4038 | |
4039 | close STDOUT; | |
8f1da26d TC |
4040 | open(STDOUT, ">", \$variable) |
4041 | or die "Can't open STDOUT: $!"; | |
ba964c95 | 4042 | |
3b10bc60 | 4043 | General examples: |
a0d0e21e | 4044 | |
8f1da26d | 4045 | open(LOG, ">>/usr/spool/news/twitlog"); # (log is reserved) |
fb73857a | 4046 | # if the open fails, output is discarded |
a0d0e21e | 4047 | |
8f1da26d | 4048 | open(my $dbase, "+<", "dbase.mine") # open for update |
a9a5a0dc | 4049 | or die "Can't open 'dbase.mine' for update: $!"; |
cb1a09d0 | 4050 | |
8f1da26d | 4051 | open(my $dbase, "+<dbase.mine") # ditto |
a9a5a0dc | 4052 | or die "Can't open 'dbase.mine' for update: $!"; |
6170680b | 4053 | |
8f1da26d | 4054 | open(ARTICLE, "-|", "caesar <$article") # decrypt article |
a9a5a0dc | 4055 | or die "Can't start caesar: $!"; |
a0d0e21e | 4056 | |
5ed4f2ec | 4057 | open(ARTICLE, "caesar <$article |") # ditto |
a9a5a0dc | 4058 | or die "Can't start caesar: $!"; |
6170680b | 4059 | |
5ed4f2ec | 4060 | open(EXTRACT, "|sort >Tmp$$") # $$ is our process id |
a9a5a0dc | 4061 | or die "Can't start sort: $!"; |
a0d0e21e | 4062 | |
3b10bc60 | 4063 | # in-memory files |
8f1da26d | 4064 | open(MEMORY, ">", \$var) |
a9a5a0dc | 4065 | or die "Can't open memory file: $!"; |
f7051f2c | 4066 | print MEMORY "foo!\n"; # output will appear in $var |
ba964c95 | 4067 | |
a0d0e21e LW |
4068 | # process argument list of files along with any includes |
4069 | ||
4070 | foreach $file (@ARGV) { | |
8f1da26d | 4071 | process($file, "fh00"); |
a0d0e21e LW |
4072 | } |
4073 | ||
4074 | sub process { | |
a9a5a0dc VP |
4075 | my($filename, $input) = @_; |
4076 | $input++; # this is a string increment | |
8f1da26d | 4077 | unless (open($input, "<", $filename)) { |
a9a5a0dc VP |
4078 | print STDERR "Can't open $filename: $!\n"; |
4079 | return; | |
4080 | } | |
5ed4f2ec | 4081 | |
a9a5a0dc VP |
4082 | local $_; |
4083 | while (<$input>) { # note use of indirection | |
4084 | if (/^#include "(.*)"/) { | |
4085 | process($1, $input); | |
4086 | next; | |
4087 | } | |
4088 | #... # whatever | |
5ed4f2ec | 4089 | } |
a0d0e21e LW |
4090 | } |
4091 | ||
ae4c5402 | 4092 | See L<perliol> for detailed info on PerlIO. |
2ce64696 | 4093 | |
a0d0e21e | 4094 | You may also, in the Bourne shell tradition, specify an EXPR beginning |
8f1da26d | 4095 | with C<< >& >>, in which case the rest of the string is interpreted |
00cafafa | 4096 | as the name of a filehandle (or file descriptor, if numeric) to be |
f4084e39 | 4097 | duped (as C<dup(2)>) and opened. You may use C<&> after C<< > >>, |
00cafafa JH |
4098 | C<<< >> >>>, C<< < >>, C<< +> >>, C<<< +>> >>>, and C<< +< >>. |
4099 | The mode you specify should match the mode of the original filehandle. | |
4100 | (Duping a filehandle does not take into account any existing contents | |
391b733c FC |
4101 | of IO buffers.) If you use the three-argument |
4102 | form, then you can pass either a | |
8f1da26d | 4103 | number, the name of a filehandle, or the normal "reference to a glob". |
6170680b | 4104 | |
eae1b76b SB |
4105 | Here is a script that saves, redirects, and restores C<STDOUT> and |
4106 | C<STDERR> using various methods: | |
a0d0e21e LW |
4107 | |
4108 | #!/usr/bin/perl | |
8f1da26d TC |
4109 | open(my $oldout, ">&STDOUT") or die "Can't dup STDOUT: $!"; |
4110 | open(OLDERR, ">&", \*STDERR) or die "Can't dup STDERR: $!"; | |
818c4caa | 4111 | |
8f1da26d TC |
4112 | open(STDOUT, '>', "foo.out") or die "Can't redirect STDOUT: $!"; |
4113 | open(STDERR, ">&STDOUT") or die "Can't dup STDOUT: $!"; | |
a0d0e21e | 4114 | |
5ed4f2ec | 4115 | select STDERR; $| = 1; # make unbuffered |
4116 | select STDOUT; $| = 1; # make unbuffered | |
a0d0e21e | 4117 | |
5ed4f2ec | 4118 | print STDOUT "stdout 1\n"; # this works for |
4119 | print STDERR "stderr 1\n"; # subprocesses too | |
a0d0e21e | 4120 | |
8f1da26d TC |
4121 | open(STDOUT, ">&", $oldout) or die "Can't dup \$oldout: $!"; |
4122 | open(STDERR, ">&OLDERR") or die "Can't dup OLDERR: $!"; | |
a0d0e21e LW |
4123 | |
4124 | print STDOUT "stdout 2\n"; | |
4125 | print STDERR "stderr 2\n"; | |
4126 | ||
ef8b303f JH |
4127 | If you specify C<< '<&=X' >>, where C<X> is a file descriptor number |
4128 | or a filehandle, then Perl will do an equivalent of C's C<fdopen> of | |
f4084e39 | 4129 | that file descriptor (and not call C<dup(2)>); this is more |
ef8b303f | 4130 | parsimonious of file descriptors. For example: |
a0d0e21e | 4131 | |
00cafafa | 4132 | # open for input, reusing the fileno of $fd |
a0d0e21e | 4133 | open(FILEHANDLE, "<&=$fd") |
df632fdf | 4134 | |
b76cc8ba | 4135 | or |
df632fdf | 4136 | |
b76cc8ba | 4137 | open(FILEHANDLE, "<&=", $fd) |
a0d0e21e | 4138 | |
00cafafa JH |
4139 | or |
4140 | ||
4141 | # open for append, using the fileno of OLDFH | |
4142 | open(FH, ">>&=", OLDFH) | |
4143 | ||
4144 | or | |
4145 | ||
4146 | open(FH, ">>&=OLDFH") | |
4147 | ||
ef8b303f JH |
4148 | Being parsimonious on filehandles is also useful (besides being |
4149 | parsimonious) for example when something is dependent on file | |
4150 | descriptors, like for example locking using flock(). If you do just | |
8f1da26d TC |
4151 | C<< open(A, ">>&B") >>, the filehandle A will not have the same file |
4152 | descriptor as B, and therefore flock(A) will not flock(B) nor vice | |
4153 | versa. But with C<< open(A, ">>&=B") >>, the filehandles will share | |
4154 | the same underlying system file descriptor. | |
4155 | ||
4156 | Note that under Perls older than 5.8.0, Perl uses the standard C library's' | |
4157 | fdopen() to implement the C<=> functionality. On many Unix systems, | |
4158 | fdopen() fails when file descriptors exceed a certain value, typically 255. | |
4159 | For Perls 5.8.0 and later, PerlIO is (most often) the default. | |
4160 | ||
4161 | You can see whether your Perl was built with PerlIO by running C<perl -V> | |
4162 | and looking for the C<useperlio=> line. If C<useperlio> is C<define>, you | |
4163 | have PerlIO; otherwise you don't. | |
4164 | ||
4165 | If you open a pipe on the command C<-> (that is, specify either C<|-> or C<-|> | |
4166 | with the one- or two-argument forms of C<open>), | |
4167 | an implicit C<fork> is done, so C<open> returns twice: in the parent | |
4168 | process it returns the pid | |
4169 | of the child process, and in the child process it returns (a defined) C<0>. | |
4170 | Use C<defined($pid)> or C<//> to determine whether the open was successful. | |
4171 | ||
4172 | For example, use either | |
4173 | ||
5f64ea7a | 4174 | $child_pid = open(FROM_KID, "-|") // die "can't fork: $!"; |
8f1da26d TC |
4175 | |
4176 | or | |
d18fc9db | 4177 | |
8f1da26d TC |
4178 | $child_pid = open(TO_KID, "|-") // die "can't fork: $!"; |
4179 | ||
4180 | followed by | |
4181 | ||
4182 | if ($child_pid) { | |
4183 | # am the parent: | |
4184 | # either write TO_KID or else read FROM_KID | |
4185 | ... | |
237f7097 | 4186 | waitpid $child_pid, 0; |
8f1da26d TC |
4187 | } else { |
4188 | # am the child; use STDIN/STDOUT normally | |
4189 | ... | |
4190 | exit; | |
4191 | } | |
4192 | ||
3b10bc60 | 4193 | The filehandle behaves normally for the parent, but I/O to that |
a0d0e21e | 4194 | filehandle is piped from/to the STDOUT/STDIN of the child process. |
3b10bc60 | 4195 | In the child process, the filehandle isn't opened--I/O happens from/to |
4196 | the new STDOUT/STDIN. Typically this is used like the normal | |
a0d0e21e | 4197 | piped open when you want to exercise more control over just how the |
3b10bc60 | 4198 | pipe command gets executed, such as when running setuid and |
4199 | you don't want to have to scan shell commands for metacharacters. | |
4200 | ||
5b867647 | 4201 | The following blocks are more or less equivalent: |
a0d0e21e LW |
4202 | |
4203 | open(FOO, "|tr '[a-z]' '[A-Z]'"); | |
8f1da26d TC |
4204 | open(FOO, "|-", "tr '[a-z]' '[A-Z]'"); |
4205 | open(FOO, "|-") || exec 'tr', '[a-z]', '[A-Z]'; | |
4206 | open(FOO, "|-", "tr", '[a-z]', '[A-Z]'); | |
a0d0e21e LW |
4207 | |
4208 | open(FOO, "cat -n '$file'|"); | |
8f1da26d TC |
4209 | open(FOO, "-|", "cat -n '$file'"); |
4210 | open(FOO, "-|") || exec "cat", "-n", $file; | |
4211 | open(FOO, "-|", "cat", "-n", $file); | |
b76cc8ba | 4212 | |
8f1da26d | 4213 | The last two examples in each block show the pipe as "list form", which is |
64da03b2 | 4214 | not yet supported on all platforms. A good rule of thumb is that if |
8f1da26d TC |
4215 | your platform has a real C<fork()> (in other words, if your platform is |
4216 | Unix, including Linux and MacOS X), you can use the list form. You would | |
4217 | want to use the list form of the pipe so you can pass literal arguments | |
4218 | to the command without risk of the shell interpreting any shell metacharacters | |
4219 | in them. However, this also bars you from opening pipes to commands | |
4220 | that intentionally contain shell metacharacters, such as: | |
4221 | ||
4222 | open(FOO, "|cat -n | expand -4 | lpr") | |
4223 | // die "Can't open pipeline to lpr: $!"; | |
a0d0e21e | 4224 | |
4633a7c4 LW |
4225 | See L<perlipc/"Safe Pipe Opens"> for more examples of this. |
4226 | ||
e9fa405d | 4227 | Perl will attempt to flush all files opened for |
0f897271 GS |
4228 | output before any operation that may do a fork, but this may not be |
4229 | supported on some platforms (see L<perlport>). To be safe, you may need | |
4230 | to set C<$|> ($AUTOFLUSH in English) or call the C<autoflush()> method | |
4231 | of C<IO::Handle> on any open handles. | |
4232 | ||
ed53a2bb JH |
4233 | On systems that support a close-on-exec flag on files, the flag will |
4234 | be set for the newly opened file descriptor as determined by the value | |
8f1da26d | 4235 | of C<$^F>. See L<perlvar/$^F>. |
a0d0e21e | 4236 | |
0dccf244 | 4237 | Closing any piped filehandle causes the parent process to wait for the |
8f1da26d | 4238 | child to finish, then returns the status value in C<$?> and |
e5218da5 | 4239 | C<${^CHILD_ERROR_NATIVE}>. |
0dccf244 | 4240 | |
8f1da26d TC |
4241 | The filename passed to the one- and two-argument forms of open() will |
4242 | have leading and trailing whitespace deleted and normal | |
ed53a2bb | 4243 | redirection characters honored. This property, known as "magic open", |
5a964f20 | 4244 | can often be used to good effect. A user could specify a filename of |
7660c0ab | 4245 | F<"rsh cat file |">, or you could change certain filenames as needed: |
5a964f20 TC |
4246 | |
4247 | $filename =~ s/(.*\.gz)\s*$/gzip -dc < $1|/; | |
4248 | open(FH, $filename) or die "Can't open $filename: $!"; | |
4249 | ||
8f1da26d | 4250 | Use the three-argument form to open a file with arbitrary weird characters in it, |
6170680b | 4251 | |
8f1da26d TC |
4252 | open(FOO, "<", $file) |
4253 | || die "can't open < $file: $!"; | |
6170680b IZ |
4254 | |
4255 | otherwise it's necessary to protect any leading and trailing whitespace: | |
5a964f20 TC |
4256 | |
4257 | $file =~ s#^(\s)#./$1#; | |
8f1da26d TC |
4258 | open(FOO, "< $file\0") |
4259 | || die "open failed: $!"; | |
5a964f20 | 4260 | |
a31a806a | 4261 | (this may not work on some bizarre filesystems). One should |
8f1da26d | 4262 | conscientiously choose between the I<magic> and I<three-argument> form |
6170680b IZ |
4263 | of open(): |
4264 | ||
8f1da26d | 4265 | open(IN, $ARGV[0]) || die "can't open $ARGV[0]: $!"; |
6170680b IZ |
4266 | |
4267 | will allow the user to specify an argument of the form C<"rsh cat file |">, | |
80d38338 | 4268 | but will not work on a filename that happens to have a trailing space, while |
6170680b | 4269 | |
8f1da26d TC |
4270 | open(IN, "<", $ARGV[0]) |
4271 | || die "can't open < $ARGV[0]: $!"; | |
6170680b IZ |
4272 | |
4273 | will have exactly the opposite restrictions. | |
4274 | ||
01aa884e | 4275 | If you want a "real" C C<open> (see L<open(2)> on your system), then you |
8f1da26d TC |
4276 | should use the C<sysopen> function, which involves no such magic (but may |
4277 | use subtly different filemodes than Perl open(), which is mapped to C | |
4278 | fopen()). This is another way to protect your filenames from | |
4279 | interpretation. For example: | |
5a964f20 TC |
4280 | |
4281 | use IO::Handle; | |
4282 | sysopen(HANDLE, $path, O_RDWR|O_CREAT|O_EXCL) | |
a9a5a0dc | 4283 | or die "sysopen $path: $!"; |
5a964f20 | 4284 | $oldfh = select(HANDLE); $| = 1; select($oldfh); |
38762f02 | 4285 | print HANDLE "stuff $$\n"; |
5a964f20 TC |
4286 | seek(HANDLE, 0, 0); |
4287 | print "File contains: ", <HANDLE>; | |
4288 | ||
b687b08b | 4289 | See L</seek> for some details about mixing reading and writing. |
a0d0e21e | 4290 | |
ea9eb35a BJ |
4291 | Portability issues: L<perlport/open>. |
4292 | ||
a0d0e21e | 4293 | =item opendir DIRHANDLE,EXPR |
d74e8afc | 4294 | X<opendir> |
a0d0e21e | 4295 | |
c17cdb72 NC |
4296 | =for Pod::Functions open a directory |
4297 | ||
19799a22 GS |
4298 | Opens a directory named EXPR for processing by C<readdir>, C<telldir>, |
4299 | C<seekdir>, C<rewinddir>, and C<closedir>. Returns true if successful. | |
a28cd5c9 NT |
4300 | DIRHANDLE may be an expression whose value can be used as an indirect |
4301 | dirhandle, usually the real dirhandle name. If DIRHANDLE is an undefined | |
4302 | scalar variable (or array or hash element), the variable is assigned a | |
8f1da26d | 4303 | reference to a new anonymous dirhandle; that is, it's autovivified. |
a0d0e21e LW |
4304 | DIRHANDLEs have their own namespace separate from FILEHANDLEs. |
4305 | ||
bea6df1c | 4306 | See the example at C<readdir>. |
b0169937 | 4307 | |
a0d0e21e | 4308 | =item ord EXPR |
d74e8afc | 4309 | X<ord> X<encoding> |
a0d0e21e | 4310 | |
54310121 | 4311 | =item ord |
bbce6d69 | 4312 | |
c17cdb72 NC |
4313 | =for Pod::Functions find a character's numeric representation |
4314 | ||
c9b06361 | 4315 | Returns the numeric value of the first character of EXPR. |
8f1da26d TC |
4316 | If EXPR is an empty string, returns 0. If EXPR is omitted, uses C<$_>. |
4317 | (Note I<character>, not byte.) | |
121910a4 JH |
4318 | |
4319 | For the reverse, see L</chr>. | |
2575c402 | 4320 | See L<perlunicode> for more about Unicode. |
a0d0e21e | 4321 | |
672208d2 | 4322 | =item our VARLIST |
d74e8afc | 4323 | X<our> X<global> |
77ca0c92 | 4324 | |
672208d2 | 4325 | =item our TYPE VARLIST |
307ea6df | 4326 | |
672208d2 | 4327 | =item our VARLIST : ATTRS |
9969eac4 | 4328 | |
672208d2 | 4329 | =item our TYPE VARLIST : ATTRS |
307ea6df | 4330 | |
d9b04284 | 4331 | =for Pod::Functions +5.6.0 declare and assign a package variable (lexical scoping) |
c17cdb72 | 4332 | |
66b30015 DG |
4333 | C<our> makes a lexical alias to a package variable of the same name in the current |
4334 | package for use within the current lexical scope. | |
4335 | ||
4336 | C<our> has the same scoping rules as C<my> or C<state>, but C<our> only | |
4337 | declares an alias, whereas C<my> or C<state> both declare a variable name and | |
4338 | allocate storage for that name within the current scope. | |
4339 | ||
4340 | This means that when C<use strict 'vars'> is in effect, C<our> lets you use | |
4341 | a package variable without qualifying it with the package name, but only within | |
4342 | the lexical scope of the C<our> declaration. In this way, C<our> differs from | |
848bab4f DG |
4343 | C<use vars>, which allows use of an unqualified name I<only> within the |
4344 | affected package, but across scopes. | |
65c680eb | 4345 | |
672208d2 | 4346 | If more than one variable is listed, the list must be placed |
65c680eb | 4347 | in parentheses. |
85d8b7d5 MS |
4348 | |
4349 | our $foo; | |
4350 | our($bar, $baz); | |
77ca0c92 | 4351 | |
66b30015 | 4352 | An C<our> declaration declares an alias for a package variable that will be visible |
f472eb5c GS |
4353 | across its entire lexical scope, even across package boundaries. The |
4354 | package in which the variable is entered is determined at the point | |
4355 | of the declaration, not at the point of use. This means the following | |
4356 | behavior holds: | |
4357 | ||
4358 | package Foo; | |
5ed4f2ec | 4359 | our $bar; # declares $Foo::bar for rest of lexical scope |
f472eb5c GS |
4360 | $bar = 20; |
4361 | ||
4362 | package Bar; | |
5ed4f2ec | 4363 | print $bar; # prints 20, as it refers to $Foo::bar |
f472eb5c | 4364 | |
65c680eb MS |
4365 | Multiple C<our> declarations with the same name in the same lexical |
4366 | scope are allowed if they are in different packages. If they happen | |
4367 | to be in the same package, Perl will emit warnings if you have asked | |
4368 | for them, just like multiple C<my> declarations. Unlike a second | |
4369 | C<my> declaration, which will bind the name to a fresh variable, a | |
4370 | second C<our> declaration in the same package, in the same scope, is | |
4371 | merely redundant. | |
f472eb5c GS |
4372 | |
4373 | use warnings; | |
4374 | package Foo; | |
5ed4f2ec | 4375 | our $bar; # declares $Foo::bar for rest of lexical scope |
f472eb5c GS |
4376 | $bar = 20; |
4377 | ||
4378 | package Bar; | |
5ed4f2ec | 4379 | our $bar = 30; # declares $Bar::bar for rest of lexical scope |
4380 | print $bar; # prints 30 | |
f472eb5c | 4381 | |
5ed4f2ec | 4382 | our $bar; # emits warning but has no other effect |
4383 | print $bar; # still prints 30 | |
f472eb5c | 4384 | |
9969eac4 | 4385 | An C<our> declaration may also have a list of attributes associated |
307ea6df JH |
4386 | with it. |
4387 | ||
1d2de774 | 4388 | The exact semantics and interface of TYPE and ATTRS are still |
bade7fbc TC |
4389 | evolving. TYPE is currently bound to the use of the C<fields> pragma, |
4390 | and attributes are handled using the C<attributes> pragma, or, starting | |
4391 | from Perl 5.8.0, also via the C<Attribute::Handlers> module. See | |
307ea6df JH |
4392 | L<perlsub/"Private Variables via my()"> for details, and L<fields>, |
4393 | L<attributes>, and L<Attribute::Handlers>. | |
4394 | ||
672208d2 JV |
4395 | Note that with a parenthesised list, C<undef> can be used as a dummy |
4396 | placeholder, for example to skip assignment of initial values: | |
4397 | ||
4398 | our ( undef, $min, $hour ) = localtime; | |
4399 | ||
a0d0e21e | 4400 | =item pack TEMPLATE,LIST |
d74e8afc | 4401 | X<pack> |
a0d0e21e | 4402 | |
c17cdb72 NC |
4403 | =for Pod::Functions convert a list into a binary representation |
4404 | ||
2b6c5635 GS |
4405 | Takes a LIST of values and converts it into a string using the rules |
4406 | given by the TEMPLATE. The resulting string is the concatenation of | |
4407 | the converted values. Typically, each converted value looks | |
4408 | like its machine-level representation. For example, on 32-bit machines | |
3980dc9c KW |
4409 | an integer may be represented by a sequence of 4 bytes, which will in |
4410 | Perl be presented as a string that's 4 characters long. | |
4411 | ||
4412 | See L<perlpacktut> for an introduction to this function. | |
e1b711da | 4413 | |
18529408 IZ |
4414 | The TEMPLATE is a sequence of characters that give the order and type |
4415 | of values, as follows: | |
a0d0e21e | 4416 | |
5ed4f2ec | 4417 | a A string with arbitrary binary data, will be null padded. |
4418 | A A text (ASCII) string, will be space padded. | |
3b10bc60 | 4419 | Z A null-terminated (ASCIZ) string, will be null padded. |
5a929a98 | 4420 | |
4d0444a3 FC |
4421 | b A bit string (ascending bit order inside each byte, |
4422 | like vec()). | |
5ed4f2ec | 4423 | B A bit string (descending bit order inside each byte). |
4424 | h A hex string (low nybble first). | |
4425 | H A hex string (high nybble first). | |
a0d0e21e | 4426 | |
5ed4f2ec | 4427 | c A signed char (8-bit) value. |
4428 | C An unsigned char (octet) value. | |
3b10bc60 | 4429 | W An unsigned char value (can be greater than 255). |
96e4d5b1 | 4430 | |
5ed4f2ec | 4431 | s A signed short (16-bit) value. |
4432 | S An unsigned short value. | |
96e4d5b1 | 4433 | |
5ed4f2ec | 4434 | l A signed long (32-bit) value. |
4435 | L An unsigned long value. | |
a0d0e21e | 4436 | |
5ed4f2ec | 4437 | q A signed quad (64-bit) value. |
4438 | Q An unsigned quad value. | |
4d0444a3 FC |
4439 | (Quads are available only if your system supports 64-bit |
4440 | integer values _and_ if Perl has been compiled to support | |
4441 | those. Raises an exception otherwise.) | |
dae0da7a | 4442 | |
5ed4f2ec | 4443 | i A signed integer value. |
4444 | I A unsigned integer value. | |
4d0444a3 FC |
4445 | (This 'integer' is _at_least_ 32 bits wide. Its exact |
4446 | size depends on what a local C compiler calls 'int'.) | |
2b191d53 | 4447 | |
5ed4f2ec | 4448 | n An unsigned short (16-bit) in "network" (big-endian) order. |
4449 | N An unsigned long (32-bit) in "network" (big-endian) order. | |
4450 | v An unsigned short (16-bit) in "VAX" (little-endian) order. | |
4451 | V An unsigned long (32-bit) in "VAX" (little-endian) order. | |
1109a392 | 4452 | |
4d0444a3 FC |
4453 | j A Perl internal signed integer value (IV). |
4454 | J A Perl internal unsigned integer value (UV). | |
92d41999 | 4455 | |
3b10bc60 | 4456 | f A single-precision float in native format. |
4457 | d A double-precision float in native format. | |
a0d0e21e | 4458 | |
3b10bc60 | 4459 | F A Perl internal floating-point value (NV) in native format |
4460 | D A float of long-double precision in native format. | |
4d0444a3 FC |
4461 | (Long doubles are available only if your system supports |
4462 | long double values _and_ if Perl has been compiled to | |
4463 | support those. Raises an exception otherwise.) | |
92d41999 | 4464 | |
5ed4f2ec | 4465 | p A pointer to a null-terminated string. |
4466 | P A pointer to a structure (fixed-length string). | |
a0d0e21e | 4467 | |
5ed4f2ec | 4468 | u A uuencoded string. |
4d0444a3 FC |
4469 | U A Unicode character number. Encodes to a character in char- |
4470 | acter mode and UTF-8 (or UTF-EBCDIC in EBCDIC platforms) in | |
4471 | byte mode. | |
a0d0e21e | 4472 | |
4d0444a3 FC |
4473 | w A BER compressed integer (not an ASN.1 BER, see perlpacktut |
4474 | for details). Its bytes represent an unsigned integer in | |
4475 | base 128, most significant digit first, with as few digits | |
4476 | as possible. Bit eight (the high bit) is set on each byte | |
4477 | except the last. | |
def98dd4 | 4478 | |
3b10bc60 | 4479 | x A null byte (a.k.a ASCII NUL, "\000", chr(0)) |
5ed4f2ec | 4480 | X Back up a byte. |
3b10bc60 | 4481 | @ Null-fill or truncate to absolute position, counted from the |
4482 | start of the innermost ()-group. | |
4d0444a3 FC |
4483 | . Null-fill or truncate to absolute position specified by |
4484 | the value. | |
5ed4f2ec | 4485 | ( Start of a ()-group. |
a0d0e21e | 4486 | |
3b10bc60 | 4487 | One or more modifiers below may optionally follow certain letters in the |
4488 | TEMPLATE (the second column lists letters for which the modifier is valid): | |
1109a392 MHM |
4489 | |
4490 | ! sSlLiI Forces native (short, long, int) sizes instead | |
4491 | of fixed (16-/32-bit) sizes. | |
4492 | ||
c584250a | 4493 | ! xX Make x and X act as alignment commands. |
1109a392 | 4494 | |
c584250a | 4495 | ! nNvV Treat integers as signed instead of unsigned. |
1109a392 | 4496 | |
c584250a | 4497 | ! @. Specify position as byte offset in the internal |
391b733c FC |
4498 | representation of the packed string. Efficient |
4499 | but dangerous. | |
28be1210 | 4500 | |
1109a392 MHM |
4501 | > sSiIlLqQ Force big-endian byte-order on the type. |
4502 | jJfFdDpP (The "big end" touches the construct.) | |
4503 | ||
4504 | < sSiIlLqQ Force little-endian byte-order on the type. | |
4505 | jJfFdDpP (The "little end" touches the construct.) | |
4506 | ||
3b10bc60 | 4507 | The C<< > >> and C<< < >> modifiers can also be used on C<()> groups |
4508 | to force a particular byte-order on all components in that group, | |
4509 | including all its subgroups. | |
66c611c5 | 4510 | |
24f4b7da NC |
4511 | =begin comment |
4512 | ||
4513 | Larry recalls that the hex and bit string formats (H, h, B, b) were added to | |
7161e5c2 | 4514 | pack for processing data from NASA's Magellan probe. Magellan was in an |
24f4b7da NC |
4515 | elliptical orbit, using the antenna for the radar mapping when close to |
4516 | Venus and for communicating data back to Earth for the rest of the orbit. | |
4517 | There were two transmission units, but one of these failed, and then the | |
4518 | other developed a fault whereby it would randomly flip the sense of all the | |
4519 | bits. It was easy to automatically detect complete records with the correct | |
4520 | sense, and complete records with all the bits flipped. However, this didn't | |
4521 | recover the records where the sense flipped midway. A colleague of Larry's | |
4522 | was able to pretty much eyeball where the records flipped, so they wrote an | |
4523 | editor named kybble (a pun on the dog food Kibbles 'n Bits) to enable him to | |
4524 | manually correct the records and recover the data. For this purpose pack | |
4525 | gained the hex and bit string format specifiers. | |
4526 | ||
4527 | git shows that they were added to perl 3.0 in patch #44 (Jan 1991, commit | |
4528 | 27e2fb84680b9cc1), but the patch description makes no mention of their | |
4529 | addition, let alone the story behind them. | |
4530 | ||
4531 | =end comment | |
4532 | ||
5a929a98 VU |
4533 | The following rules apply: |
4534 | ||
3b10bc60 | 4535 | =over |
5a929a98 VU |
4536 | |
4537 | =item * | |
4538 | ||
3b10bc60 | 4539 | Each letter may optionally be followed by a number indicating the repeat |
4540 | count. A numeric repeat count may optionally be enclosed in brackets, as | |
4541 | in C<pack("C[80]", @arr)>. The repeat count gobbles that many values from | |
4542 | the LIST when used with all format types other than C<a>, C<A>, C<Z>, C<b>, | |
4543 | C<B>, C<h>, C<H>, C<@>, C<.>, C<x>, C<X>, and C<P>, where it means | |
7698aede | 4544 | something else, described below. Supplying a C<*> for the repeat count |
3b10bc60 | 4545 | instead of a number means to use however many items are left, except for: |
4546 | ||
4547 | =over | |
4548 | ||
4549 | =item * | |
4550 | ||
4551 | C<@>, C<x>, and C<X>, where it is equivalent to C<0>. | |
4552 | ||
4553 | =item * | |
4554 | ||
4555 | <.>, where it means relative to the start of the string. | |
4556 | ||
4557 | =item * | |
4558 | ||
4559 | C<u>, where it is equivalent to 1 (or 45, which here is equivalent). | |
4560 | ||
4561 | =back | |
4562 | ||
4563 | One can replace a numeric repeat count with a template letter enclosed in | |
4564 | brackets to use the packed byte length of the bracketed template for the | |
4565 | repeat count. | |
4566 | ||
4567 | For example, the template C<x[L]> skips as many bytes as in a packed long, | |
4568 | and the template C<"$t X[$t] $t"> unpacks twice whatever $t (when | |
4569 | variable-expanded) unpacks. If the template in brackets contains alignment | |
4570 | commands (such as C<x![d]>), its packed length is calculated as if the | |
4571 | start of the template had the maximal possible alignment. | |
4572 | ||
4573 | When used with C<Z>, a C<*> as the repeat count is guaranteed to add a | |
4574 | trailing null byte, so the resulting string is always one byte longer than | |
4575 | the byte length of the item itself. | |
2b6c5635 | 4576 | |
28be1210 | 4577 | When used with C<@>, the repeat count represents an offset from the start |
3b10bc60 | 4578 | of the innermost C<()> group. |
4579 | ||
4580 | When used with C<.>, the repeat count determines the starting position to | |
4581 | calculate the value offset as follows: | |
4582 | ||
4583 | =over | |
4584 | ||
4585 | =item * | |
4586 | ||
4587 | If the repeat count is C<0>, it's relative to the current position. | |
28be1210 | 4588 | |
3b10bc60 | 4589 | =item * |
4590 | ||
4591 | If the repeat count is C<*>, the offset is relative to the start of the | |
4592 | packed string. | |
4593 | ||
4594 | =item * | |
4595 | ||
4596 | And if it's an integer I<n>, the offset is relative to the start of the | |
8f1da26d | 4597 | I<n>th innermost C<( )> group, or to the start of the string if I<n> is |
3b10bc60 | 4598 | bigger then the group level. |
4599 | ||
4600 | =back | |
28be1210 | 4601 | |
951ba7fe | 4602 | The repeat count for C<u> is interpreted as the maximal number of bytes |
391b733c | 4603 | to encode per line of output, with 0, 1 and 2 replaced by 45. The repeat |
f337b084 | 4604 | count should not be more than 65. |
5a929a98 VU |
4605 | |
4606 | =item * | |
4607 | ||
951ba7fe | 4608 | The C<a>, C<A>, and C<Z> types gobble just one value, but pack it as a |
3b10bc60 | 4609 | string of length count, padding with nulls or spaces as needed. When |
18bdf90a | 4610 | unpacking, C<A> strips trailing whitespace and nulls, C<Z> strips everything |
8f1da26d | 4611 | after the first null, and C<a> returns data with no stripping at all. |
2b6c5635 | 4612 | |
3b10bc60 | 4613 | If the value to pack is too long, the result is truncated. If it's too |
4614 | long and an explicit count is provided, C<Z> packs only C<$count-1> bytes, | |
4615 | followed by a null byte. Thus C<Z> always packs a trailing null, except | |
8f1da26d | 4616 | when the count is 0. |
5a929a98 VU |
4617 | |
4618 | =item * | |
4619 | ||
3b10bc60 | 4620 | Likewise, the C<b> and C<B> formats pack a string that's that many bits long. |
8f1da26d TC |
4621 | Each such format generates 1 bit of the result. These are typically followed |
4622 | by a repeat count like C<B8> or C<B64>. | |
3b10bc60 | 4623 | |
c73032f5 | 4624 | Each result bit is based on the least-significant bit of the corresponding |
f337b084 | 4625 | input character, i.e., on C<ord($char)%2>. In particular, characters C<"0"> |
3b10bc60 | 4626 | and C<"1"> generate bits 0 and 1, as do characters C<"\000"> and C<"\001">. |
c73032f5 | 4627 | |
3b10bc60 | 4628 | Starting from the beginning of the input string, each 8-tuple |
4629 | of characters is converted to 1 character of output. With format C<b>, | |
f337b084 | 4630 | the first character of the 8-tuple determines the least-significant bit of a |
3b10bc60 | 4631 | character; with format C<B>, it determines the most-significant bit of |
f337b084 | 4632 | a character. |
c73032f5 | 4633 | |
3b10bc60 | 4634 | If the length of the input string is not evenly divisible by 8, the |
f337b084 | 4635 | remainder is packed as if the input string were padded by null characters |
3b10bc60 | 4636 | at the end. Similarly during unpacking, "extra" bits are ignored. |
c73032f5 | 4637 | |
3b10bc60 | 4638 | If the input string is longer than needed, remaining characters are ignored. |
4639 | ||
4640 | A C<*> for the repeat count uses all characters of the input field. | |
8f1da26d | 4641 | On unpacking, bits are converted to a string of C<0>s and C<1>s. |
5a929a98 VU |
4642 | |
4643 | =item * | |
4644 | ||
3b10bc60 | 4645 | The C<h> and C<H> formats pack a string that many nybbles (4-bit groups, |
4646 | representable as hexadecimal digits, C<"0".."9"> C<"a".."f">) long. | |
5a929a98 | 4647 | |
8f1da26d | 4648 | For each such format, pack() generates 4 bits of result. |
3b10bc60 | 4649 | With non-alphabetical characters, the result is based on the 4 least-significant |
f337b084 TH |
4650 | bits of the input character, i.e., on C<ord($char)%16>. In particular, |
4651 | characters C<"0"> and C<"1"> generate nybbles 0 and 1, as do bytes | |
ce7b6f06 | 4652 | C<"\000"> and C<"\001">. For characters C<"a".."f"> and C<"A".."F">, the result |
c73032f5 | 4653 | is compatible with the usual hexadecimal digits, so that C<"a"> and |
8f1da26d TC |
4654 | C<"A"> both generate the nybble C<0xA==10>. Use only these specific hex |
4655 | characters with this format. | |
c73032f5 | 4656 | |
3b10bc60 | 4657 | Starting from the beginning of the template to pack(), each pair |
4658 | of characters is converted to 1 character of output. With format C<h>, the | |
f337b084 | 4659 | first character of the pair determines the least-significant nybble of the |
3b10bc60 | 4660 | output character; with format C<H>, it determines the most-significant |
c73032f5 IZ |
4661 | nybble. |
4662 | ||
3b10bc60 | 4663 | If the length of the input string is not even, it behaves as if padded by |
4664 | a null character at the end. Similarly, "extra" nybbles are ignored during | |
4665 | unpacking. | |
4666 | ||
4667 | If the input string is longer than needed, extra characters are ignored. | |
c73032f5 | 4668 | |
3b10bc60 | 4669 | A C<*> for the repeat count uses all characters of the input field. For |
4670 | unpack(), nybbles are converted to a string of hexadecimal digits. | |
c73032f5 | 4671 | |
5a929a98 VU |
4672 | =item * |
4673 | ||
3b10bc60 | 4674 | The C<p> format packs a pointer to a null-terminated string. You are |
4675 | responsible for ensuring that the string is not a temporary value, as that | |
4676 | could potentially get deallocated before you got around to using the packed | |
4677 | result. The C<P> format packs a pointer to a structure of the size indicated | |
4678 | by the length. A null pointer is created if the corresponding value for | |
4679 | C<p> or C<P> is C<undef>; similarly with unpack(), where a null pointer | |
4680 | unpacks into C<undef>. | |
5a929a98 | 4681 | |
3b10bc60 | 4682 | If your system has a strange pointer size--meaning a pointer is neither as |
4683 | big as an int nor as big as a long--it may not be possible to pack or | |
1109a392 | 4684 | unpack pointers in big- or little-endian byte order. Attempting to do |
3b10bc60 | 4685 | so raises an exception. |
1109a392 | 4686 | |
5a929a98 VU |
4687 | =item * |
4688 | ||
246f24af | 4689 | The C</> template character allows packing and unpacking of a sequence of |
3b10bc60 | 4690 | items where the packed structure contains a packed item count followed by |
4691 | the packed items themselves. This is useful when the structure you're | |
4692 | unpacking has encoded the sizes or repeat counts for some of its fields | |
4693 | within the structure itself as separate fields. | |
4694 | ||
4695 | For C<pack>, you write I<length-item>C</>I<sequence-item>, and the | |
391b733c | 4696 | I<length-item> describes how the length value is packed. Formats likely |
3b10bc60 | 4697 | to be of most use are integer-packing ones like C<n> for Java strings, |
4698 | C<w> for ASN.1 or SNMP, and C<N> for Sun XDR. | |
4699 | ||
4700 | For C<pack>, I<sequence-item> may have a repeat count, in which case | |
4701 | the minimum of that and the number of available items is used as the argument | |
391b733c | 4702 | for I<length-item>. If it has no repeat count or uses a '*', the number |
54f961c9 PD |
4703 | of available items is used. |
4704 | ||
3b10bc60 | 4705 | For C<unpack>, an internal stack of integer arguments unpacked so far is |
391b733c FC |
4706 | used. You write C</>I<sequence-item> and the repeat count is obtained by |
4707 | popping off the last element from the stack. The I<sequence-item> must not | |
54f961c9 | 4708 | have a repeat count. |
246f24af | 4709 | |
3b10bc60 | 4710 | If I<sequence-item> refers to a string type (C<"A">, C<"a">, or C<"Z">), |
4711 | the I<length-item> is the string length, not the number of strings. With | |
4712 | an explicit repeat count for pack, the packed string is adjusted to that | |
4713 | length. For example: | |
246f24af | 4714 | |
f7051f2c | 4715 | This code: gives this result: |
f703fc96 | 4716 | |
f7051f2c FC |
4717 | unpack("W/a", "\004Gurusamy") ("Guru") |
4718 | unpack("a3/A A*", "007 Bond J ") (" Bond", "J") | |
4719 | unpack("a3 x2 /A A*", "007: Bond, J.") ("Bond, J", ".") | |
3b10bc60 | 4720 | |
f7051f2c FC |
4721 | pack("n/a* w/a","hello,","world") "\000\006hello,\005world" |
4722 | pack("a/W2", ord("a") .. ord("z")) "2ab" | |
43192e07 IP |
4723 | |
4724 | The I<length-item> is not returned explicitly from C<unpack>. | |
4725 | ||
3b10bc60 | 4726 | Supplying a count to the I<length-item> format letter is only useful with |
4727 | C<A>, C<a>, or C<Z>. Packing with a I<length-item> of C<a> or C<Z> may | |
4728 | introduce C<"\000"> characters, which Perl does not regard as legal in | |
4729 | numeric strings. | |
43192e07 IP |
4730 | |
4731 | =item * | |
4732 | ||
951ba7fe | 4733 | The integer types C<s>, C<S>, C<l>, and C<L> may be |
3b10bc60 | 4734 | followed by a C<!> modifier to specify native shorts or |
4735 | longs. As shown in the example above, a bare C<l> means | |
4736 | exactly 32 bits, although the native C<long> as seen by the local C compiler | |
4737 | may be larger. This is mainly an issue on 64-bit platforms. You can | |
4738 | see whether using C<!> makes any difference this way: | |
4739 | ||
4740 | printf "format s is %d, s! is %d\n", | |
4741 | length pack("s"), length pack("s!"); | |
726ea183 | 4742 | |
3b10bc60 | 4743 | printf "format l is %d, l! is %d\n", |
4744 | length pack("l"), length pack("l!"); | |
ef54e1a4 | 4745 | |
3b10bc60 | 4746 | |
4747 | C<i!> and C<I!> are also allowed, but only for completeness' sake: | |
951ba7fe | 4748 | they are identical to C<i> and C<I>. |
ef54e1a4 | 4749 | |
19799a22 | 4750 | The actual sizes (in bytes) of native shorts, ints, longs, and long |
3b10bc60 | 4751 | longs on the platform where Perl was built are also available from |
4752 | the command line: | |
4753 | ||
4754 | $ perl -V:{short,int,long{,long}}size | |
4755 | shortsize='2'; | |
4756 | intsize='4'; | |
4757 | longsize='4'; | |
4758 | longlongsize='8'; | |
4759 | ||
4760 | or programmatically via the C<Config> module: | |
19799a22 GS |
4761 | |
4762 | use Config; | |
4763 | print $Config{shortsize}, "\n"; | |
4764 | print $Config{intsize}, "\n"; | |
4765 | print $Config{longsize}, "\n"; | |
4766 | print $Config{longlongsize}, "\n"; | |
ef54e1a4 | 4767 | |
3b10bc60 | 4768 | C<$Config{longlongsize}> is undefined on systems without |
4769 | long long support. | |
851646ae | 4770 | |
ef54e1a4 JH |
4771 | =item * |
4772 | ||
3b10bc60 | 4773 | The integer formats C<s>, C<S>, C<i>, C<I>, C<l>, C<L>, C<j>, and C<J> are |
4774 | inherently non-portable between processors and operating systems because | |
4775 | they obey native byteorder and endianness. For example, a 4-byte integer | |
4776 | 0x12345678 (305419896 decimal) would be ordered natively (arranged in and | |
4777 | handled by the CPU registers) into bytes as | |
61eff3bc | 4778 | |
5ed4f2ec | 4779 | 0x12 0x34 0x56 0x78 # big-endian |
4780 | 0x78 0x56 0x34 0x12 # little-endian | |
61eff3bc | 4781 | |
3b10bc60 | 4782 | Basically, Intel and VAX CPUs are little-endian, while everybody else, |
4783 | including Motorola m68k/88k, PPC, Sparc, HP PA, Power, and Cray, are | |
8f1da26d TC |
4784 | big-endian. Alpha and MIPS can be either: Digital/Compaq uses (well, used) |
4785 | them in little-endian mode, but SGI/Cray uses them in big-endian mode. | |
719a3cf5 | 4786 | |
3b10bc60 | 4787 | The names I<big-endian> and I<little-endian> are comic references to the |
4788 | egg-eating habits of the little-endian Lilliputians and the big-endian | |
4789 | Blefuscudians from the classic Jonathan Swift satire, I<Gulliver's Travels>. | |
4790 | This entered computer lingo via the paper "On Holy Wars and a Plea for | |
4791 | Peace" by Danny Cohen, USC/ISI IEN 137, April 1, 1980. | |
61eff3bc | 4792 | |
140cb37e | 4793 | Some systems may have even weirder byte orders such as |
61eff3bc | 4794 | |
5ed4f2ec | 4795 | 0x56 0x78 0x12 0x34 |
4796 | 0x34 0x12 0x78 0x56 | |
61eff3bc | 4797 | |
3b10bc60 | 4798 | You can determine your system endianness with this incantation: |
ef54e1a4 | 4799 | |
3b10bc60 | 4800 | printf("%#02x ", $_) for unpack("W*", pack L=>0x12345678); |
ef54e1a4 | 4801 | |
d99ad34e | 4802 | The byteorder on the platform where Perl was built is also available |
726ea183 | 4803 | via L<Config>: |
ef54e1a4 | 4804 | |
5ed4f2ec | 4805 | use Config; |
3b10bc60 | 4806 | print "$Config{byteorder}\n"; |
4807 | ||
4808 | or from the command line: | |
ef54e1a4 | 4809 | |
3b10bc60 | 4810 | $ perl -V:byteorder |
719a3cf5 | 4811 | |
3b10bc60 | 4812 | Byteorders C<"1234"> and C<"12345678"> are little-endian; C<"4321"> |
4813 | and C<"87654321"> are big-endian. | |
4814 | ||
4815 | For portably packed integers, either use the formats C<n>, C<N>, C<v>, | |
4816 | and C<V> or else use the C<< > >> and C<< < >> modifiers described | |
4817 | immediately below. See also L<perlport>. | |
ef54e1a4 JH |
4818 | |
4819 | =item * | |
4820 | ||
e9fa405d | 4821 | Starting with Perl 5.10.0, integer and floating-point formats, along with |
3b10bc60 | 4822 | the C<p> and C<P> formats and C<()> groups, may all be followed by the |
4823 | C<< > >> or C<< < >> endianness modifiers to respectively enforce big- | |
4824 | or little-endian byte-order. These modifiers are especially useful | |
8f1da26d | 4825 | given how C<n>, C<N>, C<v>, and C<V> don't cover signed integers, |
3b10bc60 | 4826 | 64-bit integers, or floating-point values. |
4827 | ||
bea6df1c | 4828 | Here are some concerns to keep in mind when using an endianness modifier: |
3b10bc60 | 4829 | |
4830 | =over | |
4831 | ||
4832 | =item * | |
4833 | ||
4834 | Exchanging signed integers between different platforms works only | |
4835 | when all platforms store them in the same format. Most platforms store | |
4836 | signed integers in two's-complement notation, so usually this is not an issue. | |
1109a392 | 4837 | |
3b10bc60 | 4838 | =item * |
1109a392 | 4839 | |
3b10bc60 | 4840 | The C<< > >> or C<< < >> modifiers can only be used on floating-point |
1109a392 | 4841 | formats on big- or little-endian machines. Otherwise, attempting to |
3b10bc60 | 4842 | use them raises an exception. |
1109a392 | 4843 | |
3b10bc60 | 4844 | =item * |
4845 | ||
4846 | Forcing big- or little-endian byte-order on floating-point values for | |
4847 | data exchange can work only if all platforms use the same | |
4848 | binary representation such as IEEE floating-point. Even if all | |
4849 | platforms are using IEEE, there may still be subtle differences. Being able | |
4850 | to use C<< > >> or C<< < >> on floating-point values can be useful, | |
80d38338 | 4851 | but also dangerous if you don't know exactly what you're doing. |
3b10bc60 | 4852 | It is not a general way to portably store floating-point values. |
4853 | ||
4854 | =item * | |
1109a392 | 4855 | |
3b10bc60 | 4856 | When using C<< > >> or C<< < >> on a C<()> group, this affects |
4857 | all types inside the group that accept byte-order modifiers, | |
4858 | including all subgroups. It is silently ignored for all other | |
66c611c5 MHM |
4859 | types. You are not allowed to override the byte-order within a group |
4860 | that already has a byte-order modifier suffix. | |
4861 | ||
3b10bc60 | 4862 | =back |
4863 | ||
1109a392 MHM |
4864 | =item * |
4865 | ||
3b10bc60 | 4866 | Real numbers (floats and doubles) are in native machine format only. |
4867 | Due to the multiplicity of floating-point formats and the lack of a | |
4868 | standard "network" representation for them, no facility for interchange has been | |
4869 | made. This means that packed floating-point data written on one machine | |
4870 | may not be readable on another, even if both use IEEE floating-point | |
4871 | arithmetic (because the endianness of the memory representation is not part | |
851646ae | 4872 | of the IEEE spec). See also L<perlport>. |
5a929a98 | 4873 | |
3b10bc60 | 4874 | If you know I<exactly> what you're doing, you can use the C<< > >> or C<< < >> |
4875 | modifiers to force big- or little-endian byte-order on floating-point values. | |
1109a392 | 4876 | |
3b10bc60 | 4877 | Because Perl uses doubles (or long doubles, if configured) internally for |
4878 | all numeric calculation, converting from double into float and thence | |
4879 | to double again loses precision, so C<unpack("f", pack("f", $foo)>) | |
4880 | will not in general equal $foo. | |
5a929a98 | 4881 | |
851646ae JH |
4882 | =item * |
4883 | ||
3b10bc60 | 4884 | Pack and unpack can operate in two modes: character mode (C<C0> mode) where |
4885 | the packed string is processed per character, and UTF-8 mode (C<U0> mode) | |
f337b084 | 4886 | where the packed string is processed in its UTF-8-encoded Unicode form on |
391b733c FC |
4887 | a byte-by-byte basis. Character mode is the default |
4888 | unless the format string starts with C<U>. You | |
4889 | can always switch mode mid-format with an explicit | |
3b10bc60 | 4890 | C<C0> or C<U0> in the format. This mode remains in effect until the next |
4891 | mode change, or until the end of the C<()> group it (directly) applies to. | |
036b4402 | 4892 | |
8f1da26d TC |
4893 | Using C<C0> to get Unicode characters while using C<U0> to get I<non>-Unicode |
4894 | bytes is not necessarily obvious. Probably only the first of these | |
4895 | is what you want: | |
4896 | ||
4897 | $ perl -CS -E 'say "\x{3B1}\x{3C9}"' | | |
4898 | perl -CS -ne 'printf "%v04X\n", $_ for unpack("C0A*", $_)' | |
4899 | 03B1.03C9 | |
4900 | $ perl -CS -E 'say "\x{3B1}\x{3C9}"' | | |
4901 | perl -CS -ne 'printf "%v02X\n", $_ for unpack("U0A*", $_)' | |
4902 | CE.B1.CF.89 | |
4903 | $ perl -CS -E 'say "\x{3B1}\x{3C9}"' | | |
4904 | perl -C0 -ne 'printf "%v02X\n", $_ for unpack("C0A*", $_)' | |
4905 | CE.B1.CF.89 | |
4906 | $ perl -CS -E 'say "\x{3B1}\x{3C9}"' | | |
4907 | perl -C0 -ne 'printf "%v02X\n", $_ for unpack("U0A*", $_)' | |
4908 | C3.8E.C2.B1.C3.8F.C2.89 | |
4909 | ||
4910 | Those examples also illustrate that you should not try to use | |
4911 | C<pack>/C<unpack> as a substitute for the L<Encode> module. | |
4912 | ||
036b4402 GS |
4913 | =item * |
4914 | ||
3b10bc60 | 4915 | You must yourself do any alignment or padding by inserting, for example, |
4916 | enough C<"x">es while packing. There is no way for pack() and unpack() | |
4917 | to know where characters are going to or coming from, so they | |
4918 | handle their output and input as flat sequences of characters. | |
851646ae | 4919 | |
17f4a12d IZ |
4920 | =item * |
4921 | ||
3b10bc60 | 4922 | A C<()> group is a sub-TEMPLATE enclosed in parentheses. A group may |
4923 | take a repeat count either as postfix, or for unpack(), also via the C</> | |
4924 | template character. Within each repetition of a group, positioning with | |
391b733c | 4925 | C<@> starts over at 0. Therefore, the result of |
49704364 | 4926 | |
3b10bc60 | 4927 | pack("@1A((@2A)@3A)", qw[X Y Z]) |
49704364 | 4928 | |
3b10bc60 | 4929 | is the string C<"\0X\0\0YZ">. |
49704364 | 4930 | |
18529408 IZ |
4931 | =item * |
4932 | ||
3b10bc60 | 4933 | C<x> and C<X> accept the C<!> modifier to act as alignment commands: they |
4934 | jump forward or back to the closest position aligned at a multiple of C<count> | |
391b733c | 4935 | characters. For example, to pack() or unpack() a C structure like |
666f95b9 | 4936 | |
3b10bc60 | 4937 | struct { |
4938 | char c; /* one signed, 8-bit character */ | |
4939 | double d; | |
4940 | char cc[2]; | |
4941 | } | |
4942 | ||
4943 | one may need to use the template C<c x![d] d c[2]>. This assumes that | |
4944 | doubles must be aligned to the size of double. | |
4945 | ||
4946 | For alignment commands, a C<count> of 0 is equivalent to a C<count> of 1; | |
4947 | both are no-ops. | |
666f95b9 | 4948 | |
62f95557 IZ |
4949 | =item * |
4950 | ||
3b10bc60 | 4951 | C<n>, C<N>, C<v> and C<V> accept the C<!> modifier to |
4952 | represent signed 16-/32-bit integers in big-/little-endian order. | |
4953 | This is portable only when all platforms sharing packed data use the | |
4954 | same binary representation for signed integers; for example, when all | |
4955 | platforms use two's-complement representation. | |
068bd2e7 MHM |
4956 | |
4957 | =item * | |
4958 | ||
3b10bc60 | 4959 | Comments can be embedded in a TEMPLATE using C<#> through the end of line. |
4960 | White space can separate pack codes from each other, but modifiers and | |
4961 | repeat counts must follow immediately. Breaking complex templates into | |
4962 | individual line-by-line components, suitably annotated, can do as much to | |
4963 | improve legibility and maintainability of pack/unpack formats as C</x> can | |
4964 | for complicated pattern matches. | |
17f4a12d | 4965 | |
2b6c5635 GS |
4966 | =item * |
4967 | ||
bea6df1c | 4968 | If TEMPLATE requires more arguments than pack() is given, pack() |
cf264981 | 4969 | assumes additional C<""> arguments. If TEMPLATE requires fewer arguments |
3b10bc60 | 4970 | than given, extra arguments are ignored. |
2b6c5635 | 4971 | |
5a929a98 | 4972 | =back |
a0d0e21e LW |
4973 | |
4974 | Examples: | |
4975 | ||
f337b084 | 4976 | $foo = pack("WWWW",65,66,67,68); |
a0d0e21e | 4977 | # foo eq "ABCD" |
f337b084 | 4978 | $foo = pack("W4",65,66,67,68); |
a0d0e21e | 4979 | # same thing |
f337b084 TH |
4980 | $foo = pack("W4",0x24b6,0x24b7,0x24b8,0x24b9); |
4981 | # same thing with Unicode circled letters. | |
a0ed51b3 | 4982 | $foo = pack("U4",0x24b6,0x24b7,0x24b8,0x24b9); |
391b733c | 4983 | # same thing with Unicode circled letters. You don't get the |
4d0444a3 FC |
4984 | # UTF-8 bytes because the U at the start of the format caused |
4985 | # a switch to U0-mode, so the UTF-8 bytes get joined into | |
4986 | # characters | |
f337b084 TH |
4987 | $foo = pack("C0U4",0x24b6,0x24b7,0x24b8,0x24b9); |
4988 | # foo eq "\xe2\x92\xb6\xe2\x92\xb7\xe2\x92\xb8\xe2\x92\xb9" | |
4d0444a3 FC |
4989 | # This is the UTF-8 encoding of the string in the |
4990 | # previous example | |
a0d0e21e LW |
4991 | |
4992 | $foo = pack("ccxxcc",65,66,67,68); | |
4993 | # foo eq "AB\0\0CD" | |
4994 | ||
3b10bc60 | 4995 | # NOTE: The examples above featuring "W" and "c" are true |
9ccd05c0 | 4996 | # only on ASCII and ASCII-derived systems such as ISO Latin 1 |
3b10bc60 | 4997 | # and UTF-8. On EBCDIC systems, the first example would be |
4998 | # $foo = pack("WWWW",193,194,195,196); | |
9ccd05c0 | 4999 | |
a0d0e21e | 5000 | $foo = pack("s2",1,2); |
ce7b6f06 KW |
5001 | # "\001\000\002\000" on little-endian |
5002 | # "\000\001\000\002" on big-endian | |
a0d0e21e LW |
5003 | |
5004 | $foo = pack("a4","abcd","x","y","z"); | |
5005 | # "abcd" | |
5006 | ||
5007 | $foo = pack("aaaa","abcd","x","y","z"); | |
5008 | # "axyz" | |
5009 | ||
5010 | $foo = pack("a14","abcdefg"); | |
5011 | # "abcdefg\0\0\0\0\0\0\0" | |
5012 | ||
5013 | $foo = pack("i9pl", gmtime); | |
5014 | # a real struct tm (on my system anyway) | |
5015 | ||
5a929a98 VU |
5016 | $utmp_template = "Z8 Z8 Z16 L"; |
5017 | $utmp = pack($utmp_template, @utmp1); | |
5018 | # a struct utmp (BSDish) | |
5019 | ||
5020 | @utmp2 = unpack($utmp_template, $utmp); | |
5021 | # "@utmp1" eq "@utmp2" | |
5022 | ||
a0d0e21e | 5023 | sub bintodec { |
a9a5a0dc | 5024 | unpack("N", pack("B32", substr("0" x 32 . shift, -32))); |
a0d0e21e LW |
5025 | } |
5026 | ||
851646ae JH |
5027 | $foo = pack('sx2l', 12, 34); |
5028 | # short 12, two zero bytes padding, long 34 | |
5029 | $bar = pack('s@4l', 12, 34); | |
5030 | # short 12, zero fill to position 4, long 34 | |
5031 | # $foo eq $bar | |
28be1210 TH |
5032 | $baz = pack('s.l', 12, 4, 34); |
5033 | # short 12, zero fill to position 4, long 34 | |
851646ae | 5034 | |
1109a392 MHM |
5035 | $foo = pack('nN', 42, 4711); |
5036 | # pack big-endian 16- and 32-bit unsigned integers | |
5037 | $foo = pack('S>L>', 42, 4711); | |
5038 | # exactly the same | |
5039 | $foo = pack('s<l<', -42, 4711); | |
5040 | # pack little-endian 16- and 32-bit signed integers | |
66c611c5 MHM |
5041 | $foo = pack('(sl)<', -42, 4711); |
5042 | # exactly the same | |
1109a392 | 5043 | |
5a929a98 | 5044 | The same template may generally also be used in unpack(). |
a0d0e21e | 5045 | |
8f1da26d TC |
5046 | =item package NAMESPACE |
5047 | ||
6fa4d285 DG |
5048 | =item package NAMESPACE VERSION |
5049 | X<package> X<module> X<namespace> X<version> | |
5050 | ||
8f1da26d | 5051 | =item package NAMESPACE BLOCK |
cb1a09d0 | 5052 | |
4e4da3ac Z |
5053 | =item package NAMESPACE VERSION BLOCK |
5054 | X<package> X<module> X<namespace> X<version> | |
5055 | ||
c17cdb72 NC |
5056 | =for Pod::Functions declare a separate global namespace |
5057 | ||
8f1da26d TC |
5058 | Declares the BLOCK or the rest of the compilation unit as being in the |
5059 | given namespace. The scope of the package declaration is either the | |
4e4da3ac | 5060 | supplied code BLOCK or, in the absence of a BLOCK, from the declaration |
8f1da26d TC |
5061 | itself through the end of current scope (the enclosing block, file, or |
5062 | C<eval>). That is, the forms without a BLOCK are operative through the end | |
5063 | of the current scope, just like the C<my>, C<state>, and C<our> operators. | |
5064 | All unqualified dynamic identifiers in this scope will be in the given | |
5065 | namespace, except where overridden by another C<package> declaration or | |
5066 | when they're one of the special identifiers that qualify into C<main::>, | |
5067 | like C<STDOUT>, C<ARGV>, C<ENV>, and the punctuation variables. | |
4e4da3ac | 5068 | |
3b10bc60 | 5069 | A package statement affects dynamic variables only, including those |
4dd95518 | 5070 | you've used C<local> on, but I<not> lexically-scoped variables, which are created |
8f1da26d | 5071 | with C<my>, C<state>, or C<our>. Typically it would be the first |
3b10bc60 | 5072 | declaration in a file included by C<require> or C<use>. You can switch into a |
5073 | package in more than one place, since this only determines which default | |
5074 | symbol table the compiler uses for the rest of that block. You can refer to | |
5075 | identifiers in other packages than the current one by prefixing the identifier | |
5076 | with the package name and a double colon, as in C<$SomePack::var> | |
5077 | or C<ThatPack::INPUT_HANDLE>. If package name is omitted, the C<main> | |
5078 | package as assumed. That is, C<$::sail> is equivalent to | |
5079 | C<$main::sail> (as well as to C<$main'sail>, still seen in ancient | |
5080 | code, mostly from Perl 4). | |
5081 | ||
bd12309b | 5082 | If VERSION is provided, C<package> sets the C<$VERSION> variable in the given |
a2bff36e DG |
5083 | namespace to a L<version> object with the VERSION provided. VERSION must be a |
5084 | "strict" style version number as defined by the L<version> module: a positive | |
5085 | decimal number (integer or decimal-fraction) without exponentiation or else a | |
5086 | dotted-decimal v-string with a leading 'v' character and at least three | |
5087 | components. You should set C<$VERSION> only once per package. | |
6fa4d285 | 5088 | |
cb1a09d0 AD |
5089 | See L<perlmod/"Packages"> for more information about packages, modules, |
5090 | and classes. See L<perlsub> for other scoping issues. | |
5091 | ||
f5fa2679 NC |
5092 | =item __PACKAGE__ |
5093 | X<__PACKAGE__> | |
5094 | ||
d9b04284 | 5095 | =for Pod::Functions +5.004 the current package |
c17cdb72 | 5096 | |
f5fa2679 NC |
5097 | A special token that returns the name of the package in which it occurs. |
5098 | ||
a0d0e21e | 5099 | =item pipe READHANDLE,WRITEHANDLE |
d74e8afc | 5100 | X<pipe> |
a0d0e21e | 5101 | |
c17cdb72 NC |
5102 | =for Pod::Functions open a pair of connected filehandles |
5103 | ||
a0d0e21e LW |
5104 | Opens a pair of connected pipes like the corresponding system call. |
5105 | Note that if you set up a loop of piped processes, deadlock can occur | |
5106 | unless you are very careful. In addition, note that Perl's pipes use | |
9124316e | 5107 | IO buffering, so you may need to set C<$|> to flush your WRITEHANDLE |
a0d0e21e LW |
5108 | after each command, depending on the application. |
5109 | ||
f7a9f755 TC |
5110 | Returns true on success. |
5111 | ||
96090e4f LB |
5112 | See L<IPC::Open2>, L<IPC::Open3>, and |
5113 | L<perlipc/"Bidirectional Communication with Another Process"> | |
4633a7c4 LW |
5114 | for examples of such things. |
5115 | ||
3b10bc60 | 5116 | On systems that support a close-on-exec flag on files, that flag is set |
5117 | on all newly opened file descriptors whose C<fileno>s are I<higher> than | |
5118 | the current value of $^F (by default 2 for C<STDERR>). See L<perlvar/$^F>. | |
4771b018 | 5119 | |
532eee96 | 5120 | =item pop ARRAY |
d74e8afc | 5121 | X<pop> X<stack> |
a0d0e21e | 5122 | |
f5a93a43 TC |
5123 | =item pop EXPR |
5124 | ||
54310121 | 5125 | =item pop |
28757baa | 5126 | |
c17cdb72 NC |
5127 | =for Pod::Functions remove the last element from an array and return it |
5128 | ||
a0d0e21e | 5129 | Pops and returns the last value of the array, shortening the array by |
cd7f9af7 | 5130 | one element. |
a0d0e21e | 5131 | |
3b10bc60 | 5132 | Returns the undefined value if the array is empty, although this may also |
5133 | happen at other times. If ARRAY is omitted, pops the C<@ARGV> array in the | |
5134 | main program, but the C<@_> array in subroutines, just like C<shift>. | |
a0d0e21e | 5135 | |
f5a93a43 TC |
5136 | Starting with Perl 5.14, C<pop> can take a scalar EXPR, which must hold a |
5137 | reference to an unblessed array. The argument will be dereferenced | |
5138 | automatically. This aspect of C<pop> is considered highly experimental. | |
5139 | The exact behaviour may change in a future version of Perl. | |
cba5a3b0 | 5140 | |
bade7fbc TC |
5141 | To avoid confusing would-be users of your code who are running earlier |
5142 | versions of Perl with mysterious syntax errors, put this sort of thing at | |
5143 | the top of your file to signal that your code will work I<only> on Perls of | |
5144 | a recent vintage: | |
5145 | ||
5146 | use 5.014; # so push/pop/etc work on scalars (experimental) | |
5147 | ||
a0d0e21e | 5148 | =item pos SCALAR |
d74e8afc | 5149 | X<pos> X<match, position> |
a0d0e21e | 5150 | |
54310121 | 5151 | =item pos |
bbce6d69 | 5152 | |
c17cdb72 NC |
5153 | =for Pod::Functions find or set the offset for the last/next m//g search |
5154 | ||
7664c618 | 5155 | Returns the offset of where the last C<m//g> search left off for the |
5156 | variable in question (C<$_> is used when the variable is not | |
391b733c | 5157 | specified). Note that 0 is a valid match offset. C<undef> indicates |
7664c618 | 5158 | that the search position is reset (usually due to match failure, but |
5159 | can also be because no match has yet been run on the scalar). | |
5160 | ||
5161 | C<pos> directly accesses the location used by the regexp engine to | |
5162 | store the offset, so assigning to C<pos> will change that offset, and | |
5163 | so will also influence the C<\G> zero-width assertion in regular | |
391b733c | 5164 | expressions. Both of these effects take place for the next match, so |
7664c618 | 5165 | you can't affect the position with C<pos> during the current match, |
5166 | such as in C<(?{pos() = 5})> or C<s//pos() = 5/e>. | |
5167 | ||
f9179917 FC |
5168 | Setting C<pos> also resets the I<matched with zero-length> flag, described |
5169 | under L<perlre/"Repeated Patterns Matching a Zero-length Substring">. | |
5170 | ||
7664c618 | 5171 | Because a failed C<m//gc> match doesn't reset the offset, the return |
5172 | from C<pos> won't change either in this case. See L<perlre> and | |
44a8e56a | 5173 | L<perlop>. |
a0d0e21e LW |
5174 | |
5175 | =item print FILEHANDLE LIST | |
d74e8afc | 5176 | X<print> |
a0d0e21e | 5177 | |
dee33c94 TC |
5178 | =item print FILEHANDLE |
5179 | ||
a0d0e21e LW |
5180 | =item print LIST |
5181 | ||
5182 | =item print | |
5183 | ||
c17cdb72 NC |
5184 | =for Pod::Functions output a list to a filehandle |
5185 | ||
19799a22 | 5186 | Prints a string or a list of strings. Returns true if successful. |
dee33c94 TC |
5187 | FILEHANDLE may be a scalar variable containing the name of or a reference |
5188 | to the filehandle, thus introducing one level of indirection. (NOTE: If | |
5189 | FILEHANDLE is a variable and the next token is a term, it may be | |
5190 | misinterpreted as an operator unless you interpose a C<+> or put | |
391b733c | 5191 | parentheses around the arguments.) If FILEHANDLE is omitted, prints to the |
8f1da26d TC |
5192 | last selected (see L</select>) output handle. If LIST is omitted, prints |
5193 | C<$_> to the currently selected output handle. To use FILEHANDLE alone to | |
5194 | print the content of C<$_> to it, you must use a real filehandle like | |
5195 | C<FH>, not an indirect one like C<$fh>. To set the default output handle | |
5196 | to something other than STDOUT, use the select operation. | |
5197 | ||
5198 | The current value of C<$,> (if any) is printed between each LIST item. The | |
5199 | current value of C<$\> (if any) is printed after the entire LIST has been | |
5200 | printed. Because print takes a LIST, anything in the LIST is evaluated in | |
5201 | list context, including any subroutines whose return lists you pass to | |
5202 | C<print>. Be careful not to follow the print keyword with a left | |
5203 | parenthesis unless you want the corresponding right parenthesis to | |
5204 | terminate the arguments to the print; put parentheses around all arguments | |
5205 | (or interpose a C<+>, but that doesn't look as good). | |
5206 | ||
5207 | If you're storing handles in an array or hash, or in general whenever | |
5208 | you're using any expression more complex than a bareword handle or a plain, | |
5209 | unsubscripted scalar variable to retrieve it, you will have to use a block | |
5210 | returning the filehandle value instead, in which case the LIST may not be | |
5211 | omitted: | |
4633a7c4 LW |
5212 | |
5213 | print { $files[$i] } "stuff\n"; | |
5214 | print { $OK ? STDOUT : STDERR } "stuff\n"; | |
5215 | ||
785fd561 DG |
5216 | Printing to a closed pipe or socket will generate a SIGPIPE signal. See |
5217 | L<perlipc> for more on signal handling. | |
5218 | ||
5f05dabc | 5219 | =item printf FILEHANDLE FORMAT, LIST |
d74e8afc | 5220 | X<printf> |
a0d0e21e | 5221 | |
dee33c94 TC |
5222 | =item printf FILEHANDLE |
5223 | ||
5f05dabc | 5224 | =item printf FORMAT, LIST |
a0d0e21e | 5225 | |
dee33c94 TC |
5226 | =item printf |
5227 | ||
c17cdb72 NC |
5228 | =for Pod::Functions output a formatted list to a filehandle |
5229 | ||
7660c0ab | 5230 | Equivalent to C<print FILEHANDLE sprintf(FORMAT, LIST)>, except that C<$\> |
2ad09a1f FC |
5231 | (the output record separator) is not appended. The FORMAT and the |
5232 | LIST are actually parsed as a single list. The first argument | |
5233 | of the list will be interpreted as the C<printf> format. This | |
5234 | means that C<printf(@_)> will use C<$_[0]> as the format. See | |
01aa884e | 5235 | L<sprintf|/sprintf FORMAT, LIST> for an |
2ad09a1f | 5236 | explanation of the format argument. If C<use locale> (including |
66cbab2c | 5237 | C<use locale ':not_characters'>) is in effect and |
dee33c94 | 5238 | POSIX::setlocale() has been called, the character used for the decimal |
3b10bc60 | 5239 | separator in formatted floating-point numbers is affected by the LC_NUMERIC |
dee33c94 | 5240 | locale setting. See L<perllocale> and L<POSIX>. |
a0d0e21e | 5241 | |
2ad09a1f FC |
5242 | For historical reasons, if you omit the list, C<$_> is used as the format; |
5243 | to use FILEHANDLE without a list, you must use a real filehandle like | |
5244 | C<FH>, not an indirect one like C<$fh>. However, this will rarely do what | |
5245 | you want; if $_ contains formatting codes, they will be replaced with the | |
5246 | empty string and a warning will be emitted if warnings are enabled. Just | |
5247 | use C<print> if you want to print the contents of $_. | |
5248 | ||
19799a22 GS |
5249 | Don't fall into the trap of using a C<printf> when a simple |
5250 | C<print> would do. The C<print> is more efficient and less | |
28757baa | 5251 | error prone. |
5252 | ||
da0045b7 | 5253 | =item prototype FUNCTION |
d74e8afc | 5254 | X<prototype> |
da0045b7 | 5255 | |
d9b04284 | 5256 | =for Pod::Functions +5.002 get the prototype (if any) of a subroutine |
c17cdb72 | 5257 | |
da0045b7 | 5258 | Returns the prototype of a function as a string (or C<undef> if the |
5f05dabc | 5259 | function has no prototype). FUNCTION is a reference to, or the name of, |
5260 | the function whose prototype you want to retrieve. | |
da0045b7 | 5261 | |
2b5ab1e7 | 5262 | If FUNCTION is a string starting with C<CORE::>, the rest is taken as a |
85d83254 FC |
5263 | name for a Perl builtin. If the builtin's arguments |
5264 | cannot be adequately expressed by a prototype | |
0a2ca743 RGS |
5265 | (such as C<system>), prototype() returns C<undef>, because the builtin |
5266 | does not really behave like a Perl function. Otherwise, the string | |
5267 | describing the equivalent prototype is returned. | |
b6c543e3 | 5268 | |
532eee96 | 5269 | =item push ARRAY,LIST |
1dc8ecb8 | 5270 | X<push> X<stack> |
a0d0e21e | 5271 | |
f5a93a43 TC |
5272 | =item push EXPR,LIST |
5273 | ||
c17cdb72 NC |
5274 | =for Pod::Functions append one or more elements to an array |
5275 | ||
8f1da26d TC |
5276 | Treats ARRAY as a stack by appending the values of LIST to the end of |
5277 | ARRAY. The length of ARRAY increases by the length of LIST. Has the same | |
5278 | effect as | |
a0d0e21e LW |
5279 | |
5280 | for $value (LIST) { | |
a9a5a0dc | 5281 | $ARRAY[++$#ARRAY] = $value; |
a0d0e21e LW |
5282 | } |
5283 | ||
cde9c211 SP |
5284 | but is more efficient. Returns the number of elements in the array following |
5285 | the completed C<push>. | |
a0d0e21e | 5286 | |
f5a93a43 TC |
5287 | Starting with Perl 5.14, C<push> can take a scalar EXPR, which must hold a |
5288 | reference to an unblessed array. The argument will be dereferenced | |
5289 | automatically. This aspect of C<push> is considered highly experimental. | |
5290 | The exact behaviour may change in a future version of Perl. | |
cba5a3b0 | 5291 | |
bade7fbc TC |
5292 | To avoid confusing would-be users of your code who are running earlier |
5293 | versions of Perl with mysterious syntax errors, put this sort of thing at | |
5294 | the top of your file to signal that your code will work I<only> on Perls of | |
5295 | a recent vintage: | |
5296 | ||
5297 | use 5.014; # so push/pop/etc work on scalars (experimental) | |
5298 | ||
a0d0e21e LW |
5299 | =item q/STRING/ |
5300 | ||
c17cdb72 NC |
5301 | =for Pod::Functions singly quote a string |
5302 | ||
a0d0e21e LW |
5303 | =item qq/STRING/ |
5304 | ||
c17cdb72 NC |
5305 | =for Pod::Functions doubly quote a string |
5306 | ||
a0d0e21e LW |
5307 | =item qw/STRING/ |
5308 | ||
c17cdb72 NC |
5309 | =for Pod::Functions quote a list of words |
5310 | ||
f5fa2679 NC |
5311 | =item qx/STRING/ |
5312 | ||
c17cdb72 NC |
5313 | =for Pod::Functions backquote quote a string |
5314 | ||
1d888ee3 MK |
5315 | Generalized quotes. See L<perlop/"Quote-Like Operators">. |
5316 | ||
5317 | =item qr/STRING/ | |
5318 | ||
d9b04284 | 5319 | =for Pod::Functions +5.005 compile pattern |
c17cdb72 | 5320 | |
1d888ee3 | 5321 | Regexp-like quote. See L<perlop/"Regexp Quote-Like Operators">. |
a0d0e21e LW |
5322 | |
5323 | =item quotemeta EXPR | |
d74e8afc | 5324 | X<quotemeta> X<metacharacter> |
a0d0e21e | 5325 | |
54310121 | 5326 | =item quotemeta |
bbce6d69 | 5327 | |
c17cdb72 NC |
5328 | =for Pod::Functions quote regular expression magic characters |
5329 | ||
4cd68991 KW |
5330 | Returns the value of EXPR with all the ASCII non-"word" |
5331 | characters backslashed. (That is, all ASCII characters not matching | |
a034a98d DD |
5332 | C</[A-Za-z_0-9]/> will be preceded by a backslash in the |
5333 | returned string, regardless of any locale settings.) | |
5334 | This is the internal function implementing | |
7660c0ab | 5335 | the C<\Q> escape in double-quoted strings. |
4cd68991 | 5336 | (See below for the behavior on non-ASCII code points.) |
a0d0e21e | 5337 | |
7660c0ab | 5338 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 5339 | |
9702b155 RGS |
5340 | quotemeta (and C<\Q> ... C<\E>) are useful when interpolating strings into |
5341 | regular expressions, because by default an interpolated variable will be | |
391b733c | 5342 | considered a mini-regular expression. For example: |
9702b155 RGS |
5343 | |
5344 | my $sentence = 'The quick brown fox jumped over the lazy dog'; | |
5345 | my $substring = 'quick.*?fox'; | |
5346 | $sentence =~ s{$substring}{big bad wolf}; | |
5347 | ||
5348 | Will cause C<$sentence> to become C<'The big bad wolf jumped over...'>. | |
5349 | ||
5350 | On the other hand: | |
5351 | ||
5352 | my $sentence = 'The quick brown fox jumped over the lazy dog'; | |
5353 | my $substring = 'quick.*?fox'; | |
5354 | $sentence =~ s{\Q$substring\E}{big bad wolf}; | |
5355 | ||
5356 | Or: | |
5357 | ||
5358 | my $sentence = 'The quick brown fox jumped over the lazy dog'; | |
5359 | my $substring = 'quick.*?fox'; | |
5360 | my $quoted_substring = quotemeta($substring); | |
5361 | $sentence =~ s{$quoted_substring}{big bad wolf}; | |
5362 | ||
391b733c FC |
5363 | Will both leave the sentence as is. |
5364 | Normally, when accepting literal string | |
8f1da26d | 5365 | input from the user, quotemeta() or C<\Q> must be used. |
9702b155 | 5366 | |
4cd68991 KW |
5367 | In Perl v5.14, all non-ASCII characters are quoted in non-UTF-8-encoded |
5368 | strings, but not quoted in UTF-8 strings. | |
2e2b2571 KW |
5369 | |
5370 | Starting in Perl v5.16, Perl adopted a Unicode-defined strategy for | |
5371 | quoting non-ASCII characters; the quoting of ASCII characters is | |
5372 | unchanged. | |
5373 | ||
5374 | Also unchanged is the quoting of non-UTF-8 strings when outside the | |
5375 | scope of a C<use feature 'unicode_strings'>, which is to quote all | |
5376 | characters in the upper Latin1 range. This provides complete backwards | |
5377 | compatibility for old programs which do not use Unicode. (Note that | |
5378 | C<unicode_strings> is automatically enabled within the scope of a | |
5379 | S<C<use v5.12>> or greater.) | |
5380 | ||
20adcf7c KW |
5381 | Within the scope of C<use locale>, all non-ASCII Latin1 code points |
5382 | are quoted whether the string is encoded as UTF-8 or not. As mentioned | |
5383 | above, locale does not affect the quoting of ASCII-range characters. | |
5384 | This protects against those locales where characters such as C<"|"> are | |
5385 | considered to be word characters. | |
5386 | ||
2e2b2571 | 5387 | Otherwise, Perl quotes non-ASCII characters using an adaptation from |
f321be7e | 5388 | Unicode (see L<http://www.unicode.org/reports/tr31/>). |
2e2b2571 KW |
5389 | The only code points that are quoted are those that have any of the |
5390 | Unicode properties: Pattern_Syntax, Pattern_White_Space, White_Space, | |
5391 | Default_Ignorable_Code_Point, or General_Category=Control. | |
5392 | ||
5393 | Of these properties, the two important ones are Pattern_Syntax and | |
5394 | Pattern_White_Space. They have been set up by Unicode for exactly this | |
5395 | purpose of deciding which characters in a regular expression pattern | |
5396 | should be quoted. No character that can be in an identifier has these | |
5397 | properties. | |
5398 | ||
5399 | Perl promises, that if we ever add regular expression pattern | |
5400 | metacharacters to the dozen already defined | |
5401 | (C<\ E<verbar> ( ) [ { ^ $ * + ? .>), that we will only use ones that have the | |
5402 | Pattern_Syntax property. Perl also promises, that if we ever add | |
5403 | characters that are considered to be white space in regular expressions | |
5404 | (currently mostly affected by C</x>), they will all have the | |
5405 | Pattern_White_Space property. | |
5406 | ||
5407 | Unicode promises that the set of code points that have these two | |
5408 | properties will never change, so something that is not quoted in v5.16 | |
5409 | will never need to be quoted in any future Perl release. (Not all the | |
5410 | code points that match Pattern_Syntax have actually had characters | |
5411 | assigned to them; so there is room to grow, but they are quoted | |
5412 | whether assigned or not. Perl, of course, would never use an | |
5413 | unassigned code point as an actual metacharacter.) | |
5414 | ||
5415 | Quoting characters that have the other 3 properties is done to enhance | |
5416 | the readability of the regular expression and not because they actually | |
5417 | need to be quoted for regular expression purposes (characters with the | |
5418 | White_Space property are likely to be indistinguishable on the page or | |
5419 | screen from those with the Pattern_White_Space property; and the other | |
5420 | two properties contain non-printing characters). | |
b29c72cb | 5421 | |
a0d0e21e | 5422 | =item rand EXPR |
d74e8afc | 5423 | X<rand> X<random> |
a0d0e21e LW |
5424 | |
5425 | =item rand | |
5426 | ||
c17cdb72 NC |
5427 | =for Pod::Functions retrieve the next pseudorandom number |
5428 | ||
7660c0ab | 5429 | Returns a random fractional number greater than or equal to C<0> and less |
3e3baf6d | 5430 | than the value of EXPR. (EXPR should be positive.) If EXPR is |
351f3254 | 5431 | omitted, the value C<1> is used. Currently EXPR with the value C<0> is |
3b10bc60 | 5432 | also special-cased as C<1> (this was undocumented before Perl 5.8.0 |
5433 | and is subject to change in future versions of Perl). Automatically calls | |
351f3254 | 5434 | C<srand> unless C<srand> has already been called. See also C<srand>. |
a0d0e21e | 5435 | |
6063ba18 WM |
5436 | Apply C<int()> to the value returned by C<rand()> if you want random |
5437 | integers instead of random fractional numbers. For example, | |
5438 | ||
5439 | int(rand(10)) | |
5440 | ||
5441 | returns a random integer between C<0> and C<9>, inclusive. | |
5442 | ||
2f9daede | 5443 | (Note: If your rand function consistently returns numbers that are too |
a0d0e21e | 5444 | large or too small, then your version of Perl was probably compiled |
2f9daede | 5445 | with the wrong number of RANDBITS.) |
a0d0e21e | 5446 | |
9700c45b JV |
5447 | B<C<rand()> is not cryptographically secure. You should not rely |
5448 | on it in security-sensitive situations.> As of this writing, a | |
5449 | number of third-party CPAN modules offer random number generators | |
5450 | intended by their authors to be cryptographically secure, | |
416e3a83 AMS |
5451 | including: L<Data::Entropy>, L<Crypt::Random>, L<Math::Random::Secure>, |
5452 | and L<Math::TrulyRandom>. | |
9700c45b | 5453 | |
a0d0e21e | 5454 | =item read FILEHANDLE,SCALAR,LENGTH,OFFSET |
f723aae1 | 5455 | X<read> X<file, read> |
a0d0e21e LW |
5456 | |
5457 | =item read FILEHANDLE,SCALAR,LENGTH | |
5458 | ||
c17cdb72 NC |
5459 | =for Pod::Functions fixed-length buffered input from a filehandle |
5460 | ||
9124316e JH |
5461 | Attempts to read LENGTH I<characters> of data into variable SCALAR |
5462 | from the specified FILEHANDLE. Returns the number of characters | |
b5fe5ca2 | 5463 | actually read, C<0> at end of file, or undef if there was an error (in |
b49f3be6 SG |
5464 | the latter case C<$!> is also set). SCALAR will be grown or shrunk |
5465 | so that the last character actually read is the last character of the | |
5466 | scalar after the read. | |
5467 | ||
5468 | An OFFSET may be specified to place the read data at some place in the | |
5469 | string other than the beginning. A negative OFFSET specifies | |
5470 | placement at that many characters counting backwards from the end of | |
5471 | the string. A positive OFFSET greater than the length of SCALAR | |
5472 | results in the string being padded to the required size with C<"\0"> | |
5473 | bytes before the result of the read is appended. | |
5474 | ||
80d38338 | 5475 | The call is implemented in terms of either Perl's or your system's native |
01aa884e KW |
5476 | fread(3) library function. To get a true read(2) system call, see |
5477 | L<sysread|/sysread FILEHANDLE,SCALAR,LENGTH,OFFSET>. | |
9124316e JH |
5478 | |
5479 | Note the I<characters>: depending on the status of the filehandle, | |
8f1da26d | 5480 | either (8-bit) bytes or characters are read. By default, all |
9124316e | 5481 | filehandles operate on bytes, but for example if the filehandle has |
fae2c0fb | 5482 | been opened with the C<:utf8> I/O layer (see L</open>, and the C<open> |
8f1da26d | 5483 | pragma, L<open>), the I/O will operate on UTF8-encoded Unicode |
1d714267 JH |
5484 | characters, not bytes. Similarly for the C<:encoding> pragma: |
5485 | in that case pretty much any characters can be read. | |
a0d0e21e LW |
5486 | |
5487 | =item readdir DIRHANDLE | |
d74e8afc | 5488 | X<readdir> |
a0d0e21e | 5489 | |
c17cdb72 NC |
5490 | =for Pod::Functions get a directory from a directory handle |
5491 | ||
19799a22 | 5492 | Returns the next directory entry for a directory opened by C<opendir>. |
5a964f20 | 5493 | If used in list context, returns all the rest of the entries in the |
3b10bc60 | 5494 | directory. If there are no more entries, returns the undefined value in |
5495 | scalar context and the empty list in list context. | |
a0d0e21e | 5496 | |
19799a22 | 5497 | If you're planning to filetest the return values out of a C<readdir>, you'd |
5f05dabc | 5498 | better prepend the directory in question. Otherwise, because we didn't |
19799a22 | 5499 | C<chdir> there, it would have been testing the wrong file. |
cb1a09d0 | 5500 | |
b0169937 GS |
5501 | opendir(my $dh, $some_dir) || die "can't opendir $some_dir: $!"; |
5502 | @dots = grep { /^\./ && -f "$some_dir/$_" } readdir($dh); | |
5503 | closedir $dh; | |
cb1a09d0 | 5504 | |
e9fa405d | 5505 | As of Perl 5.12 you can use a bare C<readdir> in a C<while> loop, |
114c60ec BG |
5506 | which will set C<$_> on every iteration. |
5507 | ||
5508 | opendir(my $dh, $some_dir) || die; | |
5509 | while(readdir $dh) { | |
5510 | print "$some_dir/$_\n"; | |
5511 | } | |
5512 | closedir $dh; | |
5513 | ||
bade7fbc TC |
5514 | To avoid confusing would-be users of your code who are running earlier |
5515 | versions of Perl with mysterious failures, put this sort of thing at the | |
5516 | top of your file to signal that your code will work I<only> on Perls of a | |
5517 | recent vintage: | |
5518 | ||
5519 | use 5.012; # so readdir assigns to $_ in a lone while test | |
5520 | ||
84902520 | 5521 | =item readline EXPR |
e4b7ebf3 RGS |
5522 | |
5523 | =item readline | |
d74e8afc | 5524 | X<readline> X<gets> X<fgets> |
84902520 | 5525 | |
c17cdb72 NC |
5526 | =for Pod::Functions fetch a record from a file |
5527 | ||
e4b7ebf3 | 5528 | Reads from the filehandle whose typeglob is contained in EXPR (or from |
8f1da26d | 5529 | C<*ARGV> if EXPR is not provided). In scalar context, each call reads and |
80d38338 | 5530 | returns the next line until end-of-file is reached, whereupon the |
0f03d336 | 5531 | subsequent call returns C<undef>. In list context, reads until end-of-file |
e4b7ebf3 | 5532 | is reached and returns a list of lines. Note that the notion of "line" |
80d38338 | 5533 | used here is whatever you may have defined with C<$/> or |
e4b7ebf3 | 5534 | C<$INPUT_RECORD_SEPARATOR>). See L<perlvar/"$/">. |
fbad3eb5 | 5535 | |
0f03d336 | 5536 | When C<$/> is set to C<undef>, when C<readline> is in scalar |
80d38338 | 5537 | context (i.e., file slurp mode), and when an empty file is read, it |
449bc448 | 5538 | returns C<''> the first time, followed by C<undef> subsequently. |
fbad3eb5 | 5539 | |
61eff3bc JH |
5540 | This is the internal function implementing the C<< <EXPR> >> |
5541 | operator, but you can use it directly. The C<< <EXPR> >> | |
84902520 TB |
5542 | operator is discussed in more detail in L<perlop/"I/O Operators">. |
5543 | ||
5a964f20 | 5544 | $line = <STDIN>; |
5ed4f2ec | 5545 | $line = readline(*STDIN); # same thing |
5a964f20 | 5546 | |
0f03d336 | 5547 | If C<readline> encounters an operating system error, C<$!> will be set |
5548 | with the corresponding error message. It can be helpful to check | |
5549 | C<$!> when you are reading from filehandles you don't trust, such as a | |
5550 | tty or a socket. The following example uses the operator form of | |
5551 | C<readline> and dies if the result is not defined. | |
5552 | ||
5ed4f2ec | 5553 | while ( ! eof($fh) ) { |
5554 | defined( $_ = <$fh> ) or die "readline failed: $!"; | |
5555 | ... | |
5556 | } | |
0f03d336 | 5557 | |
5558 | Note that you have can't handle C<readline> errors that way with the | |
391b733c | 5559 | C<ARGV> filehandle. In that case, you have to open each element of |
0f03d336 | 5560 | C<@ARGV> yourself since C<eof> handles C<ARGV> differently. |
5561 | ||
5562 | foreach my $arg (@ARGV) { | |
5563 | open(my $fh, $arg) or warn "Can't open $arg: $!"; | |
5564 | ||
5565 | while ( ! eof($fh) ) { | |
5566 | defined( $_ = <$fh> ) | |
5567 | or die "readline failed for $arg: $!"; | |
5568 | ... | |
00cb5da1 | 5569 | } |
00cb5da1 | 5570 | } |
e00e4ce9 | 5571 | |
a0d0e21e | 5572 | =item readlink EXPR |
d74e8afc | 5573 | X<readlink> |
a0d0e21e | 5574 | |
54310121 | 5575 | =item readlink |
bbce6d69 | 5576 | |
c17cdb72 NC |
5577 | =for Pod::Functions determine where a symbolic link is pointing |
5578 | ||
a0d0e21e | 5579 | Returns the value of a symbolic link, if symbolic links are |
3b10bc60 | 5580 | implemented. If not, raises an exception. If there is a system |
184e9718 | 5581 | error, returns the undefined value and sets C<$!> (errno). If EXPR is |
7660c0ab | 5582 | omitted, uses C<$_>. |
a0d0e21e | 5583 | |
ea9eb35a BJ |
5584 | Portability issues: L<perlport/readlink>. |
5585 | ||
84902520 | 5586 | =item readpipe EXPR |
8d7403e6 RGS |
5587 | |
5588 | =item readpipe | |
d74e8afc | 5589 | X<readpipe> |
84902520 | 5590 | |
c17cdb72 NC |
5591 | =for Pod::Functions execute a system command and collect standard output |
5592 | ||
5a964f20 | 5593 | EXPR is executed as a system command. |
84902520 TB |
5594 | The collected standard output of the command is returned. |
5595 | In scalar context, it comes back as a single (potentially | |
5596 | multi-line) string. In list context, returns a list of lines | |
7660c0ab | 5597 | (however you've defined lines with C<$/> or C<$INPUT_RECORD_SEPARATOR>). |
84902520 TB |
5598 | This is the internal function implementing the C<qx/EXPR/> |
5599 | operator, but you can use it directly. The C<qx/EXPR/> | |
5600 | operator is discussed in more detail in L<perlop/"I/O Operators">. | |
8d7403e6 | 5601 | If EXPR is omitted, uses C<$_>. |
84902520 | 5602 | |
399388f4 | 5603 | =item recv SOCKET,SCALAR,LENGTH,FLAGS |
d74e8afc | 5604 | X<recv> |
a0d0e21e | 5605 | |
c17cdb72 NC |
5606 | =for Pod::Functions receive a message over a Socket |
5607 | ||
9124316e JH |
5608 | Receives a message on a socket. Attempts to receive LENGTH characters |
5609 | of data into variable SCALAR from the specified SOCKET filehandle. | |
5610 | SCALAR will be grown or shrunk to the length actually read. Takes the | |
5611 | same flags as the system call of the same name. Returns the address | |
5612 | of the sender if SOCKET's protocol supports this; returns an empty | |
5613 | string otherwise. If there's an error, returns the undefined value. | |
5614 | This call is actually implemented in terms of recvfrom(2) system call. | |
5615 | See L<perlipc/"UDP: Message Passing"> for examples. | |
5616 | ||
5617 | Note the I<characters>: depending on the status of the socket, either | |
5618 | (8-bit) bytes or characters are received. By default all sockets | |
5619 | operate on bytes, but for example if the socket has been changed using | |
740d4bb2 | 5620 | binmode() to operate with the C<:encoding(utf8)> I/O layer (see the |
8f1da26d | 5621 | C<open> pragma, L<open>), the I/O will operate on UTF8-encoded Unicode |
740d4bb2 JW |
5622 | characters, not bytes. Similarly for the C<:encoding> pragma: in that |
5623 | case pretty much any characters can be read. | |
a0d0e21e LW |
5624 | |
5625 | =item redo LABEL | |
d74e8afc | 5626 | X<redo> |
a0d0e21e | 5627 | |
8a7e748e FC |
5628 | =item redo EXPR |
5629 | ||
a0d0e21e LW |
5630 | =item redo |
5631 | ||
c17cdb72 NC |
5632 | =for Pod::Functions start this loop iteration over again |
5633 | ||
a0d0e21e | 5634 | The C<redo> command restarts the loop block without evaluating the |
98293880 | 5635 | conditional again. The C<continue> block, if any, is not executed. If |
a0d0e21e | 5636 | the LABEL is omitted, the command refers to the innermost enclosing |
8a7e748e FC |
5637 | loop. The C<redo EXPR> form, available starting in Perl 5.18.0, allows a |
5638 | label name to be computed at run time, and is otherwise identical to C<redo | |
5639 | LABEL>. Programs that want to lie to themselves about what was just input | |
cf264981 | 5640 | normally use this command: |
a0d0e21e LW |
5641 | |
5642 | # a simpleminded Pascal comment stripper | |
5643 | # (warning: assumes no { or } in strings) | |
4633a7c4 | 5644 | LINE: while (<STDIN>) { |
a9a5a0dc VP |
5645 | while (s|({.*}.*){.*}|$1 |) {} |
5646 | s|{.*}| |; | |
5647 | if (s|{.*| |) { | |
5648 | $front = $_; | |
5649 | while (<STDIN>) { | |
5650 | if (/}/) { # end of comment? | |
5651 | s|^|$front\{|; | |
5652 | redo LINE; | |
5653 | } | |
5654 | } | |
5ed4f2ec | 5655 | } |
a9a5a0dc | 5656 | print; |
a0d0e21e LW |
5657 | } |
5658 | ||
80d38338 | 5659 | C<redo> cannot be used to retry a block that returns a value such as |
8f1da26d | 5660 | C<eval {}>, C<sub {}>, or C<do {}>, and should not be used to exit |
2b5ab1e7 | 5661 | a grep() or map() operation. |
4968c1e4 | 5662 | |
6c1372ed GS |
5663 | Note that a block by itself is semantically identical to a loop |
5664 | that executes once. Thus C<redo> inside such a block will effectively | |
5665 | turn it into a looping construct. | |
5666 | ||
98293880 | 5667 | See also L</continue> for an illustration of how C<last>, C<next>, and |
1d2dff63 GS |
5668 | C<redo> work. |
5669 | ||
2ba1f20a FC |
5670 | Unlike most named operators, this has the same precedence as assignment. |
5671 | It is also exempt from the looks-like-a-function rule, so | |
5672 | C<redo ("foo")."bar"> will cause "bar" to be part of the argument to | |
5673 | C<redo>. | |
5674 | ||
a0d0e21e | 5675 | =item ref EXPR |
d74e8afc | 5676 | X<ref> X<reference> |
a0d0e21e | 5677 | |
54310121 | 5678 | =item ref |
bbce6d69 | 5679 | |
c17cdb72 NC |
5680 | =for Pod::Functions find out the type of thing being referenced |
5681 | ||
8a2e0804 | 5682 | Returns a non-empty string if EXPR is a reference, the empty |
0373590a BB |
5683 | string otherwise. If EXPR is not specified, C<$_> will be used. The |
5684 | value returned depends on the type of thing the reference is a reference to. | |
5685 | ||
a0d0e21e LW |
5686 | Builtin types include: |
5687 | ||
a0d0e21e LW |
5688 | SCALAR |
5689 | ARRAY | |
5690 | HASH | |
5691 | CODE | |
19799a22 | 5692 | REF |
a0d0e21e | 5693 | GLOB |
19799a22 | 5694 | LVALUE |
cc10766d RGS |
5695 | FORMAT |
5696 | IO | |
5697 | VSTRING | |
5698 | Regexp | |
a0d0e21e | 5699 | |
0373590a | 5700 | You can think of C<ref> as a C<typeof> operator. |
a0d0e21e LW |
5701 | |
5702 | if (ref($r) eq "HASH") { | |
a9a5a0dc | 5703 | print "r is a reference to a hash.\n"; |
54310121 | 5704 | } |
2b5ab1e7 | 5705 | unless (ref($r)) { |
a9a5a0dc | 5706 | print "r is not a reference at all.\n"; |
54310121 | 5707 | } |
a0d0e21e | 5708 | |
85dd5c8b | 5709 | The return value C<LVALUE> indicates a reference to an lvalue that is not |
391b733c FC |
5710 | a variable. You get this from taking the reference of function calls like |
5711 | C<pos()> or C<substr()>. C<VSTRING> is returned if the reference points | |
603c58be | 5712 | to a L<version string|perldata/"Version Strings">. |
85dd5c8b WL |
5713 | |
5714 | The result C<Regexp> indicates that the argument is a regular expression | |
5715 | resulting from C<qr//>. | |
5716 | ||
0373590a BB |
5717 | If the referenced object has been blessed into a package, then that package |
5718 | name is returned instead. But don't use that, as it's now considered | |
5719 | "bad practice". For one reason, an object could be using a class called | |
5720 | C<Regexp> or C<IO>, or even C<HASH>. Also, C<ref> doesn't take into account | |
5721 | subclasses, like C<isa> does. | |
5722 | ||
24968583 TC |
5723 | Instead, use C<blessed> (in the L<Scalar::Util> module) for boolean |
5724 | checks, C<isa> for specific class checks and C<reftype> (also from | |
5725 | L<Scalar::Util>) for type checks. (See L<perlobj> for details and a | |
0373590a BB |
5726 | C<blessed/isa> example.) |
5727 | ||
a0d0e21e LW |
5728 | See also L<perlref>. |
5729 | ||
5730 | =item rename OLDNAME,NEWNAME | |
d74e8afc | 5731 | X<rename> X<move> X<mv> X<ren> |
a0d0e21e | 5732 | |
c17cdb72 NC |
5733 | =for Pod::Functions change a filename |
5734 | ||
19799a22 GS |
5735 | Changes the name of a file; an existing file NEWNAME will be |
5736 | clobbered. Returns true for success, false otherwise. | |
5737 | ||
2b5ab1e7 TC |
5738 | Behavior of this function varies wildly depending on your system |
5739 | implementation. For example, it will usually not work across file system | |
5740 | boundaries, even though the system I<mv> command sometimes compensates | |
5741 | for this. Other restrictions include whether it works on directories, | |
5742 | open files, or pre-existing files. Check L<perlport> and either the | |
5743 | rename(2) manpage or equivalent system documentation for details. | |
a0d0e21e | 5744 | |
dd184578 RGS |
5745 | For a platform independent C<move> function look at the L<File::Copy> |
5746 | module. | |
5747 | ||
ea9eb35a BJ |
5748 | Portability issues: L<perlport/rename>. |
5749 | ||
16070b82 | 5750 | =item require VERSION |
d74e8afc | 5751 | X<require> |
16070b82 | 5752 | |
a0d0e21e LW |
5753 | =item require EXPR |
5754 | ||
5755 | =item require | |
5756 | ||
c17cdb72 NC |
5757 | =for Pod::Functions load in external functions from a library at runtime |
5758 | ||
3b825e41 RK |
5759 | Demands a version of Perl specified by VERSION, or demands some semantics |
5760 | specified by EXPR or by C<$_> if EXPR is not supplied. | |
44dcb63b | 5761 | |
3b825e41 RK |
5762 | VERSION may be either a numeric argument such as 5.006, which will be |
5763 | compared to C<$]>, or a literal of the form v5.6.1, which will be compared | |
3b10bc60 | 5764 | to C<$^V> (aka $PERL_VERSION). An exception is raised if |
3b825e41 RK |
5765 | VERSION is greater than the version of the current Perl interpreter. |
5766 | Compare with L</use>, which can do a similar check at compile time. | |
5767 | ||
5768 | Specifying VERSION as a literal of the form v5.6.1 should generally be | |
5769 | avoided, because it leads to misleading error messages under earlier | |
cf264981 | 5770 | versions of Perl that do not support this syntax. The equivalent numeric |
3b825e41 | 5771 | version should be used instead. |
44dcb63b | 5772 | |
5ed4f2ec | 5773 | require v5.6.1; # run time version check |
5774 | require 5.6.1; # ditto | |
f7051f2c FC |
5775 | require 5.006_001; # ditto; preferred for backwards |
5776 | compatibility | |
a0d0e21e | 5777 | |
362eead3 RGS |
5778 | Otherwise, C<require> demands that a library file be included if it |
5779 | hasn't already been included. The file is included via the do-FILE | |
73c71df6 CW |
5780 | mechanism, which is essentially just a variety of C<eval> with the |
5781 | caveat that lexical variables in the invoking script will be invisible | |
bf8b9e96 DG |
5782 | to the included code. If it were implemented in pure Perl, it |
5783 | would have semantics similar to the following: | |
5784 | ||
5785 | use Carp 'croak'; | |
5786 | use version; | |
a0d0e21e LW |
5787 | |
5788 | sub require { | |
3b927101 DM |
5789 | my ($filename) = @_; |
5790 | if ( my $version = eval { version->parse($filename) } ) { | |
5791 | if ( $version > $^V ) { | |
e29828a5 FC |
5792 | my $vn = $version->normal; |
5793 | croak "Perl $vn required--this is only $^V, stopped"; | |
3b927101 DM |
5794 | } |
5795 | return 1; | |
5796 | } | |
5797 | ||
5798 | if (exists $INC{$filename}) { | |
5799 | return 1 if $INC{$filename}; | |
5800 | croak "Compilation failed in require"; | |
5801 | } | |
5802 | ||
5803 | foreach $prefix (@INC) { | |
5804 | if (ref($prefix)) { | |
5805 | #... do other stuff - see text below .... | |
5806 | } | |
5807 | # (see text below about possible appending of .pmc | |
5808 | # suffix to $filename) | |
5809 | my $realfilename = "$prefix/$filename"; | |
5810 | next if ! -e $realfilename || -d _ || -b _; | |
5811 | $INC{$filename} = $realfilename; | |
e29828a5 FC |
5812 | my $result = do($realfilename); |
5813 | # but run in caller's namespace | |
3b927101 DM |
5814 | |
5815 | if (!defined $result) { | |
5816 | $INC{$filename} = undef; | |
5817 | croak $@ ? "$@Compilation failed in require" | |
5818 | : "Can't locate $filename: $!\n"; | |
5819 | } | |
5820 | if (!$result) { | |
5821 | delete $INC{$filename}; | |
5822 | croak "$filename did not return true value"; | |
5823 | } | |
5824 | $! = 0; | |
5825 | return $result; | |
5826 | } | |
5827 | croak "Can't locate $filename in \@INC ..."; | |
a0d0e21e LW |
5828 | } |
5829 | ||
5830 | Note that the file will not be included twice under the same specified | |
a12755f0 SB |
5831 | name. |
5832 | ||
5833 | The file must return true as the last statement to indicate | |
a0d0e21e | 5834 | successful execution of any initialization code, so it's customary to |
19799a22 GS |
5835 | end such a file with C<1;> unless you're sure it'll return true |
5836 | otherwise. But it's better just to put the C<1;>, in case you add more | |
a0d0e21e LW |
5837 | statements. |
5838 | ||
54310121 | 5839 | If EXPR is a bareword, the require assumes a "F<.pm>" extension and |
da0045b7 | 5840 | replaces "F<::>" with "F</>" in the filename for you, |
54310121 | 5841 | to make it easy to load standard modules. This form of loading of |
a0d0e21e LW |
5842 | modules does not risk altering your namespace. |
5843 | ||
ee580363 GS |
5844 | In other words, if you try this: |
5845 | ||
5ed4f2ec | 5846 | require Foo::Bar; # a splendid bareword |
ee580363 | 5847 | |
b76cc8ba | 5848 | The require function will actually look for the "F<Foo/Bar.pm>" file in the |
7660c0ab | 5849 | directories specified in the C<@INC> array. |
ee580363 | 5850 | |
5a964f20 | 5851 | But if you try this: |
ee580363 GS |
5852 | |
5853 | $class = 'Foo::Bar'; | |
5ed4f2ec | 5854 | require $class; # $class is not a bareword |
5a964f20 | 5855 | #or |
5ed4f2ec | 5856 | require "Foo::Bar"; # not a bareword because of the "" |
ee580363 | 5857 | |
b76cc8ba | 5858 | The require function will look for the "F<Foo::Bar>" file in the @INC array and |
19799a22 | 5859 | will complain about not finding "F<Foo::Bar>" there. In this case you can do: |
ee580363 GS |
5860 | |
5861 | eval "require $class"; | |
5862 | ||
3b10bc60 | 5863 | Now that you understand how C<require> looks for files with a |
a91233bf RGS |
5864 | bareword argument, there is a little extra functionality going on behind |
5865 | the scenes. Before C<require> looks for a "F<.pm>" extension, it will | |
391b733c | 5866 | first look for a similar filename with a "F<.pmc>" extension. If this file |
a91233bf RGS |
5867 | is found, it will be loaded in place of any file ending in a "F<.pm>" |
5868 | extension. | |
662cc546 | 5869 | |
8f1da26d | 5870 | You can also insert hooks into the import facility by putting Perl code |
1c3d5054 | 5871 | directly into the @INC array. There are three forms of hooks: subroutine |
8f1da26d | 5872 | references, array references, and blessed objects. |
d54b56d5 RGS |
5873 | |
5874 | Subroutine references are the simplest case. When the inclusion system | |
5875 | walks through @INC and encounters a subroutine, this subroutine gets | |
3b10bc60 | 5876 | called with two parameters, the first a reference to itself, and the |
5877 | second the name of the file to be included (e.g., "F<Foo/Bar.pm>"). The | |
5e5128ba | 5878 | subroutine should return either nothing or else a list of up to four |
3b10bc60 | 5879 | values in the following order: |
1f0bdf18 NC |
5880 | |
5881 | =over | |
5882 | ||
5883 | =item 1 | |
5884 | ||
5e5128ba FC |
5885 | A reference to a scalar, containing any initial source code to prepend to |
5886 | the file or generator output. | |
1f0bdf18 | 5887 | |
cec0e1a7 | 5888 | =item 2 |
1f0bdf18 | 5889 | |
5e5128ba FC |
5890 | A filehandle, from which the file will be read. |
5891 | ||
5892 | =item 3 | |
5893 | ||
391b733c | 5894 | A reference to a subroutine. If there is no filehandle (previous item), |
60d352b3 | 5895 | then this subroutine is expected to generate one line of source code per |
8f1da26d TC |
5896 | call, writing the line into C<$_> and returning 1, then finally at end of |
5897 | file returning 0. If there is a filehandle, then the subroutine will be | |
b8921b3e | 5898 | called to act as a simple source filter, with the line as read in C<$_>. |
60d352b3 RGS |
5899 | Again, return 1 for each valid line, and 0 after all lines have been |
5900 | returned. | |
1f0bdf18 | 5901 | |
5e5128ba | 5902 | =item 4 |
1f0bdf18 | 5903 | |
391b733c | 5904 | Optional state for the subroutine. The state is passed in as C<$_[1]>. A |
1f0bdf18 NC |
5905 | reference to the subroutine itself is passed in as C<$_[0]>. |
5906 | ||
5907 | =back | |
5908 | ||
5909 | If an empty list, C<undef>, or nothing that matches the first 3 values above | |
3b10bc60 | 5910 | is returned, then C<require> looks at the remaining elements of @INC. |
5911 | Note that this filehandle must be a real filehandle (strictly a typeglob | |
8f1da26d TC |
5912 | or reference to a typeglob, whether blessed or unblessed); tied filehandles |
5913 | will be ignored and processing will stop there. | |
d54b56d5 RGS |
5914 | |
5915 | If the hook is an array reference, its first element must be a subroutine | |
5916 | reference. This subroutine is called as above, but the first parameter is | |
3b10bc60 | 5917 | the array reference. This lets you indirectly pass arguments to |
d54b56d5 RGS |
5918 | the subroutine. |
5919 | ||
5920 | In other words, you can write: | |
5921 | ||
5922 | push @INC, \&my_sub; | |
5923 | sub my_sub { | |
a9a5a0dc VP |
5924 | my ($coderef, $filename) = @_; # $coderef is \&my_sub |
5925 | ... | |
d54b56d5 RGS |
5926 | } |
5927 | ||
5928 | or: | |
5929 | ||
5930 | push @INC, [ \&my_sub, $x, $y, ... ]; | |
5931 | sub my_sub { | |
a9a5a0dc VP |
5932 | my ($arrayref, $filename) = @_; |
5933 | # Retrieve $x, $y, ... | |
5934 | my @parameters = @$arrayref[1..$#$arrayref]; | |
5935 | ... | |
d54b56d5 RGS |
5936 | } |
5937 | ||
cf264981 | 5938 | If the hook is an object, it must provide an INC method that will be |
d54b56d5 | 5939 | called as above, the first parameter being the object itself. (Note that |
92c6daad NC |
5940 | you must fully qualify the sub's name, as unqualified C<INC> is always forced |
5941 | into package C<main>.) Here is a typical code layout: | |
d54b56d5 RGS |
5942 | |
5943 | # In Foo.pm | |
5944 | package Foo; | |
5945 | sub new { ... } | |
5946 | sub Foo::INC { | |
a9a5a0dc VP |
5947 | my ($self, $filename) = @_; |
5948 | ... | |
d54b56d5 RGS |
5949 | } |
5950 | ||
5951 | # In the main program | |
797f796a | 5952 | push @INC, Foo->new(...); |
d54b56d5 | 5953 | |
3b10bc60 | 5954 | These hooks are also permitted to set the %INC entry |
391b733c | 5955 | corresponding to the files they have loaded. See L<perlvar/%INC>. |
9ae8cd5b | 5956 | |
ee580363 | 5957 | For a yet-more-powerful import facility, see L</use> and L<perlmod>. |
a0d0e21e LW |
5958 | |
5959 | =item reset EXPR | |
d74e8afc | 5960 | X<reset> |
a0d0e21e LW |
5961 | |
5962 | =item reset | |
5963 | ||
c17cdb72 NC |
5964 | =for Pod::Functions clear all variables of a given name |
5965 | ||
a0d0e21e | 5966 | Generally used in a C<continue> block at the end of a loop to clear |
7660c0ab | 5967 | variables and reset C<??> searches so that they work again. The |
a0d0e21e LW |
5968 | expression is interpreted as a list of single characters (hyphens |
5969 | allowed for ranges). All variables and arrays beginning with one of | |
5970 | those letters are reset to their pristine state. If the expression is | |
3b10bc60 | 5971 | omitted, one-match searches (C<?pattern?>) are reset to match again. |
5972 | Only resets variables or searches in the current package. Always returns | |
5973 | 1. Examples: | |
a0d0e21e | 5974 | |
5ed4f2ec | 5975 | reset 'X'; # reset all X variables |
5976 | reset 'a-z'; # reset lower case variables | |
5977 | reset; # just reset ?one-time? searches | |
a0d0e21e | 5978 | |
7660c0ab | 5979 | Resetting C<"A-Z"> is not recommended because you'll wipe out your |
2b5ab1e7 | 5980 | C<@ARGV> and C<@INC> arrays and your C<%ENV> hash. Resets only package |
3b10bc60 | 5981 | variables; lexical variables are unaffected, but they clean themselves |
2b5ab1e7 TC |
5982 | up on scope exit anyway, so you'll probably want to use them instead. |
5983 | See L</my>. | |
a0d0e21e | 5984 | |
54310121 | 5985 | =item return EXPR |
d74e8afc | 5986 | X<return> |
54310121 | 5987 | |
5988 | =item return | |
5989 | ||
c17cdb72 NC |
5990 | =for Pod::Functions get out of a function early |
5991 | ||
b76cc8ba | 5992 | Returns from a subroutine, C<eval>, or C<do FILE> with the value |
5a964f20 | 5993 | given in EXPR. Evaluation of EXPR may be in list, scalar, or void |
54310121 | 5994 | context, depending on how the return value will be used, and the context |
01aa884e | 5995 | may vary from one execution to the next (see L</wantarray>). If no EXPR |
2b5ab1e7 | 5996 | is given, returns an empty list in list context, the undefined value in |
3b10bc60 | 5997 | scalar context, and (of course) nothing at all in void context. |
a0d0e21e | 5998 | |
3b10bc60 | 5999 | (In the absence of an explicit C<return>, a subroutine, eval, |
6000 | or do FILE automatically returns the value of the last expression | |
2b5ab1e7 | 6001 | evaluated.) |
a0d0e21e | 6002 | |
85897674 EB |
6003 | Unlike most named operators, this is also exempt from the |
6004 | looks-like-a-function rule, so C<return ("foo")."bar"> will | |
6005 | cause "bar" to be part of the argument to C<return>. | |
6006 | ||
a0d0e21e | 6007 | =item reverse LIST |
d74e8afc | 6008 | X<reverse> X<rev> X<invert> |
a0d0e21e | 6009 | |
c17cdb72 NC |
6010 | =for Pod::Functions flip a string or a list |
6011 | ||
5a964f20 TC |
6012 | In list context, returns a list value consisting of the elements |
6013 | of LIST in the opposite order. In scalar context, concatenates the | |
2b5ab1e7 | 6014 | elements of LIST and returns a string value with all characters |
a0ed51b3 | 6015 | in the opposite order. |
4633a7c4 | 6016 | |
9649ed94 | 6017 | print join(", ", reverse "world", "Hello"); # Hello, world |
4633a7c4 | 6018 | |
9649ed94 | 6019 | print scalar reverse "dlrow ,", "olleH"; # Hello, world |
2f9daede | 6020 | |
2d713cbd RGS |
6021 | Used without arguments in scalar context, reverse() reverses C<$_>. |
6022 | ||
9649ed94 | 6023 | $_ = "dlrow ,olleH"; |
f7051f2c FC |
6024 | print reverse; # No output, list context |
6025 | print scalar reverse; # Hello, world | |
9649ed94 | 6026 | |
437d4214 | 6027 | Note that reversing an array to itself (as in C<@a = reverse @a>) will |
e1f15c13 FC |
6028 | preserve non-existent elements whenever possible; i.e., for non-magical |
6029 | arrays or for tied arrays with C<EXISTS> and C<DELETE> methods. | |
437d4214 | 6030 | |
2f9daede TP |
6031 | This operator is also handy for inverting a hash, although there are some |
6032 | caveats. If a value is duplicated in the original hash, only one of those | |
6033 | can be represented as a key in the inverted hash. Also, this has to | |
6034 | unwind one hash and build a whole new one, which may take some time | |
2b5ab1e7 | 6035 | on a large hash, such as from a DBM file. |
2f9daede | 6036 | |
5ed4f2ec | 6037 | %by_name = reverse %by_address; # Invert the hash |
a0d0e21e LW |
6038 | |
6039 | =item rewinddir DIRHANDLE | |
d74e8afc | 6040 | X<rewinddir> |
a0d0e21e | 6041 | |
c17cdb72 NC |
6042 | =for Pod::Functions reset directory handle |
6043 | ||
a0d0e21e | 6044 | Sets the current position to the beginning of the directory for the |
19799a22 | 6045 | C<readdir> routine on DIRHANDLE. |
a0d0e21e | 6046 | |
ea9eb35a BJ |
6047 | Portability issues: L<perlport/rewinddir>. |
6048 | ||
a0d0e21e | 6049 | =item rindex STR,SUBSTR,POSITION |
d74e8afc | 6050 | X<rindex> |
a0d0e21e LW |
6051 | |
6052 | =item rindex STR,SUBSTR | |
6053 | ||
c17cdb72 NC |
6054 | =for Pod::Functions right-to-left substring search |
6055 | ||
ff551661 | 6056 | Works just like index() except that it returns the position of the I<last> |
a0d0e21e | 6057 | occurrence of SUBSTR in STR. If POSITION is specified, returns the |
ff551661 | 6058 | last occurrence beginning at or before that position. |
a0d0e21e LW |
6059 | |
6060 | =item rmdir FILENAME | |
d74e8afc | 6061 | X<rmdir> X<rd> X<directory, remove> |
a0d0e21e | 6062 | |
54310121 | 6063 | =item rmdir |
bbce6d69 | 6064 | |
c17cdb72 NC |
6065 | =for Pod::Functions remove a directory |
6066 | ||
974da8e5 | 6067 | Deletes the directory specified by FILENAME if that directory is |
8f1da26d | 6068 | empty. If it succeeds it returns true; otherwise it returns false and |
974da8e5 | 6069 | sets C<$!> (errno). If FILENAME is omitted, uses C<$_>. |
a0d0e21e | 6070 | |
e1020413 | 6071 | To remove a directory tree recursively (C<rm -rf> on Unix) look at |
dd184578 RGS |
6072 | the C<rmtree> function of the L<File::Path> module. |
6073 | ||
a0d0e21e LW |
6074 | =item s/// |
6075 | ||
c17cdb72 NC |
6076 | =for Pod::Functions replace a pattern with a string |
6077 | ||
9f4b9cd0 | 6078 | The substitution operator. See L<perlop/"Regexp Quote-Like Operators">. |
a0d0e21e | 6079 | |
0d863452 RH |
6080 | =item say FILEHANDLE LIST |
6081 | X<say> | |
6082 | ||
dee33c94 TC |
6083 | =item say FILEHANDLE |
6084 | ||
0d863452 RH |
6085 | =item say LIST |
6086 | ||
6087 | =item say | |
6088 | ||
d9b04284 | 6089 | =for Pod::Functions +say output a list to a filehandle, appending a newline |
c17cdb72 | 6090 | |
dee33c94 TC |
6091 | Just like C<print>, but implicitly appends a newline. C<say LIST> is |
6092 | simply an abbreviation for C<{ local $\ = "\n"; print LIST }>. To use | |
6093 | FILEHANDLE without a LIST to print the contents of C<$_> to it, you must | |
6094 | use a real filehandle like C<FH>, not an indirect one like C<$fh>. | |
f406c1e8 | 6095 | |
4a904372 FC |
6096 | This keyword is available only when the C<"say"> feature |
6097 | is enabled, or when prefixed with C<CORE::>; see | |
8f1da26d TC |
6098 | L<feature>. Alternately, include a C<use v5.10> or later to the current |
6099 | scope. | |
0d863452 | 6100 | |
a0d0e21e | 6101 | =item scalar EXPR |
d74e8afc | 6102 | X<scalar> X<context> |
a0d0e21e | 6103 | |
c17cdb72 NC |
6104 | =for Pod::Functions force a scalar context |
6105 | ||
5a964f20 | 6106 | Forces EXPR to be interpreted in scalar context and returns the value |
54310121 | 6107 | of EXPR. |
cb1a09d0 AD |
6108 | |
6109 | @counts = ( scalar @a, scalar @b, scalar @c ); | |
6110 | ||
54310121 | 6111 | There is no equivalent operator to force an expression to |
2b5ab1e7 | 6112 | be interpolated in list context because in practice, this is never |
cb1a09d0 AD |
6113 | needed. If you really wanted to do so, however, you could use |
6114 | the construction C<@{[ (some expression) ]}>, but usually a simple | |
6115 | C<(some expression)> suffices. | |
a0d0e21e | 6116 | |
8f1da26d TC |
6117 | Because C<scalar> is a unary operator, if you accidentally use a |
6118 | parenthesized list for the EXPR, this behaves as a scalar comma expression, | |
6119 | evaluating all but the last element in void context and returning the final | |
6120 | element evaluated in scalar context. This is seldom what you want. | |
62c18ce2 GS |
6121 | |
6122 | The following single statement: | |
6123 | ||
5ed4f2ec | 6124 | print uc(scalar(&foo,$bar)),$baz; |
62c18ce2 GS |
6125 | |
6126 | is the moral equivalent of these two: | |
6127 | ||
5ed4f2ec | 6128 | &foo; |
6129 | print(uc($bar),$baz); | |
62c18ce2 GS |
6130 | |
6131 | See L<perlop> for more details on unary operators and the comma operator. | |
6132 | ||
a0d0e21e | 6133 | =item seek FILEHANDLE,POSITION,WHENCE |
d74e8afc | 6134 | X<seek> X<fseek> X<filehandle, position> |
a0d0e21e | 6135 | |
c17cdb72 NC |
6136 | =for Pod::Functions reposition file pointer for random-access I/O |
6137 | ||
19799a22 | 6138 | Sets FILEHANDLE's position, just like the C<fseek> call of C<stdio>. |
8903cb82 | 6139 | FILEHANDLE may be an expression whose value gives the name of the |
9124316e | 6140 | filehandle. The values for WHENCE are C<0> to set the new position |
8f1da26d TC |
6141 | I<in bytes> to POSITION; C<1> to set it to the current position plus |
6142 | POSITION; and C<2> to set it to EOF plus POSITION, typically | |
6143 | negative. For WHENCE you may use the constants C<SEEK_SET>, | |
9124316e | 6144 | C<SEEK_CUR>, and C<SEEK_END> (start of the file, current position, end |
8f1da26d | 6145 | of the file) from the L<Fcntl> module. Returns C<1> on success, false |
9124316e JH |
6146 | otherwise. |
6147 | ||
6148 | Note the I<in bytes>: even if the filehandle has been set to | |
740d4bb2 | 6149 | operate on characters (for example by using the C<:encoding(utf8)> open |
fae2c0fb | 6150 | layer), tell() will return byte offsets, not character offsets |
9124316e | 6151 | (because implementing that would render seek() and tell() rather slow). |
8903cb82 | 6152 | |
3b10bc60 | 6153 | If you want to position the file for C<sysread> or C<syswrite>, don't use |
6154 | C<seek>, because buffering makes its effect on the file's read-write position | |
19799a22 | 6155 | unpredictable and non-portable. Use C<sysseek> instead. |
a0d0e21e | 6156 | |
2b5ab1e7 TC |
6157 | Due to the rules and rigors of ANSI C, on some systems you have to do a |
6158 | seek whenever you switch between reading and writing. Amongst other | |
6159 | things, this may have the effect of calling stdio's clearerr(3). | |
6160 | A WHENCE of C<1> (C<SEEK_CUR>) is useful for not moving the file position: | |
cb1a09d0 AD |
6161 | |
6162 | seek(TEST,0,1); | |
6163 | ||
6164 | This is also useful for applications emulating C<tail -f>. Once you hit | |
3b10bc60 | 6165 | EOF on your read and then sleep for a while, you (probably) have to stick in a |
6166 | dummy seek() to reset things. The C<seek> doesn't change the position, | |
8903cb82 | 6167 | but it I<does> clear the end-of-file condition on the handle, so that the |
3b10bc60 | 6168 | next C<< <FILE> >> makes Perl try again to read something. (We hope.) |
cb1a09d0 | 6169 | |
3b10bc60 | 6170 | If that doesn't work (some I/O implementations are particularly |
6171 | cantankerous), you might need something like this: | |
cb1a09d0 AD |
6172 | |
6173 | for (;;) { | |
a9a5a0dc | 6174 | for ($curpos = tell(FILE); $_ = <FILE>; |
f86cebdf | 6175 | $curpos = tell(FILE)) { |
a9a5a0dc VP |
6176 | # search for some stuff and put it into files |
6177 | } | |
6178 | sleep($for_a_while); | |
6179 | seek(FILE, $curpos, 0); | |
cb1a09d0 AD |
6180 | } |
6181 | ||
a0d0e21e | 6182 | =item seekdir DIRHANDLE,POS |
d74e8afc | 6183 | X<seekdir> |
a0d0e21e | 6184 | |
c17cdb72 NC |
6185 | =for Pod::Functions reposition directory pointer |
6186 | ||
19799a22 | 6187 | Sets the current position for the C<readdir> routine on DIRHANDLE. POS |
cf264981 SP |
6188 | must be a value returned by C<telldir>. C<seekdir> also has the same caveats |
6189 | about possible directory compaction as the corresponding system library | |
a0d0e21e LW |
6190 | routine. |
6191 | ||
6192 | =item select FILEHANDLE | |
d74e8afc | 6193 | X<select> X<filehandle, default> |
a0d0e21e LW |
6194 | |
6195 | =item select | |
6196 | ||
c17cdb72 NC |
6197 | =for Pod::Functions reset default output or do I/O multiplexing |
6198 | ||
b5dffda6 RGS |
6199 | Returns the currently selected filehandle. If FILEHANDLE is supplied, |
6200 | sets the new current default filehandle for output. This has two | |
8f1da26d | 6201 | effects: first, a C<write> or a C<print> without a filehandle |
a0d0e21e | 6202 | default to this FILEHANDLE. Second, references to variables related to |
8f1da26d TC |
6203 | output will refer to this output channel. |
6204 | ||
6205 | For example, to set the top-of-form format for more than one | |
6206 | output channel, you might do the following: | |
a0d0e21e LW |
6207 | |
6208 | select(REPORT1); | |
6209 | $^ = 'report1_top'; | |
6210 | select(REPORT2); | |
6211 | $^ = 'report2_top'; | |
6212 | ||
6213 | FILEHANDLE may be an expression whose value gives the name of the | |
6214 | actual filehandle. Thus: | |
6215 | ||
6216 | $oldfh = select(STDERR); $| = 1; select($oldfh); | |
6217 | ||
4633a7c4 LW |
6218 | Some programmers may prefer to think of filehandles as objects with |
6219 | methods, preferring to write the last example as: | |
a0d0e21e | 6220 | |
28757baa | 6221 | use IO::Handle; |
a0d0e21e LW |
6222 | STDERR->autoflush(1); |
6223 | ||
ea9eb35a BJ |
6224 | Portability issues: L<perlport/select>. |
6225 | ||
a0d0e21e | 6226 | =item select RBITS,WBITS,EBITS,TIMEOUT |
d74e8afc | 6227 | X<select> |
a0d0e21e | 6228 | |
3b10bc60 | 6229 | This calls the select(2) syscall with the bit masks specified, which |
19799a22 | 6230 | can be constructed using C<fileno> and C<vec>, along these lines: |
a0d0e21e LW |
6231 | |
6232 | $rin = $win = $ein = ''; | |
f0815dd4 TC |
6233 | vec($rin, fileno(STDIN), 1) = 1; |
6234 | vec($win, fileno(STDOUT), 1) = 1; | |
a0d0e21e LW |
6235 | $ein = $rin | $win; |
6236 | ||
3b10bc60 | 6237 | If you want to select on many filehandles, you may wish to write a |
6238 | subroutine like this: | |
a0d0e21e LW |
6239 | |
6240 | sub fhbits { | |
f0815dd4 TC |
6241 | my @fhlist = @_; |
6242 | my $bits = ""; | |
6243 | for my $fh (@fhlist) { | |
6244 | vec($bits, fileno($fh), 1) = 1; | |
a9a5a0dc | 6245 | } |
f0815dd4 | 6246 | return $bits; |
a0d0e21e | 6247 | } |
f0815dd4 | 6248 | $rin = fhbits(*STDIN, *TTY, *MYSOCK); |
a0d0e21e LW |
6249 | |
6250 | The usual idiom is: | |
6251 | ||
6252 | ($nfound,$timeleft) = | |
6253 | select($rout=$rin, $wout=$win, $eout=$ein, $timeout); | |
6254 | ||
54310121 | 6255 | or to block until something becomes ready just do this |
a0d0e21e LW |
6256 | |
6257 | $nfound = select($rout=$rin, $wout=$win, $eout=$ein, undef); | |
6258 | ||
19799a22 GS |
6259 | Most systems do not bother to return anything useful in $timeleft, so |
6260 | calling select() in scalar context just returns $nfound. | |
c07a80fd | 6261 | |
5f05dabc | 6262 | Any of the bit masks can also be undef. The timeout, if specified, is |
a0d0e21e | 6263 | in seconds, which may be fractional. Note: not all implementations are |
be119125 | 6264 | capable of returning the $timeleft. If not, they always return |
19799a22 | 6265 | $timeleft equal to the supplied $timeout. |
a0d0e21e | 6266 | |
ff68c719 | 6267 | You can effect a sleep of 250 milliseconds this way: |
a0d0e21e LW |
6268 | |
6269 | select(undef, undef, undef, 0.25); | |
6270 | ||
b09fc1d8 | 6271 | Note that whether C<select> gets restarted after signals (say, SIGALRM) |
8b0ac1d7 MHM |
6272 | is implementation-dependent. See also L<perlport> for notes on the |
6273 | portability of C<select>. | |
40454f26 | 6274 | |
f0815dd4 | 6275 | On error, C<select> behaves just like select(2): it returns |
4189264e | 6276 | -1 and sets C<$!>. |
353e5636 | 6277 | |
8f1da26d TC |
6278 | On some Unixes, select(2) may report a socket file descriptor as "ready for |
6279 | reading" even when no data is available, and thus any subsequent C<read> | |
391b733c FC |
6280 | would block. This can be avoided if you always use O_NONBLOCK on the |
6281 | socket. See select(2) and fcntl(2) for further details. | |
ec8ce15a | 6282 | |
f0815dd4 TC |
6283 | The standard C<IO::Select> module provides a user-friendlier interface |
6284 | to C<select>, mostly because it does all the bit-mask work for you. | |
6285 | ||
19799a22 | 6286 | B<WARNING>: One should not attempt to mix buffered I/O (like C<read> |
61eff3bc | 6287 | or <FH>) with C<select>, except as permitted by POSIX, and even |
19799a22 | 6288 | then only on POSIX systems. You have to use C<sysread> instead. |
a0d0e21e | 6289 | |
ea9eb35a BJ |
6290 | Portability issues: L<perlport/select>. |
6291 | ||
a0d0e21e | 6292 | =item semctl ID,SEMNUM,CMD,ARG |
d74e8afc | 6293 | X<semctl> |
a0d0e21e | 6294 | |
c17cdb72 NC |
6295 | =for Pod::Functions SysV semaphore control operations |
6296 | ||
3b10bc60 | 6297 | Calls the System V IPC function semctl(2). You'll probably have to say |
0ade1984 JH |
6298 | |
6299 | use IPC::SysV; | |
6300 | ||
6301 | first to get the correct constant definitions. If CMD is IPC_STAT or | |
cf264981 | 6302 | GETALL, then ARG must be a variable that will hold the returned |
e4038a1f MS |
6303 | semid_ds structure or semaphore value array. Returns like C<ioctl>: |
6304 | the undefined value for error, "C<0 but true>" for zero, or the actual | |
6305 | return value otherwise. The ARG must consist of a vector of native | |
106325ad | 6306 | short integers, which may be created with C<pack("s!",(0)x$nsem)>. |
4755096e GS |
6307 | See also L<perlipc/"SysV IPC">, C<IPC::SysV>, C<IPC::Semaphore> |
6308 | documentation. | |
a0d0e21e | 6309 | |
ea9eb35a BJ |
6310 | Portability issues: L<perlport/semctl>. |
6311 | ||
a0d0e21e | 6312 | =item semget KEY,NSEMS,FLAGS |
d74e8afc | 6313 | X<semget> |
a0d0e21e | 6314 | |
c17cdb72 NC |
6315 | =for Pod::Functions get set of SysV semaphores |
6316 | ||
3b10bc60 | 6317 | Calls the System V IPC function semget(2). Returns the semaphore id, or |
8f1da26d | 6318 | the undefined value on error. See also |
4755096e GS |
6319 | L<perlipc/"SysV IPC">, C<IPC::SysV>, C<IPC::SysV::Semaphore> |
6320 | documentation. | |
a0d0e21e | 6321 | |
ea9eb35a BJ |
6322 | Portability issues: L<perlport/semget>. |
6323 | ||
a0d0e21e | 6324 | =item semop KEY,OPSTRING |
d74e8afc | 6325 | X<semop> |
a0d0e21e | 6326 | |
c17cdb72 NC |
6327 | =for Pod::Functions SysV semaphore operations |
6328 | ||
80d38338 | 6329 | Calls the System V IPC function semop(2) for semaphore operations |
5354997a | 6330 | such as signalling and waiting. OPSTRING must be a packed array of |
a0d0e21e | 6331 | semop structures. Each semop structure can be generated with |
cf264981 SP |
6332 | C<pack("s!3", $semnum, $semop, $semflag)>. The length of OPSTRING |
6333 | implies the number of semaphore operations. Returns true if | |
8f1da26d | 6334 | successful, false on error. As an example, the |
19799a22 | 6335 | following code waits on semaphore $semnum of semaphore id $semid: |
a0d0e21e | 6336 | |
f878ba33 | 6337 | $semop = pack("s!3", $semnum, -1, 0); |
a0d0e21e LW |
6338 | die "Semaphore trouble: $!\n" unless semop($semid, $semop); |
6339 | ||
4755096e GS |
6340 | To signal the semaphore, replace C<-1> with C<1>. See also |
6341 | L<perlipc/"SysV IPC">, C<IPC::SysV>, and C<IPC::SysV::Semaphore> | |
6342 | documentation. | |
a0d0e21e | 6343 | |
ea9eb35a BJ |
6344 | Portability issues: L<perlport/semop>. |
6345 | ||
a0d0e21e | 6346 | =item send SOCKET,MSG,FLAGS,TO |
d74e8afc | 6347 | X<send> |
a0d0e21e LW |
6348 | |
6349 | =item send SOCKET,MSG,FLAGS | |
6350 | ||
c17cdb72 NC |
6351 | =for Pod::Functions send a message over a socket |
6352 | ||
3b10bc60 | 6353 | Sends a message on a socket. Attempts to send the scalar MSG to the SOCKET |
6354 | filehandle. Takes the same flags as the system call of the same name. On | |
6355 | unconnected sockets, you must specify a destination to I<send to>, in which | |
6356 | case it does a sendto(2) syscall. Returns the number of characters sent, | |
6357 | or the undefined value on error. The sendmsg(2) syscall is currently | |
6358 | unimplemented. See L<perlipc/"UDP: Message Passing"> for examples. | |
9124316e JH |
6359 | |
6360 | Note the I<characters>: depending on the status of the socket, either | |
6361 | (8-bit) bytes or characters are sent. By default all sockets operate | |
6362 | on bytes, but for example if the socket has been changed using | |
740d4bb2 JW |
6363 | binmode() to operate with the C<:encoding(utf8)> I/O layer (see |
6364 | L</open>, or the C<open> pragma, L<open>), the I/O will operate on UTF-8 | |
6365 | encoded Unicode characters, not bytes. Similarly for the C<:encoding> | |
6366 | pragma: in that case pretty much any characters can be sent. | |
a0d0e21e LW |
6367 | |
6368 | =item setpgrp PID,PGRP | |
d74e8afc | 6369 | X<setpgrp> X<group> |
a0d0e21e | 6370 | |
c17cdb72 NC |
6371 | =for Pod::Functions set the process group of a process |
6372 | ||
7660c0ab | 6373 | Sets the current process group for the specified PID, C<0> for the current |
3b10bc60 | 6374 | process. Raises an exception when used on a machine that doesn't |
81777298 GS |
6375 | implement POSIX setpgid(2) or BSD setpgrp(2). If the arguments are omitted, |
6376 | it defaults to C<0,0>. Note that the BSD 4.2 version of C<setpgrp> does not | |
6377 | accept any arguments, so only C<setpgrp(0,0)> is portable. See also | |
6378 | C<POSIX::setsid()>. | |
a0d0e21e | 6379 | |
ea9eb35a BJ |
6380 | Portability issues: L<perlport/setpgrp>. |
6381 | ||
a0d0e21e | 6382 | =item setpriority WHICH,WHO,PRIORITY |
d74e8afc | 6383 | X<setpriority> X<priority> X<nice> X<renice> |
a0d0e21e | 6384 | |
c17cdb72 NC |
6385 | =for Pod::Functions set a process's nice value |
6386 | ||
a0d0e21e | 6387 | Sets the current priority for a process, a process group, or a user. |
3b10bc60 | 6388 | (See setpriority(2).) Raises an exception when used on a machine |
f86cebdf | 6389 | that doesn't implement setpriority(2). |
a0d0e21e | 6390 | |
ea9eb35a BJ |
6391 | Portability issues: L<perlport/setpriority>. |
6392 | ||
a0d0e21e | 6393 | =item setsockopt SOCKET,LEVEL,OPTNAME,OPTVAL |
d74e8afc | 6394 | X<setsockopt> |
a0d0e21e | 6395 | |
c17cdb72 NC |
6396 | =for Pod::Functions set some socket options |
6397 | ||
8f1da26d TC |
6398 | Sets the socket option requested. Returns C<undef> on error. |
6399 | Use integer constants provided by the C<Socket> module for | |
23d0437f GA |
6400 | LEVEL and OPNAME. Values for LEVEL can also be obtained from |
6401 | getprotobyname. OPTVAL might either be a packed string or an integer. | |
6402 | An integer OPTVAL is shorthand for pack("i", OPTVAL). | |
6403 | ||
3b10bc60 | 6404 | An example disabling Nagle's algorithm on a socket: |
23d0437f GA |
6405 | |
6406 | use Socket qw(IPPROTO_TCP TCP_NODELAY); | |
6407 | setsockopt($socket, IPPROTO_TCP, TCP_NODELAY, 1); | |
a0d0e21e | 6408 | |
ea9eb35a BJ |
6409 | Portability issues: L<perlport/setsockopt>. |
6410 | ||
532eee96 | 6411 | =item shift ARRAY |
d74e8afc | 6412 | X<shift> |
a0d0e21e | 6413 | |
f5a93a43 TC |
6414 | =item shift EXPR |
6415 | ||
a0d0e21e LW |
6416 | =item shift |
6417 | ||
c17cdb72 NC |
6418 | =for Pod::Functions remove the first element of an array, and return it |
6419 | ||
a0d0e21e LW |
6420 | Shifts the first value of the array off and returns it, shortening the |
6421 | array by 1 and moving everything down. If there are no elements in the | |
6422 | array, returns the undefined value. If ARRAY is omitted, shifts the | |
7660c0ab | 6423 | C<@_> array within the lexical scope of subroutines and formats, and the |
80d38338 | 6424 | C<@ARGV> array outside a subroutine and also within the lexical scopes |
3c10abe3 | 6425 | established by the C<eval STRING>, C<BEGIN {}>, C<INIT {}>, C<CHECK {}>, |
8f1da26d | 6426 | C<UNITCHECK {}>, and C<END {}> constructs. |
4f25aa18 | 6427 | |
f5a93a43 TC |
6428 | Starting with Perl 5.14, C<shift> can take a scalar EXPR, which must hold a |
6429 | reference to an unblessed array. The argument will be dereferenced | |
6430 | automatically. This aspect of C<shift> is considered highly experimental. | |
6431 | The exact behaviour may change in a future version of Perl. | |
cba5a3b0 | 6432 | |
bade7fbc TC |
6433 | To avoid confusing would-be users of your code who are running earlier |
6434 | versions of Perl with mysterious syntax errors, put this sort of thing at | |
6435 | the top of your file to signal that your code will work I<only> on Perls of | |
6436 | a recent vintage: | |
6437 | ||
6438 | use 5.014; # so push/pop/etc work on scalars (experimental) | |
6439 | ||
a1b2c429 | 6440 | See also C<unshift>, C<push>, and C<pop>. C<shift> and C<unshift> do the |
19799a22 | 6441 | same thing to the left end of an array that C<pop> and C<push> do to the |
977336f5 | 6442 | right end. |
a0d0e21e LW |
6443 | |
6444 | =item shmctl ID,CMD,ARG | |
d74e8afc | 6445 | X<shmctl> |
a0d0e21e | 6446 | |
c17cdb72 NC |
6447 | =for Pod::Functions SysV shared memory operations |
6448 | ||
0ade1984 JH |
6449 | Calls the System V IPC function shmctl. You'll probably have to say |
6450 | ||
6451 | use IPC::SysV; | |
6452 | ||
7660c0ab | 6453 | first to get the correct constant definitions. If CMD is C<IPC_STAT>, |
cf264981 | 6454 | then ARG must be a variable that will hold the returned C<shmid_ds> |
8f1da26d TC |
6455 | structure. Returns like ioctl: C<undef> for error; "C<0> but |
6456 | true" for zero; and the actual return value otherwise. | |
4755096e | 6457 | See also L<perlipc/"SysV IPC"> and C<IPC::SysV> documentation. |
a0d0e21e | 6458 | |
ea9eb35a BJ |
6459 | Portability issues: L<perlport/shmctl>. |
6460 | ||
a0d0e21e | 6461 | =item shmget KEY,SIZE,FLAGS |
d74e8afc | 6462 | X<shmget> |
a0d0e21e | 6463 | |
c17cdb72 NC |
6464 | =for Pod::Functions get SysV shared memory segment identifier |
6465 | ||
a0d0e21e | 6466 | Calls the System V IPC function shmget. Returns the shared memory |
8f1da26d | 6467 | segment id, or C<undef> on error. |
4755096e | 6468 | See also L<perlipc/"SysV IPC"> and C<IPC::SysV> documentation. |
a0d0e21e | 6469 | |
ea9eb35a BJ |
6470 | Portability issues: L<perlport/shmget>. |
6471 | ||
a0d0e21e | 6472 | =item shmread ID,VAR,POS,SIZE |
d74e8afc ITB |
6473 | X<shmread> |
6474 | X<shmwrite> | |
a0d0e21e | 6475 | |
c17cdb72 NC |
6476 | =for Pod::Functions read SysV shared memory |
6477 | ||
a0d0e21e LW |
6478 | =item shmwrite ID,STRING,POS,SIZE |
6479 | ||
c17cdb72 NC |
6480 | =for Pod::Functions write SysV shared memory |
6481 | ||
a0d0e21e LW |
6482 | Reads or writes the System V shared memory segment ID starting at |
6483 | position POS for size SIZE by attaching to it, copying in/out, and | |
5a964f20 | 6484 | detaching from it. When reading, VAR must be a variable that will |
a0d0e21e LW |
6485 | hold the data read. When writing, if STRING is too long, only SIZE |
6486 | bytes are used; if STRING is too short, nulls are written to fill out | |
8f1da26d | 6487 | SIZE bytes. Return true if successful, false on error. |
391b733c | 6488 | shmread() taints the variable. See also L<perlipc/"SysV IPC">, |
8f1da26d | 6489 | C<IPC::SysV>, and the C<IPC::Shareable> module from CPAN. |
a0d0e21e | 6490 | |
ea9eb35a BJ |
6491 | Portability issues: L<perlport/shmread> and L<perlport/shmwrite>. |
6492 | ||
a0d0e21e | 6493 | =item shutdown SOCKET,HOW |
d74e8afc | 6494 | X<shutdown> |
a0d0e21e | 6495 | |
c17cdb72 NC |
6496 | =for Pod::Functions close down just half of a socket connection |
6497 | ||
a0d0e21e | 6498 | Shuts down a socket connection in the manner indicated by HOW, which |
3b10bc60 | 6499 | has the same interpretation as in the syscall of the same name. |
a0d0e21e | 6500 | |
f86cebdf GS |
6501 | shutdown(SOCKET, 0); # I/we have stopped reading data |
6502 | shutdown(SOCKET, 1); # I/we have stopped writing data | |
6503 | shutdown(SOCKET, 2); # I/we have stopped using this socket | |
5a964f20 TC |
6504 | |
6505 | This is useful with sockets when you want to tell the other | |
6506 | side you're done writing but not done reading, or vice versa. | |
b76cc8ba | 6507 | It's also a more insistent form of close because it also |
19799a22 | 6508 | disables the file descriptor in any forked copies in other |
5a964f20 TC |
6509 | processes. |
6510 | ||
3b10bc60 | 6511 | Returns C<1> for success; on error, returns C<undef> if |
f126b98b PF |
6512 | the first argument is not a valid filehandle, or returns C<0> and sets |
6513 | C<$!> for any other failure. | |
6514 | ||
a0d0e21e | 6515 | =item sin EXPR |
d74e8afc | 6516 | X<sin> X<sine> X<asin> X<arcsine> |
a0d0e21e | 6517 | |
54310121 | 6518 | =item sin |
bbce6d69 | 6519 | |
c17cdb72 NC |
6520 | =for Pod::Functions return the sine of a number |
6521 | ||
a0d0e21e | 6522 | Returns the sine of EXPR (expressed in radians). If EXPR is omitted, |
7660c0ab | 6523 | returns sine of C<$_>. |
a0d0e21e | 6524 | |
ca6e1c26 | 6525 | For the inverse sine operation, you may use the C<Math::Trig::asin> |
28757baa | 6526 | function, or use this relation: |
6527 | ||
6528 | sub asin { atan2($_[0], sqrt(1 - $_[0] * $_[0])) } | |
6529 | ||
a0d0e21e | 6530 | =item sleep EXPR |
d74e8afc | 6531 | X<sleep> X<pause> |
a0d0e21e LW |
6532 | |
6533 | =item sleep | |
6534 | ||
c17cdb72 NC |
6535 | =for Pod::Functions block for some number of seconds |
6536 | ||
80d38338 TC |
6537 | Causes the script to sleep for (integer) EXPR seconds, or forever if no |
6538 | argument is given. Returns the integer number of seconds actually slept. | |
b48653af | 6539 | |
7660c0ab | 6540 | May be interrupted if the process receives a signal such as C<SIGALRM>. |
b48653af MS |
6541 | |
6542 | eval { | |
6543 | local $SIG{ALARM} = sub { die "Alarm!\n" }; | |
6544 | sleep; | |
6545 | }; | |
6546 | die $@ unless $@ eq "Alarm!\n"; | |
6547 | ||
6548 | You probably cannot mix C<alarm> and C<sleep> calls, because C<sleep> | |
6549 | is often implemented using C<alarm>. | |
a0d0e21e LW |
6550 | |
6551 | On some older systems, it may sleep up to a full second less than what | |
6552 | you requested, depending on how it counts seconds. Most modern systems | |
5a964f20 TC |
6553 | always sleep the full amount. They may appear to sleep longer than that, |
6554 | however, because your process might not be scheduled right away in a | |
6555 | busy multitasking system. | |
a0d0e21e | 6556 | |
2bc69794 BS |
6557 | For delays of finer granularity than one second, the Time::HiRes module |
6558 | (from CPAN, and starting from Perl 5.8 part of the standard | |
6559 | distribution) provides usleep(). You may also use Perl's four-argument | |
6560 | version of select() leaving the first three arguments undefined, or you | |
6561 | might be able to use the C<syscall> interface to access setitimer(2) if | |
391b733c | 6562 | your system supports it. See L<perlfaq8> for details. |
cb1a09d0 | 6563 | |
b6e2112e | 6564 | See also the POSIX module's C<pause> function. |
5f05dabc | 6565 | |
a0d0e21e | 6566 | =item socket SOCKET,DOMAIN,TYPE,PROTOCOL |
d74e8afc | 6567 | X<socket> |
a0d0e21e | 6568 | |
c17cdb72 NC |
6569 | =for Pod::Functions create a socket |
6570 | ||
a0d0e21e | 6571 | Opens a socket of the specified kind and attaches it to filehandle |
19799a22 | 6572 | SOCKET. DOMAIN, TYPE, and PROTOCOL are specified the same as for |
3b10bc60 | 6573 | the syscall of the same name. You should C<use Socket> first |
19799a22 GS |
6574 | to get the proper definitions imported. See the examples in |
6575 | L<perlipc/"Sockets: Client/Server Communication">. | |
a0d0e21e | 6576 | |
8d2a6795 GS |
6577 | On systems that support a close-on-exec flag on files, the flag will |
6578 | be set for the newly opened file descriptor, as determined by the | |
6579 | value of $^F. See L<perlvar/$^F>. | |
6580 | ||
a0d0e21e | 6581 | =item socketpair SOCKET1,SOCKET2,DOMAIN,TYPE,PROTOCOL |
d74e8afc | 6582 | X<socketpair> |
a0d0e21e | 6583 | |
c17cdb72 NC |
6584 | =for Pod::Functions create a pair of sockets |
6585 | ||
a0d0e21e | 6586 | Creates an unnamed pair of sockets in the specified domain, of the |
5f05dabc | 6587 | specified type. DOMAIN, TYPE, and PROTOCOL are specified the same as |
3b10bc60 | 6588 | for the syscall of the same name. If unimplemented, raises an exception. |
6589 | Returns true if successful. | |
a0d0e21e | 6590 | |
8d2a6795 GS |
6591 | On systems that support a close-on-exec flag on files, the flag will |
6592 | be set for the newly opened file descriptors, as determined by the value | |
6593 | of $^F. See L<perlvar/$^F>. | |
6594 | ||
19799a22 | 6595 | Some systems defined C<pipe> in terms of C<socketpair>, in which a call |
5a964f20 TC |
6596 | to C<pipe(Rdr, Wtr)> is essentially: |
6597 | ||
6598 | use Socket; | |
6599 | socketpair(Rdr, Wtr, AF_UNIX, SOCK_STREAM, PF_UNSPEC); | |
6600 | shutdown(Rdr, 1); # no more writing for reader | |
6601 | shutdown(Wtr, 0); # no more reading for writer | |
6602 | ||
02fc2eee NC |
6603 | See L<perlipc> for an example of socketpair use. Perl 5.8 and later will |
6604 | emulate socketpair using IP sockets to localhost if your system implements | |
6605 | sockets but not socketpair. | |
5a964f20 | 6606 | |
ea9eb35a BJ |
6607 | Portability issues: L<perlport/socketpair>. |
6608 | ||
a0d0e21e | 6609 | =item sort SUBNAME LIST |
d74e8afc | 6610 | X<sort> X<qsort> X<quicksort> X<mergesort> |
a0d0e21e LW |
6611 | |
6612 | =item sort BLOCK LIST | |
6613 | ||
6614 | =item sort LIST | |
6615 | ||
c17cdb72 NC |
6616 | =for Pod::Functions sort a list of values |
6617 | ||
41d39f30 | 6618 | In list context, this sorts the LIST and returns the sorted list value. |
9fdc1d08 | 6619 | In scalar context, the behaviour of C<sort()> is undefined. |
41d39f30 A |
6620 | |
6621 | If SUBNAME or BLOCK is omitted, C<sort>s in standard string comparison | |
6622 | order. If SUBNAME is specified, it gives the name of a subroutine | |
6623 | that returns an integer less than, equal to, or greater than C<0>, | |
3b10bc60 | 6624 | depending on how the elements of the list are to be ordered. (The |
6625 | C<< <=> >> and C<cmp> operators are extremely useful in such routines.) | |
41d39f30 A |
6626 | SUBNAME may be a scalar variable name (unsubscripted), in which case |
6627 | the value provides the name of (or a reference to) the actual | |
6628 | subroutine to use. In place of a SUBNAME, you can provide a BLOCK as | |
6629 | an anonymous, in-line sort subroutine. | |
a0d0e21e | 6630 | |
8f1da26d TC |
6631 | If the subroutine's prototype is C<($$)>, the elements to be compared are |
6632 | passed by reference in C<@_>, as for a normal subroutine. This is slower | |
6633 | than unprototyped subroutines, where the elements to be compared are passed | |
6634 | into the subroutine as the package global variables $a and $b (see example | |
6635 | below). Note that in the latter case, it is usually highly counter-productive | |
6636 | to declare $a and $b as lexicals. | |
43481408 | 6637 | |
51707595 FC |
6638 | If the subroutine is an XSUB, the elements to be compared are pushed on to |
6639 | the stack, the way arguments are usually passed to XSUBs. $a and $b are | |
6640 | not set. | |
6641 | ||
c106e8bb RH |
6642 | The values to be compared are always passed by reference and should not |
6643 | be modified. | |
a0d0e21e | 6644 | |
0a753a76 | 6645 | You also cannot exit out of the sort block or subroutine using any of the |
19799a22 | 6646 | loop control operators described in L<perlsyn> or with C<goto>. |
0a753a76 | 6647 | |
66cbab2c KW |
6648 | When C<use locale> (but not C<use locale 'not_characters'>) is in |
6649 | effect, C<sort LIST> sorts LIST according to the | |
a034a98d DD |
6650 | current collation locale. See L<perllocale>. |
6651 | ||
db5021a3 MS |
6652 | sort() returns aliases into the original list, much as a for loop's index |
6653 | variable aliases the list elements. That is, modifying an element of a | |
6654 | list returned by sort() (for example, in a C<foreach>, C<map> or C<grep>) | |
6655 | actually modifies the element in the original list. This is usually | |
6656 | something to be avoided when writing clear code. | |
6657 | ||
58c7fc7c | 6658 | Perl 5.6 and earlier used a quicksort algorithm to implement sort. |
8f1da26d | 6659 | That algorithm was not stable, so I<could> go quadratic. (A I<stable> sort |
58c7fc7c JH |
6660 | preserves the input order of elements that compare equal. Although |
6661 | quicksort's run time is O(NlogN) when averaged over all arrays of | |
6662 | length N, the time can be O(N**2), I<quadratic> behavior, for some | |
6663 | inputs.) In 5.7, the quicksort implementation was replaced with | |
cf264981 | 6664 | a stable mergesort algorithm whose worst-case behavior is O(NlogN). |
58c7fc7c JH |
6665 | But benchmarks indicated that for some inputs, on some platforms, |
6666 | the original quicksort was faster. 5.8 has a sort pragma for | |
6667 | limited control of the sort. Its rather blunt control of the | |
cf264981 | 6668 | underlying algorithm may not persist into future Perls, but the |
58c7fc7c | 6669 | ability to characterize the input or output in implementation |
c25fe68d | 6670 | independent ways quite probably will. See L<the sort pragma|sort>. |
c16425f1 | 6671 | |
a0d0e21e LW |
6672 | Examples: |
6673 | ||
6674 | # sort lexically | |
6675 | @articles = sort @files; | |
f703fc96 | 6676 | |
a0d0e21e LW |
6677 | # same thing, but with explicit sort routine |
6678 | @articles = sort {$a cmp $b} @files; | |
f703fc96 | 6679 | |
cb1a09d0 | 6680 | # now case-insensitively |
628253b8 | 6681 | @articles = sort {fc($a) cmp fc($b)} @files; |
f703fc96 | 6682 | |
a0d0e21e LW |
6683 | # same thing in reversed order |
6684 | @articles = sort {$b cmp $a} @files; | |
f703fc96 | 6685 | |
a0d0e21e LW |
6686 | # sort numerically ascending |
6687 | @articles = sort {$a <=> $b} @files; | |
f703fc96 | 6688 | |
a0d0e21e LW |
6689 | # sort numerically descending |
6690 | @articles = sort {$b <=> $a} @files; | |
f703fc96 | 6691 | |
19799a22 GS |
6692 | # this sorts the %age hash by value instead of key |
6693 | # using an in-line function | |
6694 | @eldest = sort { $age{$b} <=> $age{$a} } keys %age; | |
f703fc96 | 6695 | |
a0d0e21e LW |
6696 | # sort using explicit subroutine name |
6697 | sub byage { | |
4d0444a3 | 6698 | $age{$a} <=> $age{$b}; # presuming numeric |
a0d0e21e LW |
6699 | } |
6700 | @sortedclass = sort byage @class; | |
f703fc96 | 6701 | |
19799a22 GS |
6702 | sub backwards { $b cmp $a } |
6703 | @harry = qw(dog cat x Cain Abel); | |
6704 | @george = qw(gone chased yz Punished Axed); | |
a0d0e21e | 6705 | print sort @harry; |
e1d16ab7 | 6706 | # prints AbelCaincatdogx |
a0d0e21e | 6707 | print sort backwards @harry; |
e1d16ab7 | 6708 | # prints xdogcatCainAbel |
a0d0e21e | 6709 | print sort @george, 'to', @harry; |
e1d16ab7 | 6710 | # prints AbelAxedCainPunishedcatchaseddoggonetoxyz |
a0d0e21e | 6711 | |
54310121 | 6712 | # inefficiently sort by descending numeric compare using |
6713 | # the first integer after the first = sign, or the | |
cb1a09d0 AD |
6714 | # whole record case-insensitively otherwise |
6715 | ||
e1d16ab7 | 6716 | my @new = sort { |
6717 | ($b =~ /=(\d+)/)[0] <=> ($a =~ /=(\d+)/)[0] | |
4d0444a3 | 6718 | || |
628253b8 | 6719 | fc($a) cmp fc($b) |
cb1a09d0 AD |
6720 | } @old; |
6721 | ||
6722 | # same thing, but much more efficiently; | |
6723 | # we'll build auxiliary indices instead | |
6724 | # for speed | |
e1d16ab7 | 6725 | my @nums = @caps = (); |
54310121 | 6726 | for (@old) { |
e1d16ab7 | 6727 | push @nums, ( /=(\d+)/ ? $1 : undef ); |
628253b8 | 6728 | push @caps, fc($_); |
54310121 | 6729 | } |
cb1a09d0 | 6730 | |
e1d16ab7 | 6731 | my @new = @old[ sort { |
4d0444a3 FC |
6732 | $nums[$b] <=> $nums[$a] |
6733 | || | |
6734 | $caps[$a] cmp $caps[$b] | |
6735 | } 0..$#old | |
6736 | ]; | |
cb1a09d0 | 6737 | |
19799a22 | 6738 | # same thing, but without any temps |
cb1a09d0 | 6739 | @new = map { $_->[0] } |
19799a22 | 6740 | sort { $b->[1] <=> $a->[1] |
4d0444a3 FC |
6741 | || |
6742 | $a->[2] cmp $b->[2] | |
628253b8 | 6743 | } map { [$_, /=(\d+)/, fc($_)] } @old; |
61eff3bc | 6744 | |
43481408 GS |
6745 | # using a prototype allows you to use any comparison subroutine |
6746 | # as a sort subroutine (including other package's subroutines) | |
6747 | package other; | |
f7051f2c FC |
6748 | sub backwards ($$) { $_[1] cmp $_[0]; } # $a and $b are |
6749 | # not set here | |
43481408 GS |
6750 | package main; |
6751 | @new = sort other::backwards @old; | |
f703fc96 | 6752 | |
58c7fc7c JH |
6753 | # guarantee stability, regardless of algorithm |
6754 | use sort 'stable'; | |
6755 | @new = sort { substr($a, 3, 5) cmp substr($b, 3, 5) } @old; | |
f703fc96 | 6756 | |
268e9d79 JL |
6757 | # force use of mergesort (not portable outside Perl 5.8) |
6758 | use sort '_mergesort'; # note discouraging _ | |
58c7fc7c | 6759 | @new = sort { substr($a, 3, 5) cmp substr($b, 3, 5) } @old; |
58c7fc7c | 6760 | |
1cb246e8 | 6761 | Warning: syntactical care is required when sorting the list returned from |
391b733c | 6762 | a function. If you want to sort the list returned by the function call |
1cb246e8 | 6763 | C<find_records(@key)>, you can use: |
a9320c62 | 6764 | |
a9320c62 B |
6765 | @contact = sort { $a cmp $b } find_records @key; |
6766 | @contact = sort +find_records(@key); | |
6767 | @contact = sort &find_records(@key); | |
6768 | @contact = sort(find_records(@key)); | |
6769 | ||
6770 | If instead you want to sort the array @key with the comparison routine | |
1cb246e8 RGS |
6771 | C<find_records()> then you can use: |
6772 | ||
a9320c62 B |
6773 | @contact = sort { find_records() } @key; |
6774 | @contact = sort find_records(@key); | |
6775 | @contact = sort(find_records @key); | |
6776 | @contact = sort(find_records (@key)); | |
6777 | ||
19799a22 GS |
6778 | If you're using strict, you I<must not> declare $a |
6779 | and $b as lexicals. They are package globals. That means | |
1cb246e8 | 6780 | that if you're in the C<main> package and type |
13a2d996 | 6781 | |
47223a36 | 6782 | @articles = sort {$b <=> $a} @files; |
13a2d996 | 6783 | |
47223a36 JH |
6784 | then C<$a> and C<$b> are C<$main::a> and C<$main::b> (or C<$::a> and C<$::b>), |
6785 | but if you're in the C<FooPack> package, it's the same as typing | |
cb1a09d0 AD |
6786 | |
6787 | @articles = sort {$FooPack::b <=> $FooPack::a} @files; | |
6788 | ||
55497cff | 6789 | The comparison function is required to behave. If it returns |
7660c0ab A |
6790 | inconsistent results (sometimes saying C<$x[1]> is less than C<$x[2]> and |
6791 | sometimes saying the opposite, for example) the results are not | |
6792 | well-defined. | |
55497cff | 6793 | |
03190201 | 6794 | Because C<< <=> >> returns C<undef> when either operand is C<NaN> |
1bd4e8e3 | 6795 | (not-a-number), be careful when sorting with a |
8f1da26d TC |
6796 | comparison function like C<< $a <=> $b >> any lists that might contain a |
6797 | C<NaN>. The following example takes advantage that C<NaN != NaN> to | |
3b10bc60 | 6798 | eliminate any C<NaN>s from the input list. |
03190201 JL |
6799 | |
6800 | @result = sort { $a <=> $b } grep { $_ == $_ } @input; | |
6801 | ||
f5a93a43 | 6802 | =item splice ARRAY or EXPR,OFFSET,LENGTH,LIST |
d74e8afc | 6803 | X<splice> |
a0d0e21e | 6804 | |
f5a93a43 | 6805 | =item splice ARRAY or EXPR,OFFSET,LENGTH |
a0d0e21e | 6806 | |
f5a93a43 | 6807 | =item splice ARRAY or EXPR,OFFSET |
a0d0e21e | 6808 | |
f5a93a43 | 6809 | =item splice ARRAY or EXPR |
453f9044 | 6810 | |
c17cdb72 NC |
6811 | =for Pod::Functions add or remove elements anywhere in an array |
6812 | ||
a0d0e21e | 6813 | Removes the elements designated by OFFSET and LENGTH from an array, and |
5a964f20 TC |
6814 | replaces them with the elements of LIST, if any. In list context, |
6815 | returns the elements removed from the array. In scalar context, | |
43051805 | 6816 | returns the last element removed, or C<undef> if no elements are |
48cdf507 | 6817 | removed. The array grows or shrinks as necessary. |
19799a22 | 6818 | If OFFSET is negative then it starts that far from the end of the array. |
48cdf507 | 6819 | If LENGTH is omitted, removes everything from OFFSET onward. |
d0920e03 MJD |
6820 | If LENGTH is negative, removes the elements from OFFSET onward |
6821 | except for -LENGTH elements at the end of the array. | |
391b733c | 6822 | If both OFFSET and LENGTH are omitted, removes everything. If OFFSET is |
8e602cc9 EB |
6823 | past the end of the array and a LENGTH was provided, Perl issues a warning, |
6824 | and splices at the end of the array. | |
453f9044 | 6825 | |
e1dccc0d | 6826 | The following equivalences hold (assuming C<< $#a >= $i >> ) |
a0d0e21e | 6827 | |
5ed4f2ec | 6828 | push(@a,$x,$y) splice(@a,@a,0,$x,$y) |
6829 | pop(@a) splice(@a,-1) | |
6830 | shift(@a) splice(@a,0,1) | |
6831 | unshift(@a,$x,$y) splice(@a,0,0,$x,$y) | |
6832 | $a[$i] = $y splice(@a,$i,1,$y) | |
a0d0e21e | 6833 | |
498b759b RS |
6834 | C<splice> can be used, for example, to implement n-ary queue processing: |
6835 | ||
6836 | sub nary_print { | |
6837 | my $n = shift; | |
6838 | while (my @next_n = splice @_, 0, $n) { | |
6839 | say join q{ -- }, @next_n; | |
6840 | } | |
a0d0e21e | 6841 | } |
498b759b RS |
6842 | |
6843 | nary_print(3, qw(a b c d e f g h)); | |
6844 | # prints: | |
6845 | # a -- b -- c | |
6846 | # d -- e -- f | |
6847 | # g -- h | |
a0d0e21e | 6848 | |
f5a93a43 TC |
6849 | Starting with Perl 5.14, C<splice> can take scalar EXPR, which must hold a |
6850 | reference to an unblessed array. The argument will be dereferenced | |
6851 | automatically. This aspect of C<splice> is considered highly experimental. | |
6852 | The exact behaviour may change in a future version of Perl. | |
532eee96 | 6853 | |
bade7fbc TC |
6854 | To avoid confusing would-be users of your code who are running earlier |
6855 | versions of Perl with mysterious syntax errors, put this sort of thing at | |
6856 | the top of your file to signal that your code will work I<only> on Perls of | |
6857 | a recent vintage: | |
6858 | ||
6859 | use 5.014; # so push/pop/etc work on scalars (experimental) | |
6860 | ||
a0d0e21e | 6861 | =item split /PATTERN/,EXPR,LIMIT |
d74e8afc | 6862 | X<split> |
a0d0e21e LW |
6863 | |
6864 | =item split /PATTERN/,EXPR | |
6865 | ||
6866 | =item split /PATTERN/ | |
6867 | ||
6868 | =item split | |
6869 | ||
c17cdb72 NC |
6870 | =for Pod::Functions split up a string using a regexp delimiter |
6871 | ||
bd467585 MW |
6872 | Splits the string EXPR into a list of strings and returns the |
6873 | list in list context, or the size of the list in scalar context. | |
a0d0e21e | 6874 | |
bd467585 | 6875 | If only PATTERN is given, EXPR defaults to C<$_>. |
a0d0e21e | 6876 | |
bd467585 MW |
6877 | Anything in EXPR that matches PATTERN is taken to be a separator |
6878 | that separates the EXPR into substrings (called "I<fields>") that | |
6879 | do B<not> include the separator. Note that a separator may be | |
6880 | longer than one character or even have no characters at all (the | |
6881 | empty string, which is a zero-width match). | |
6882 | ||
6883 | The PATTERN need not be constant; an expression may be used | |
6884 | to specify a pattern that varies at runtime. | |
6885 | ||
6886 | If PATTERN matches the empty string, the EXPR is split at the match | |
6887 | position (between characters). As an example, the following: | |
6888 | ||
6889 | print join(':', split('b', 'abc')), "\n"; | |
6890 | ||
6891 | uses the 'b' in 'abc' as a separator to produce the output 'a:c'. | |
6892 | However, this: | |
6893 | ||
6894 | print join(':', split('', 'abc')), "\n"; | |
6895 | ||
6896 | uses empty string matches as separators to produce the output | |
6897 | 'a:b:c'; thus, the empty string may be used to split EXPR into a | |
6898 | list of its component characters. | |
6899 | ||
6900 | As a special case for C<split>, the empty pattern given in | |
6901 | L<match operator|perlop/"m/PATTERN/msixpodualgc"> syntax (C<//>) specifically matches the empty string, which is contrary to its usual | |
6902 | interpretation as the last successful match. | |
6903 | ||
6904 | If PATTERN is C</^/>, then it is treated as if it used the | |
6905 | L<multiline modifier|perlreref/OPERATORS> (C</^/m>), since it | |
6906 | isn't much use otherwise. | |
6907 | ||
6908 | As another special case, C<split> emulates the default behavior of the | |
6909 | command line tool B<awk> when the PATTERN is either omitted or a I<literal | |
6910 | string> composed of a single space character (such as S<C<' '>> or | |
6911 | S<C<"\x20">>, but not e.g. S<C</ />>). In this case, any leading | |
6912 | whitespace in EXPR is removed before splitting occurs, and the PATTERN is | |
6913 | instead treated as if it were C</\s+/>; in particular, this means that | |
6914 | I<any> contiguous whitespace (not just a single space character) is used as | |
6915 | a separator. However, this special treatment can be avoided by specifying | |
6916 | the pattern S<C</ />> instead of the string S<C<" ">>, thereby allowing | |
7161e5c2 | 6917 | only a single space character to be a separator. In earlier Perls this |
fdde5e9b YO |
6918 | special case was restricted to the use of a plain S<C<" ">> as the |
6919 | pattern argument to split, in Perl 5.18.0 and later this special case is | |
6920 | triggered by any expression which evaluates as the simple string S<C<" ">>. | |
bd467585 MW |
6921 | |
6922 | If omitted, PATTERN defaults to a single space, S<C<" ">>, triggering | |
6923 | the previously described I<awk> emulation. | |
fb73857a | 6924 | |
836e0ee7 | 6925 | If LIMIT is specified and positive, it represents the maximum number |
bd467585 MW |
6926 | of fields into which the EXPR may be split; in other words, LIMIT is |
6927 | one greater than the maximum number of times EXPR may be split. Thus, | |
6928 | the LIMIT value C<1> means that EXPR may be split a maximum of zero | |
6929 | times, producing a maximum of one field (namely, the entire value of | |
6930 | EXPR). For instance: | |
a0d0e21e | 6931 | |
bd467585 | 6932 | print join(':', split(//, 'abc', 1)), "\n"; |
a0d0e21e | 6933 | |
bd467585 | 6934 | produces the output 'abc', and this: |
a0d0e21e | 6935 | |
bd467585 | 6936 | print join(':', split(//, 'abc', 2)), "\n"; |
a0d0e21e | 6937 | |
bd467585 | 6938 | produces the output 'a:bc', and each of these: |
6de67870 | 6939 | |
bd467585 MW |
6940 | print join(':', split(//, 'abc', 3)), "\n"; |
6941 | print join(':', split(//, 'abc', 4)), "\n"; | |
52ea55c9 | 6942 | |
bd467585 | 6943 | produces the output 'a:b:c'. |
52ea55c9 | 6944 | |
bd467585 MW |
6945 | If LIMIT is negative, it is treated as if it were instead arbitrarily |
6946 | large; as many fields as possible are produced. | |
0156e0fd | 6947 | |
bd467585 MW |
6948 | If LIMIT is omitted (or, equivalently, zero), then it is usually |
6949 | treated as if it were instead negative but with the exception that | |
6950 | trailing empty fields are stripped (empty leading fields are always | |
6951 | preserved); if all fields are empty, then all fields are considered to | |
6952 | be trailing (and are thus stripped in this case). Thus, the following: | |
0156e0fd | 6953 | |
bd467585 | 6954 | print join(':', split(',', 'a,b,c,,,')), "\n"; |
12977212 | 6955 | |
bd467585 | 6956 | produces the output 'a:b:c', but the following: |
12977212 | 6957 | |
bd467585 | 6958 | print join(':', split(',', 'a,b,c,,,', -1)), "\n"; |
0156e0fd | 6959 | |
bd467585 | 6960 | produces the output 'a:b:c:::'. |
a0d0e21e | 6961 | |
bd467585 MW |
6962 | In time-critical applications, it is worthwhile to avoid splitting |
6963 | into more fields than necessary. Thus, when assigning to a list, | |
6964 | if LIMIT is omitted (or zero), then LIMIT is treated as though it | |
6965 | were one larger than the number of variables in the list; for the | |
e05ccd69 | 6966 | following, LIMIT is implicitly 3: |
a0d0e21e | 6967 | |
e05ccd69 | 6968 | ($login, $passwd) = split(/:/); |
a0d0e21e | 6969 | |
bd467585 MW |
6970 | Note that splitting an EXPR that evaluates to the empty string always |
6971 | produces zero fields, regardless of the LIMIT specified. | |
a0d0e21e | 6972 | |
bd467585 | 6973 | An empty leading field is produced when there is a positive-width |
0d3e3823 | 6974 | match at the beginning of EXPR. For instance: |
a0d0e21e | 6975 | |
bd467585 | 6976 | print join(':', split(/ /, ' abc')), "\n"; |
a0d0e21e | 6977 | |
bd467585 MW |
6978 | produces the output ':abc'. However, a zero-width match at the |
6979 | beginning of EXPR never produces an empty field, so that: | |
a0d0e21e | 6980 | |
bd467585 | 6981 | print join(':', split(//, ' abc')); |
4633a7c4 | 6982 | |
bd467585 | 6983 | produces the output S<' :a:b:c'> (rather than S<': :a:b:c'>). |
4633a7c4 | 6984 | |
bd467585 MW |
6985 | An empty trailing field, on the other hand, is produced when there is a |
6986 | match at the end of EXPR, regardless of the length of the match | |
6987 | (of course, unless a non-zero LIMIT is given explicitly, such fields are | |
0d3e3823 | 6988 | removed, as in the last example). Thus: |
748a9306 | 6989 | |
bd467585 | 6990 | print join(':', split(//, ' abc', -1)), "\n"; |
a0d0e21e | 6991 | |
bd467585 | 6992 | produces the output S<' :a:b:c:'>. |
1ec94568 | 6993 | |
bd467585 MW |
6994 | If the PATTERN contains |
6995 | L<capturing groups|perlretut/Grouping things and hierarchical matching>, | |
6996 | then for each separator, an additional field is produced for each substring | |
6997 | captured by a group (in the order in which the groups are specified, | |
6998 | as per L<backreferences|perlretut/Backreferences>); if any group does not | |
6999 | match, then it captures the C<undef> value instead of a substring. Also, | |
7000 | note that any such additional field is produced whenever there is a | |
7001 | separator (that is, whenever a split occurs), and such an additional field | |
7002 | does B<not> count towards the LIMIT. Consider the following expressions | |
7003 | evaluated in list context (each returned list is provided in the associated | |
7004 | comment): | |
a0d0e21e | 7005 | |
bd467585 MW |
7006 | split(/-|,/, "1-10,20", 3) |
7007 | # ('1', '10', '20') | |
7008 | ||
7009 | split(/(-|,)/, "1-10,20", 3) | |
7010 | # ('1', '-', '10', ',', '20') | |
7011 | ||
7012 | split(/-|(,)/, "1-10,20", 3) | |
7013 | # ('1', undef, '10', ',', '20') | |
a0d0e21e | 7014 | |
bd467585 MW |
7015 | split(/(-)|,/, "1-10,20", 3) |
7016 | # ('1', '-', '10', undef, '20') | |
6de67870 | 7017 | |
bd467585 MW |
7018 | split(/(-)|(,)/, "1-10,20", 3) |
7019 | # ('1', '-', undef, '10', undef, ',', '20') | |
a0d0e21e | 7020 | |
5f05dabc | 7021 | =item sprintf FORMAT, LIST |
d74e8afc | 7022 | X<sprintf> |
a0d0e21e | 7023 | |
c17cdb72 NC |
7024 | =for Pod::Functions formatted print into a string |
7025 | ||
6662521e GS |
7026 | Returns a string formatted by the usual C<printf> conventions of the C |
7027 | library function C<sprintf>. See below for more details | |
01aa884e | 7028 | and see L<sprintf(3)> or L<printf(3)> on your system for an explanation of |
6662521e GS |
7029 | the general principles. |
7030 | ||
7031 | For example: | |
7032 | ||
7033 | # Format number with up to 8 leading zeroes | |
7034 | $result = sprintf("%08d", $number); | |
7035 | ||
7036 | # Round number to 3 digits after decimal point | |
7037 | $rounded = sprintf("%.3f", $number); | |
74a77017 | 7038 | |
3b10bc60 | 7039 | Perl does its own C<sprintf> formatting: it emulates the C |
7040 | function sprintf(3), but doesn't use it except for floating-point | |
7041 | numbers, and even then only standard modifiers are allowed. | |
7042 | Non-standard extensions in your local sprintf(3) are | |
7043 | therefore unavailable from Perl. | |
74a77017 | 7044 | |
194e7b38 | 7045 | Unlike C<printf>, C<sprintf> does not do what you probably mean when you |
391b733c FC |
7046 | pass it an array as your first argument. |
7047 | The array is given scalar context, | |
194e7b38 DC |
7048 | and instead of using the 0th element of the array as the format, Perl will |
7049 | use the count of elements in the array as the format, which is almost never | |
7050 | useful. | |
7051 | ||
19799a22 | 7052 | Perl's C<sprintf> permits the following universally-known conversions: |
74a77017 | 7053 | |
5ed4f2ec | 7054 | %% a percent sign |
7055 | %c a character with the given number | |
7056 | %s a string | |
7057 | %d a signed integer, in decimal | |
7058 | %u an unsigned integer, in decimal | |
7059 | %o an unsigned integer, in octal | |
7060 | %x an unsigned integer, in hexadecimal | |
7061 | %e a floating-point number, in scientific notation | |
7062 | %f a floating-point number, in fixed decimal notation | |
7063 | %g a floating-point number, in %e or %f notation | |
74a77017 | 7064 | |
1b3f7d21 | 7065 | In addition, Perl permits the following widely-supported conversions: |
74a77017 | 7066 | |
5ed4f2ec | 7067 | %X like %x, but using upper-case letters |
7068 | %E like %e, but using an upper-case "E" | |
7069 | %G like %g, but with an upper-case "E" (if applicable) | |
7070 | %b an unsigned integer, in binary | |
7071 | %B like %b, but using an upper-case "B" with the # flag | |
7072 | %p a pointer (outputs the Perl value's address in hexadecimal) | |
7073 | %n special: *stores* the number of characters output so far | |
e3852384 | 7074 | into the next argument in the parameter list |
74a77017 | 7075 | |
1b3f7d21 CS |
7076 | Finally, for backward (and we do mean "backward") compatibility, Perl |
7077 | permits these unnecessary but widely-supported conversions: | |
74a77017 | 7078 | |
5ed4f2ec | 7079 | %i a synonym for %d |
7080 | %D a synonym for %ld | |
7081 | %U a synonym for %lu | |
7082 | %O a synonym for %lo | |
7083 | %F a synonym for %f | |
74a77017 | 7084 | |
7b8dd722 HS |
7085 | Note that the number of exponent digits in the scientific notation produced |
7086 | by C<%e>, C<%E>, C<%g> and C<%G> for numbers with the modulus of the | |
b73fd64e JH |
7087 | exponent less than 100 is system-dependent: it may be three or less |
7088 | (zero-padded as necessary). In other words, 1.23 times ten to the | |
7089 | 99th may be either "1.23e99" or "1.23e099". | |
d764f01a | 7090 | |
80d38338 | 7091 | Between the C<%> and the format letter, you may specify several |
7b8dd722 HS |
7092 | additional attributes controlling the interpretation of the format. |
7093 | In order, these are: | |
74a77017 | 7094 | |
7b8dd722 HS |
7095 | =over 4 |
7096 | ||
7097 | =item format parameter index | |
7098 | ||
391b733c | 7099 | An explicit format parameter index, such as C<2$>. By default sprintf |
7b8dd722 | 7100 | will format the next unused argument in the list, but this allows you |
3b10bc60 | 7101 | to take the arguments out of order: |
7b8dd722 HS |
7102 | |
7103 | printf '%2$d %1$d', 12, 34; # prints "34 12" | |
7104 | printf '%3$d %d %1$d', 1, 2, 3; # prints "3 1 1" | |
7105 | ||
7106 | =item flags | |
7107 | ||
7108 | one or more of: | |
e6bb52fd | 7109 | |
7a81c58e A |
7110 | space prefix non-negative number with a space |
7111 | + prefix non-negative number with a plus sign | |
74a77017 CS |
7112 | - left-justify within the field |
7113 | 0 use zeros, not spaces, to right-justify | |
e6bb52fd TS |
7114 | # ensure the leading "0" for any octal, |
7115 | prefix non-zero hexadecimal with "0x" or "0X", | |
7116 | prefix non-zero binary with "0b" or "0B" | |
7b8dd722 HS |
7117 | |
7118 | For example: | |
7119 | ||
e6bb52fd TS |
7120 | printf '<% d>', 12; # prints "< 12>" |
7121 | printf '<%+d>', 12; # prints "<+12>" | |
7122 | printf '<%6s>', 12; # prints "< 12>" | |
7123 | printf '<%-6s>', 12; # prints "<12 >" | |
7124 | printf '<%06s>', 12; # prints "<000012>" | |
7125 | printf '<%#o>', 12; # prints "<014>" | |
7126 | printf '<%#x>', 12; # prints "<0xc>" | |
7127 | printf '<%#X>', 12; # prints "<0XC>" | |
7128 | printf '<%#b>', 12; # prints "<0b1100>" | |
7129 | printf '<%#B>', 12; # prints "<0B1100>" | |
7b8dd722 | 7130 | |
9911cee9 TS |
7131 | When a space and a plus sign are given as the flags at once, |
7132 | a plus sign is used to prefix a positive number. | |
7133 | ||
7134 | printf '<%+ d>', 12; # prints "<+12>" | |
7135 | printf '<% +d>', 12; # prints "<+12>" | |
7136 | ||
e6bb52fd TS |
7137 | When the # flag and a precision are given in the %o conversion, |
7138 | the precision is incremented if it's necessary for the leading "0". | |
7139 | ||
7140 | printf '<%#.5o>', 012; # prints "<00012>" | |
7141 | printf '<%#.5o>', 012345; # prints "<012345>" | |
7142 | printf '<%#.0o>', 0; # prints "<0>" | |
7143 | ||
7b8dd722 HS |
7144 | =item vector flag |
7145 | ||
3b10bc60 | 7146 | This flag tells Perl to interpret the supplied string as a vector of |
391b733c | 7147 | integers, one for each character in the string. Perl applies the format to |
920f3fa9 | 7148 | each integer in turn, then joins the resulting strings with a separator (a |
391b733c | 7149 | dot C<.> by default). This can be useful for displaying ordinal values of |
920f3fa9 | 7150 | characters in arbitrary strings: |
7b8dd722 | 7151 | |
920f3fa9 | 7152 | printf "%vd", "AB\x{100}"; # prints "65.66.256" |
7b8dd722 HS |
7153 | printf "version is v%vd\n", $^V; # Perl's version |
7154 | ||
7155 | Put an asterisk C<*> before the C<v> to override the string to | |
7156 | use to separate the numbers: | |
7157 | ||
7158 | printf "address is %*vX\n", ":", $addr; # IPv6 address | |
7159 | printf "bits are %0*v8b\n", " ", $bits; # random bitstring | |
7160 | ||
7161 | You can also explicitly specify the argument number to use for | |
3b10bc60 | 7162 | the join string using something like C<*2$v>; for example: |
7b8dd722 | 7163 | |
f7051f2c FC |
7164 | printf '%*4$vX %*4$vX %*4$vX', # 3 IPv6 addresses |
7165 | @addr[1..3], ":"; | |
7b8dd722 HS |
7166 | |
7167 | =item (minimum) width | |
7168 | ||
7169 | Arguments are usually formatted to be only as wide as required to | |
391b733c | 7170 | display the given value. You can override the width by putting |
7b8dd722 | 7171 | a number here, or get the width from the next argument (with C<*>) |
3b10bc60 | 7172 | or from a specified argument (e.g., with C<*2$>): |
7b8dd722 | 7173 | |
f7051f2c FC |
7174 | printf "<%s>", "a"; # prints "<a>" |
7175 | printf "<%6s>", "a"; # prints "< a>" | |
7176 | printf "<%*s>", 6, "a"; # prints "< a>" | |
073d6857 | 7177 | printf '<%*2$s>', "a", 6; # prints "< a>" |
f7051f2c | 7178 | printf "<%2s>", "long"; # prints "<long>" (does not truncate) |
7b8dd722 | 7179 | |
19799a22 GS |
7180 | If a field width obtained through C<*> is negative, it has the same |
7181 | effect as the C<-> flag: left-justification. | |
74a77017 | 7182 | |
7b8dd722 | 7183 | =item precision, or maximum width |
d74e8afc | 7184 | X<precision> |
7b8dd722 | 7185 | |
6c8c9a8e | 7186 | You can specify a precision (for numeric conversions) or a maximum |
7b8dd722 | 7187 | width (for string conversions) by specifying a C<.> followed by a number. |
8f1da26d | 7188 | For floating-point formats except C<g> and C<G>, this specifies |
3b10bc60 | 7189 | how many places right of the decimal point to show (the default being 6). |
7190 | For example: | |
7b8dd722 HS |
7191 | |
7192 | # these examples are subject to system-specific variation | |
7193 | printf '<%f>', 1; # prints "<1.000000>" | |
7194 | printf '<%.1f>', 1; # prints "<1.0>" | |
7195 | printf '<%.0f>', 1; # prints "<1>" | |
7196 | printf '<%e>', 10; # prints "<1.000000e+01>" | |
7197 | printf '<%.1e>', 10; # prints "<1.0e+01>" | |
7198 | ||
3b10bc60 | 7199 | For "g" and "G", this specifies the maximum number of digits to show, |
7698aede | 7200 | including those prior to the decimal point and those after it; for |
3b10bc60 | 7201 | example: |
1ff2d182 | 7202 | |
3b10bc60 | 7203 | # These examples are subject to system-specific variation. |
1ff2d182 AS |
7204 | printf '<%g>', 1; # prints "<1>" |
7205 | printf '<%.10g>', 1; # prints "<1>" | |
7206 | printf '<%g>', 100; # prints "<100>" | |
7207 | printf '<%.1g>', 100; # prints "<1e+02>" | |
7208 | printf '<%.2g>', 100.01; # prints "<1e+02>" | |
7209 | printf '<%.5g>', 100.01; # prints "<100.01>" | |
7210 | printf '<%.4g>', 100.01; # prints "<100>" | |
7211 | ||
7b8dd722 | 7212 | For integer conversions, specifying a precision implies that the |
9911cee9 TS |
7213 | output of the number itself should be zero-padded to this width, |
7214 | where the 0 flag is ignored: | |
7215 | ||
7216 | printf '<%.6d>', 1; # prints "<000001>" | |
7217 | printf '<%+.6d>', 1; # prints "<+000001>" | |
7218 | printf '<%-10.6d>', 1; # prints "<000001 >" | |
7219 | printf '<%10.6d>', 1; # prints "< 000001>" | |
7220 | printf '<%010.6d>', 1; # prints "< 000001>" | |
7221 | printf '<%+10.6d>', 1; # prints "< +000001>" | |
7b8dd722 HS |
7222 | |
7223 | printf '<%.6x>', 1; # prints "<000001>" | |
7224 | printf '<%#.6x>', 1; # prints "<0x000001>" | |
7225 | printf '<%-10.6x>', 1; # prints "<000001 >" | |
9911cee9 TS |
7226 | printf '<%10.6x>', 1; # prints "< 000001>" |
7227 | printf '<%010.6x>', 1; # prints "< 000001>" | |
7228 | printf '<%#10.6x>', 1; # prints "< 0x000001>" | |
7b8dd722 HS |
7229 | |
7230 | For string conversions, specifying a precision truncates the string | |
3b10bc60 | 7231 | to fit the specified width: |
7b8dd722 HS |
7232 | |
7233 | printf '<%.5s>', "truncated"; # prints "<trunc>" | |
7234 | printf '<%10.5s>', "truncated"; # prints "< trunc>" | |
7235 | ||
7236 | You can also get the precision from the next argument using C<.*>: | |
b22c7a20 | 7237 | |
7b8dd722 HS |
7238 | printf '<%.6x>', 1; # prints "<000001>" |
7239 | printf '<%.*x>', 6, 1; # prints "<000001>" | |
7240 | ||
3b10bc60 | 7241 | If a precision obtained through C<*> is negative, it counts |
7242 | as having no precision at all. | |
9911cee9 TS |
7243 | |
7244 | printf '<%.*s>', 7, "string"; # prints "<string>" | |
7245 | printf '<%.*s>', 3, "string"; # prints "<str>" | |
7246 | printf '<%.*s>', 0, "string"; # prints "<>" | |
7247 | printf '<%.*s>', -1, "string"; # prints "<string>" | |
7248 | ||
7249 | printf '<%.*d>', 1, 0; # prints "<0>" | |
7250 | printf '<%.*d>', 0, 0; # prints "<>" | |
7251 | printf '<%.*d>', -1, 0; # prints "<0>" | |
7252 | ||
7b8dd722 | 7253 | You cannot currently get the precision from a specified number, |
3b10bc60 | 7254 | but it is intended that this will be possible in the future, for |
7255 | example using C<.*2$>: | |
7b8dd722 | 7256 | |
073d6857 | 7257 | printf '<%.*2$x>', 1, 6; # INVALID, but in future will print |
f7051f2c | 7258 | # "<000001>" |
7b8dd722 HS |
7259 | |
7260 | =item size | |
7261 | ||
7262 | For numeric conversions, you can specify the size to interpret the | |
391b733c | 7263 | number as using C<l>, C<h>, C<V>, C<q>, C<L>, or C<ll>. For integer |
1ff2d182 AS |
7264 | conversions (C<d u o x X b i D U O>), numbers are usually assumed to be |
7265 | whatever the default integer size is on your platform (usually 32 or 64 | |
7266 | bits), but you can override this to use instead one of the standard C types, | |
7267 | as supported by the compiler used to build Perl: | |
7b8dd722 | 7268 | |
f7051f2c | 7269 | hh interpret integer as C type "char" or "unsigned |
09700023 | 7270 | char" on Perl 5.14 or later |
f7051f2c FC |
7271 | h interpret integer as C type "short" or |
7272 | "unsigned short" | |
09700023 | 7273 | j interpret integer as C type "intmax_t" on Perl |
f7051f2c FC |
7274 | 5.14 or later, and only with a C99 compiler |
7275 | (unportable) | |
7276 | l interpret integer as C type "long" or | |
7277 | "unsigned long" | |
7278 | q, L, or ll interpret integer as C type "long long", | |
7279 | "unsigned long long", or "quad" (typically | |
7280 | 64-bit integers) | |
09700023 | 7281 | t interpret integer as C type "ptrdiff_t" on Perl |
f7051f2c | 7282 | 5.14 or later |
09700023 | 7283 | z interpret integer as C type "size_t" on Perl 5.14 |
f7051f2c | 7284 | or later |
3d21943e JV |
7285 | |
7286 | As of 5.14, none of these raises an exception if they are not supported on | |
7287 | your platform. However, if warnings are enabled, a warning of the | |
7288 | C<printf> warning class is issued on an unsupported conversion flag. | |
7289 | Should you instead prefer an exception, do this: | |
7290 | ||
7291 | use warnings FATAL => "printf"; | |
7292 | ||
7293 | If you would like to know about a version dependency before you | |
7294 | start running the program, put something like this at its top: | |
7295 | ||
7296 | use 5.014; # for hh/j/t/z/ printf modifiers | |
7b8dd722 | 7297 | |
3d21943e | 7298 | You can find out whether your Perl supports quads via L<Config>: |
7b8dd722 | 7299 | |
5ed4f2ec | 7300 | use Config; |
f7051f2c FC |
7301 | if ($Config{use64bitint} eq "define" |
7302 | || $Config{longsize} >= 8) { | |
3b10bc60 | 7303 | print "Nice quads!\n"; |
7304 | } | |
1ff2d182 | 7305 | |
3b10bc60 | 7306 | For floating-point conversions (C<e f g E F G>), numbers are usually assumed |
7307 | to be the default floating-point size on your platform (double or long double), | |
7308 | but you can force "long double" with C<q>, C<L>, or C<ll> if your | |
391b733c | 7309 | platform supports them. You can find out whether your Perl supports long |
1ff2d182 AS |
7310 | doubles via L<Config>: |
7311 | ||
5ed4f2ec | 7312 | use Config; |
3b10bc60 | 7313 | print "long doubles\n" if $Config{d_longdbl} eq "define"; |
1ff2d182 | 7314 | |
3b10bc60 | 7315 | You can find out whether Perl considers "long double" to be the default |
7316 | floating-point size to use on your platform via L<Config>: | |
1ff2d182 | 7317 | |
3b10bc60 | 7318 | use Config; |
7319 | if ($Config{uselongdouble} eq "define") { | |
09700023 | 7320 | print "long doubles by default\n"; |
3b10bc60 | 7321 | } |
1ff2d182 | 7322 | |
3b10bc60 | 7323 | It can also be that long doubles and doubles are the same thing: |
1ff2d182 AS |
7324 | |
7325 | use Config; | |
7326 | ($Config{doublesize} == $Config{longdblsize}) && | |
7327 | print "doubles are long doubles\n"; | |
7328 | ||
3b10bc60 | 7329 | The size specifier C<V> has no effect for Perl code, but is supported for |
7330 | compatibility with XS code. It means "use the standard size for a Perl | |
7331 | integer or floating-point number", which is the default. | |
7b8dd722 | 7332 | |
a472f209 HS |
7333 | =item order of arguments |
7334 | ||
3b10bc60 | 7335 | Normally, sprintf() takes the next unused argument as the value to |
391b733c | 7336 | format for each format specification. If the format specification |
a472f209 | 7337 | uses C<*> to require additional arguments, these are consumed from |
3b10bc60 | 7338 | the argument list in the order they appear in the format |
7339 | specification I<before> the value to format. Where an argument is | |
7340 | specified by an explicit index, this does not affect the normal | |
7341 | order for the arguments, even when the explicitly specified index | |
7342 | would have been the next argument. | |
a472f209 HS |
7343 | |
7344 | So: | |
7345 | ||
3b10bc60 | 7346 | printf "<%*.*s>", $a, $b, $c; |
a472f209 | 7347 | |
3b10bc60 | 7348 | uses C<$a> for the width, C<$b> for the precision, and C<$c> |
7349 | as the value to format; while: | |
a472f209 | 7350 | |
073d6857 | 7351 | printf '<%*1$.*s>', $a, $b; |
a472f209 | 7352 | |
3b10bc60 | 7353 | would use C<$a> for the width and precision, and C<$b> as the |
a472f209 HS |
7354 | value to format. |
7355 | ||
3b10bc60 | 7356 | Here are some more examples; be aware that when using an explicit |
7357 | index, the C<$> may need escaping: | |
a472f209 | 7358 | |
f7051f2c FC |
7359 | printf "%2\$d %d\n", 12, 34; # will print "34 12\n" |
7360 | printf "%2\$d %d %d\n", 12, 34; # will print "34 12 34\n" | |
7361 | printf "%3\$d %d %d\n", 12, 34, 56; # will print "56 12 34\n" | |
7362 | printf "%2\$*3\$d %d\n", 12, 34, 3; # will print " 34 12\n" | |
a472f209 | 7363 | |
7b8dd722 | 7364 | =back |
b22c7a20 | 7365 | |
66cbab2c KW |
7366 | If C<use locale> (including C<use locale 'not_characters'>) is in effect |
7367 | and POSIX::setlocale() has been called, | |
3b10bc60 | 7368 | the character used for the decimal separator in formatted floating-point |
7369 | numbers is affected by the LC_NUMERIC locale. See L<perllocale> | |
7e4353e9 | 7370 | and L<POSIX>. |
a0d0e21e LW |
7371 | |
7372 | =item sqrt EXPR | |
d74e8afc | 7373 | X<sqrt> X<root> X<square root> |
a0d0e21e | 7374 | |
54310121 | 7375 | =item sqrt |
bbce6d69 | 7376 | |
c17cdb72 NC |
7377 | =for Pod::Functions square root function |
7378 | ||
3b10bc60 | 7379 | Return the positive square root of EXPR. If EXPR is omitted, uses |
7380 | C<$_>. Works only for non-negative operands unless you've | |
7381 | loaded the C<Math::Complex> module. | |
2b5ab1e7 TC |
7382 | |
7383 | use Math::Complex; | |
3b10bc60 | 7384 | print sqrt(-4); # prints 2i |
a0d0e21e LW |
7385 | |
7386 | =item srand EXPR | |
d74e8afc | 7387 | X<srand> X<seed> X<randseed> |
a0d0e21e | 7388 | |
93dc8474 CS |
7389 | =item srand |
7390 | ||
c17cdb72 NC |
7391 | =for Pod::Functions seed the random number generator |
7392 | ||
83832992 | 7393 | Sets and returns the random number seed for the C<rand> operator. |
0686c0b8 | 7394 | |
bade7fbc TC |
7395 | The point of the function is to "seed" the C<rand> function so that C<rand> |
7396 | can produce a different sequence each time you run your program. When | |
7397 | called with a parameter, C<srand> uses that for the seed; otherwise it | |
7398 | (semi-)randomly chooses a seed. In either case, starting with Perl 5.14, | |
7399 | it returns the seed. To signal that your code will work I<only> on Perls | |
7400 | of a recent vintage: | |
7401 | ||
7402 | use 5.014; # so srand returns the seed | |
83832992 KW |
7403 | |
7404 | If C<srand()> is not called explicitly, it is called implicitly without a | |
e9fa405d BF |
7405 | parameter at the first use of the C<rand> operator. |
7406 | However, there are a few situations where programs are likely to | |
3c831796 | 7407 | want to call C<srand>. One is for generating predictable results, generally for |
83832992 | 7408 | testing or debugging. There, you use C<srand($seed)>, with the same C<$seed> |
416e3a83 | 7409 | each time. Another case is that you may want to call C<srand()> |
83832992 KW |
7410 | after a C<fork()> to avoid child processes sharing the same seed value as the |
7411 | parent (and consequently each other). | |
7412 | ||
7413 | Do B<not> call C<srand()> (i.e., without an argument) more than once per | |
d460397b | 7414 | process. The internal state of the random number generator should |
0686c0b8 | 7415 | contain more entropy than can be provided by any seed, so calling |
83832992 | 7416 | C<srand()> again actually I<loses> randomness. |
0686c0b8 | 7417 | |
e0b236fe JH |
7418 | Most implementations of C<srand> take an integer and will silently |
7419 | truncate decimal numbers. This means C<srand(42)> will usually | |
7420 | produce the same results as C<srand(42.1)>. To be safe, always pass | |
7421 | C<srand> an integer. | |
0686c0b8 | 7422 | |
83832992 KW |
7423 | A typical use of the returned seed is for a test program which has too many |
7424 | combinations to test comprehensively in the time available to it each run. It | |
7425 | can test a random subset each time, and should there be a failure, log the seed | |
8f1da26d | 7426 | used for that run so that it can later be used to reproduce the same results. |
83832992 | 7427 | |
416e3a83 AMS |
7428 | B<C<rand()> is not cryptographically secure. You should not rely |
7429 | on it in security-sensitive situations.> As of this writing, a | |
7430 | number of third-party CPAN modules offer random number generators | |
7431 | intended by their authors to be cryptographically secure, | |
7432 | including: L<Data::Entropy>, L<Crypt::Random>, L<Math::Random::Secure>, | |
7433 | and L<Math::TrulyRandom>. | |
7434 | ||
a0d0e21e | 7435 | =item stat FILEHANDLE |
435fbc73 | 7436 | X<stat> X<file, status> X<ctime> |
a0d0e21e LW |
7437 | |
7438 | =item stat EXPR | |
7439 | ||
5228a96c SP |
7440 | =item stat DIRHANDLE |
7441 | ||
54310121 | 7442 | =item stat |
bbce6d69 | 7443 | |
c17cdb72 NC |
7444 | =for Pod::Functions get a file's status information |
7445 | ||
1d2dff63 | 7446 | Returns a 13-element list giving the status info for a file, either |
5228a96c | 7447 | the file opened via FILEHANDLE or DIRHANDLE, or named by EXPR. If EXPR is |
8f1da26d | 7448 | omitted, it stats C<$_> (not C<_>!). Returns the empty list if C<stat> fails. Typically |
5228a96c | 7449 | used as follows: |
a0d0e21e LW |
7450 | |
7451 | ($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size, | |
7452 | $atime,$mtime,$ctime,$blksize,$blocks) | |
7453 | = stat($filename); | |
7454 | ||
54310121 | 7455 | Not all fields are supported on all filesystem types. Here are the |
61967be2 | 7456 | meanings of the fields: |
c07a80fd | 7457 | |
54310121 | 7458 | 0 dev device number of filesystem |
7459 | 1 ino inode number | |
7460 | 2 mode file mode (type and permissions) | |
7461 | 3 nlink number of (hard) links to the file | |
7462 | 4 uid numeric user ID of file's owner | |
7463 | 5 gid numeric group ID of file's owner | |
7464 | 6 rdev the device identifier (special files only) | |
7465 | 7 size total size of file, in bytes | |
1c74f1bd GS |
7466 | 8 atime last access time in seconds since the epoch |
7467 | 9 mtime last modify time in seconds since the epoch | |
df2a7e48 | 7468 | 10 ctime inode change time in seconds since the epoch (*) |
dd766832 CB |
7469 | 11 blksize preferred I/O size in bytes for interacting with the |
7470 | file (may vary from file to file) | |
7471 | 12 blocks actual number of system-specific blocks allocated | |
7472 | on disk (often, but not always, 512 bytes each) | |
c07a80fd | 7473 | |
7474 | (The epoch was at 00:00 January 1, 1970 GMT.) | |
7475 | ||
391b733c | 7476 | (*) Not all fields are supported on all filesystem types. Notably, the |
3e2557b2 | 7477 | ctime field is non-portable. In particular, you cannot expect it to be a |
8f1da26d | 7478 | "creation time"; see L<perlport/"Files and Filesystems"> for details. |
df2a7e48 | 7479 | |
61967be2 | 7480 | If C<stat> is passed the special filehandle consisting of an underline, no |
a0d0e21e | 7481 | stat is done, but the current contents of the stat structure from the |
61967be2 | 7482 | last C<stat>, C<lstat>, or filetest are returned. Example: |
a0d0e21e LW |
7483 | |
7484 | if (-x $file && (($d) = stat(_)) && $d < 0) { | |
a9a5a0dc | 7485 | print "$file is executable NFS file\n"; |
a0d0e21e LW |
7486 | } |
7487 | ||
ca6e1c26 JH |
7488 | (This works on machines only for which the device number is negative |
7489 | under NFS.) | |
a0d0e21e | 7490 | |
2b5ab1e7 | 7491 | Because the mode contains both the file type and its permissions, you |
b76cc8ba | 7492 | should mask off the file type portion and (s)printf using a C<"%o"> |
2b5ab1e7 TC |
7493 | if you want to see the real permissions. |
7494 | ||
7495 | $mode = (stat($filename))[2]; | |
7496 | printf "Permissions are %04o\n", $mode & 07777; | |
7497 | ||
19799a22 | 7498 | In scalar context, C<stat> returns a boolean value indicating success |
1d2dff63 GS |
7499 | or failure, and, if successful, sets the information associated with |
7500 | the special filehandle C<_>. | |
7501 | ||
dd184578 | 7502 | The L<File::stat> module provides a convenient, by-name access mechanism: |
2b5ab1e7 TC |
7503 | |
7504 | use File::stat; | |
7505 | $sb = stat($filename); | |
b76cc8ba | 7506 | printf "File is %s, size is %s, perm %04o, mtime %s\n", |
a9a5a0dc VP |
7507 | $filename, $sb->size, $sb->mode & 07777, |
7508 | scalar localtime $sb->mtime; | |
2b5ab1e7 | 7509 | |
ca6e1c26 JH |
7510 | You can import symbolic mode constants (C<S_IF*>) and functions |
7511 | (C<S_IS*>) from the Fcntl module: | |
7512 | ||
7513 | use Fcntl ':mode'; | |
7514 | ||
7515 | $mode = (stat($filename))[2]; | |
7516 | ||
7517 | $user_rwx = ($mode & S_IRWXU) >> 6; | |
7518 | $group_read = ($mode & S_IRGRP) >> 3; | |
7519 | $other_execute = $mode & S_IXOTH; | |
7520 | ||
3155e0b0 | 7521 | printf "Permissions are %04o\n", S_IMODE($mode), "\n"; |
ca6e1c26 JH |
7522 | |
7523 | $is_setuid = $mode & S_ISUID; | |
ad605d16 | 7524 | $is_directory = S_ISDIR($mode); |
ca6e1c26 JH |
7525 | |
7526 | You could write the last two using the C<-u> and C<-d> operators. | |
3b10bc60 | 7527 | Commonly available C<S_IF*> constants are: |
ca6e1c26 JH |
7528 | |
7529 | # Permissions: read, write, execute, for user, group, others. | |
7530 | ||
7531 | S_IRWXU S_IRUSR S_IWUSR S_IXUSR | |
7532 | S_IRWXG S_IRGRP S_IWGRP S_IXGRP | |
7533 | S_IRWXO S_IROTH S_IWOTH S_IXOTH | |
61eff3bc | 7534 | |
3cee8101 | 7535 | # Setuid/Setgid/Stickiness/SaveText. |
7df0fd0b | 7536 | # Note that the exact meaning of these is system-dependent. |
ca6e1c26 JH |
7537 | |
7538 | S_ISUID S_ISGID S_ISVTX S_ISTXT | |
7539 | ||
7df0fd0b FC |
7540 | # File types. Not all are necessarily available on |
7541 | # your system. | |
ca6e1c26 | 7542 | |
7df0fd0b FC |
7543 | S_IFREG S_IFDIR S_IFLNK S_IFBLK S_IFCHR |
7544 | S_IFIFO S_IFSOCK S_IFWHT S_ENFMT | |
ca6e1c26 | 7545 | |
7df0fd0b FC |
7546 | # The following are compatibility aliases for S_IRUSR, |
7547 | # S_IWUSR, and S_IXUSR. | |
ca6e1c26 JH |
7548 | |
7549 | S_IREAD S_IWRITE S_IEXEC | |
7550 | ||
61967be2 | 7551 | and the C<S_IF*> functions are |
ca6e1c26 | 7552 | |
7df0fd0b FC |
7553 | S_IMODE($mode) the part of $mode containing the permission |
7554 | bits and the setuid/setgid/sticky bits | |
ca6e1c26 | 7555 | |
7df0fd0b FC |
7556 | S_IFMT($mode) the part of $mode containing the file type |
7557 | which can be bit-anded with (for example) | |
7558 | S_IFREG or with the following functions | |
ca6e1c26 | 7559 | |
61967be2 | 7560 | # The operators -f, -d, -l, -b, -c, -p, and -S. |
ca6e1c26 JH |
7561 | |
7562 | S_ISREG($mode) S_ISDIR($mode) S_ISLNK($mode) | |
7563 | S_ISBLK($mode) S_ISCHR($mode) S_ISFIFO($mode) S_ISSOCK($mode) | |
7564 | ||
7565 | # No direct -X operator counterpart, but for the first one | |
7566 | # the -g operator is often equivalent. The ENFMT stands for | |
7567 | # record flocking enforcement, a platform-dependent feature. | |
7568 | ||
7569 | S_ISENFMT($mode) S_ISWHT($mode) | |
7570 | ||
7571 | See your native chmod(2) and stat(2) documentation for more details | |
61967be2 | 7572 | about the C<S_*> constants. To get status info for a symbolic link |
c837d5b4 | 7573 | instead of the target file behind the link, use the C<lstat> function. |
ca6e1c26 | 7574 | |
ea9eb35a BJ |
7575 | Portability issues: L<perlport/stat>. |
7576 | ||
672208d2 | 7577 | =item state VARLIST |
36fb85f3 RGS |
7578 | X<state> |
7579 | ||
672208d2 | 7580 | =item state TYPE VARLIST |
36fb85f3 | 7581 | |
672208d2 | 7582 | =item state VARLIST : ATTRS |
36fb85f3 | 7583 | |
672208d2 | 7584 | =item state TYPE VARLIST : ATTRS |
36fb85f3 | 7585 | |
d9b04284 | 7586 | =for Pod::Functions +state declare and assign a persistent lexical variable |
c17cdb72 | 7587 | |
4a904372 | 7588 | C<state> declares a lexically scoped variable, just like C<my>. |
b708784e | 7589 | However, those variables will never be reinitialized, contrary to |
36fb85f3 RGS |
7590 | lexical variables that are reinitialized each time their enclosing block |
7591 | is entered. | |
e476d66f | 7592 | See L<perlsub/"Persistent Private Variables"> for details. |
36fb85f3 | 7593 | |
672208d2 | 7594 | If more than one variable is listed, the list must be placed in |
7161e5c2 FC |
7595 | parentheses. With a parenthesised list, C<undef> can be used as a |
7596 | dummy placeholder. However, since initialization of state variables in | |
672208d2 JV |
7597 | list context is currently not possible this would serve no purpose. |
7598 | ||
3b10bc60 | 7599 | C<state> variables are enabled only when the C<use feature "state"> pragma |
4a904372 | 7600 | is in effect, unless the keyword is written as C<CORE::state>. |
e476d66f | 7601 | See also L<feature>. |
36fb85f3 | 7602 | |
a0d0e21e | 7603 | =item study SCALAR |
d74e8afc | 7604 | X<study> |
a0d0e21e LW |
7605 | |
7606 | =item study | |
7607 | ||
c17cdb72 NC |
7608 | =for Pod::Functions optimize input data for repeated searches |
7609 | ||
184e9718 | 7610 | Takes extra time to study SCALAR (C<$_> if unspecified) in anticipation of |
a0d0e21e LW |
7611 | doing many pattern matches on the string before it is next modified. |
7612 | This may or may not save time, depending on the nature and number of | |
8f1da26d | 7613 | patterns you are searching and the distribution of character |
3b10bc60 | 7614 | frequencies in the string to be searched; you probably want to compare |
8f1da26d | 7615 | run times with and without it to see which is faster. Those loops |
cf264981 | 7616 | that scan for many short constant strings (including the constant |
4185c919 NC |
7617 | parts of more complex patterns) will benefit most. |
7618 | (The way C<study> works is this: a linked list of every | |
a0d0e21e | 7619 | character in the string to be searched is made, so we know, for |
7660c0ab | 7620 | example, where all the C<'k'> characters are. From each search string, |
a0d0e21e LW |
7621 | the rarest character is selected, based on some static frequency tables |
7622 | constructed from some C programs and English text. Only those places | |
7623 | that contain this "rarest" character are examined.) | |
7624 | ||
5a964f20 | 7625 | For example, here is a loop that inserts index producing entries |
a0d0e21e LW |
7626 | before any line containing a certain pattern: |
7627 | ||
7628 | while (<>) { | |
a9a5a0dc VP |
7629 | study; |
7630 | print ".IX foo\n" if /\bfoo\b/; | |
7631 | print ".IX bar\n" if /\bbar\b/; | |
7632 | print ".IX blurfl\n" if /\bblurfl\b/; | |
7633 | # ... | |
7634 | print; | |
a0d0e21e LW |
7635 | } |
7636 | ||
3b10bc60 | 7637 | In searching for C</\bfoo\b/>, only locations in C<$_> that contain C<f> |
951ba7fe | 7638 | will be looked at, because C<f> is rarer than C<o>. In general, this is |
a0d0e21e LW |
7639 | a big win except in pathological cases. The only question is whether |
7640 | it saves you more time than it took to build the linked list in the | |
7641 | first place. | |
7642 | ||
7643 | Note that if you have to look for strings that you don't know till | |
19799a22 | 7644 | runtime, you can build an entire loop as a string and C<eval> that to |
a0d0e21e | 7645 | avoid recompiling all your patterns all the time. Together with |
80d38338 | 7646 | undefining C<$/> to input entire files as one record, this can be quite |
f86cebdf | 7647 | fast, often faster than specialized programs like fgrep(1). The following |
184e9718 | 7648 | scans a list of files (C<@files>) for a list of words (C<@words>), and prints |
a0d0e21e LW |
7649 | out the names of those files that contain a match: |
7650 | ||
7651 | $search = 'while (<>) { study;'; | |
7652 | foreach $word (@words) { | |
a9a5a0dc | 7653 | $search .= "++\$seen{\$ARGV} if /\\b$word\\b/;\n"; |
a0d0e21e LW |
7654 | } |
7655 | $search .= "}"; | |
7656 | @ARGV = @files; | |
7657 | undef $/; | |
5ed4f2ec | 7658 | eval $search; # this screams |
7659 | $/ = "\n"; # put back to normal input delimiter | |
a0d0e21e | 7660 | foreach $file (sort keys(%seen)) { |
a9a5a0dc | 7661 | print $file, "\n"; |
a0d0e21e LW |
7662 | } |
7663 | ||
1d2de774 | 7664 | =item sub NAME BLOCK |
d74e8afc | 7665 | X<sub> |
cb1a09d0 | 7666 | |
1d2de774 | 7667 | =item sub NAME (PROTO) BLOCK |
cb1a09d0 | 7668 | |
1d2de774 JH |
7669 | =item sub NAME : ATTRS BLOCK |
7670 | ||
7671 | =item sub NAME (PROTO) : ATTRS BLOCK | |
7672 | ||
c17cdb72 NC |
7673 | =for Pod::Functions declare a subroutine, possibly anonymously |
7674 | ||
8f1da26d TC |
7675 | This is subroutine definition, not a real function I<per se>. Without a |
7676 | BLOCK it's just a forward declaration. Without a NAME, it's an anonymous | |
7677 | function declaration, so does return a value: the CODE ref of the closure | |
7678 | just created. | |
cb1a09d0 | 7679 | |
1d2de774 | 7680 | See L<perlsub> and L<perlref> for details about subroutines and |
8f1da26d | 7681 | references; see L<attributes> and L<Attribute::Handlers> for more |
1d2de774 | 7682 | information about attributes. |
cb1a09d0 | 7683 | |
84ed0108 FC |
7684 | =item __SUB__ |
7685 | X<__SUB__> | |
7686 | ||
d9b04284 | 7687 | =for Pod::Functions +current_sub the current subroutine, or C<undef> if not in a subroutine |
c17cdb72 | 7688 | |
a453e28a | 7689 | A special token that returns a reference to the current subroutine, or |
84ed0108 FC |
7690 | C<undef> outside of a subroutine. |
7691 | ||
a453e28a DM |
7692 | The behaviour of C<__SUB__> within a regex code block (such as C</(?{...})/>) |
7693 | is subject to change. | |
7694 | ||
84ed0108 FC |
7695 | This token is only available under C<use v5.16> or the "current_sub" |
7696 | feature. See L<feature>. | |
7697 | ||
4fa8e151 FC |
7698 | =item substr EXPR,OFFSET,LENGTH,REPLACEMENT |
7699 | X<substr> X<substring> X<mid> X<left> X<right> | |
7700 | ||
87275199 | 7701 | =item substr EXPR,OFFSET,LENGTH |
a0d0e21e LW |
7702 | |
7703 | =item substr EXPR,OFFSET | |
7704 | ||
c17cdb72 NC |
7705 | =for Pod::Functions get or alter a portion of a string |
7706 | ||
a0d0e21e | 7707 | Extracts a substring out of EXPR and returns it. First character is at |
e1dccc0d | 7708 | offset zero. If OFFSET is negative, starts |
8f1da26d TC |
7709 | that far back from the end of the string. If LENGTH is omitted, returns |
7710 | everything through the end of the string. If LENGTH is negative, leaves that | |
748a9306 LW |
7711 | many characters off the end of the string. |
7712 | ||
e1de3ec0 | 7713 | my $s = "The black cat climbed the green tree"; |
5ed4f2ec | 7714 | my $color = substr $s, 4, 5; # black |
7715 | my $middle = substr $s, 4, -11; # black cat climbed the | |
7716 | my $end = substr $s, 14; # climbed the green tree | |
7717 | my $tail = substr $s, -4; # tree | |
7718 | my $z = substr $s, -4, 2; # tr | |
e1de3ec0 | 7719 | |
2b5ab1e7 | 7720 | You can use the substr() function as an lvalue, in which case EXPR |
87275199 GS |
7721 | must itself be an lvalue. If you assign something shorter than LENGTH, |
7722 | the string will shrink, and if you assign something longer than LENGTH, | |
2b5ab1e7 | 7723 | the string will grow to accommodate it. To keep the string the same |
3b10bc60 | 7724 | length, you may need to pad or chop your value using C<sprintf>. |
a0d0e21e | 7725 | |
87275199 GS |
7726 | If OFFSET and LENGTH specify a substring that is partly outside the |
7727 | string, only the part within the string is returned. If the substring | |
7728 | is beyond either end of the string, substr() returns the undefined | |
7729 | value and produces a warning. When used as an lvalue, specifying a | |
3b10bc60 | 7730 | substring that is entirely outside the string raises an exception. |
87275199 GS |
7731 | Here's an example showing the behavior for boundary cases: |
7732 | ||
7733 | my $name = 'fred'; | |
5ed4f2ec | 7734 | substr($name, 4) = 'dy'; # $name is now 'freddy' |
3b10bc60 | 7735 | my $null = substr $name, 6, 2; # returns "" (no warning) |
5ed4f2ec | 7736 | my $oops = substr $name, 7; # returns undef, with warning |
3b10bc60 | 7737 | substr($name, 7) = 'gap'; # raises an exception |
87275199 | 7738 | |
2b5ab1e7 | 7739 | An alternative to using substr() as an lvalue is to specify the |
7b8d334a | 7740 | replacement string as the 4th argument. This allows you to replace |
2b5ab1e7 TC |
7741 | parts of the EXPR and return what was there before in one operation, |
7742 | just as you can with splice(). | |
7b8d334a | 7743 | |
e1de3ec0 | 7744 | my $s = "The black cat climbed the green tree"; |
5ed4f2ec | 7745 | my $z = substr $s, 14, 7, "jumped from"; # climbed |
e1de3ec0 GS |
7746 | # $s is now "The black cat jumped from the green tree" |
7747 | ||
8f1da26d | 7748 | Note that the lvalue returned by the three-argument version of substr() acts as |
91f73676 DM |
7749 | a 'magic bullet'; each time it is assigned to, it remembers which part |
7750 | of the original string is being modified; for example: | |
7751 | ||
7752 | $x = '1234'; | |
7753 | for (substr($x,1,2)) { | |
5ed4f2ec | 7754 | $_ = 'a'; print $x,"\n"; # prints 1a4 |
7755 | $_ = 'xyz'; print $x,"\n"; # prints 1xyz4 | |
91f73676 | 7756 | $x = '56789'; |
5ed4f2ec | 7757 | $_ = 'pq'; print $x,"\n"; # prints 5pq9 |
91f73676 DM |
7758 | } |
7759 | ||
1d95ad8b FC |
7760 | With negative offsets, it remembers its position from the end of the string |
7761 | when the target string is modified: | |
7762 | ||
7763 | $x = '1234'; | |
7764 | for (substr($x, -3, 2)) { | |
7765 | $_ = 'a'; print $x,"\n"; # prints 1a4, as above | |
7766 | $x = 'abcdefg'; | |
7767 | print $_,"\n"; # prints f | |
7768 | } | |
7769 | ||
b8c25b3c | 7770 | Prior to Perl version 5.10, the result of using an lvalue multiple times was |
1d95ad8b | 7771 | unspecified. Prior to 5.16, the result with negative offsets was |
91f73676 | 7772 | unspecified. |
c67bbae0 | 7773 | |
a0d0e21e | 7774 | =item symlink OLDFILE,NEWFILE |
d74e8afc | 7775 | X<symlink> X<link> X<symbolic link> X<link, symbolic> |
a0d0e21e | 7776 | |
c17cdb72 NC |
7777 | =for Pod::Functions create a symbolic link to a file |
7778 | ||
a0d0e21e | 7779 | Creates a new filename symbolically linked to the old filename. |
7660c0ab | 7780 | Returns C<1> for success, C<0> otherwise. On systems that don't support |
3b10bc60 | 7781 | symbolic links, raises an exception. To check for that, |
a0d0e21e LW |
7782 | use eval: |
7783 | ||
2b5ab1e7 | 7784 | $symlink_exists = eval { symlink("",""); 1 }; |
a0d0e21e | 7785 | |
ea9eb35a BJ |
7786 | Portability issues: L<perlport/symlink>. |
7787 | ||
5702da47 | 7788 | =item syscall NUMBER, LIST |
d74e8afc | 7789 | X<syscall> X<system call> |
a0d0e21e | 7790 | |
c17cdb72 NC |
7791 | =for Pod::Functions execute an arbitrary system call |
7792 | ||
a0d0e21e LW |
7793 | Calls the system call specified as the first element of the list, |
7794 | passing the remaining elements as arguments to the system call. If | |
3b10bc60 | 7795 | unimplemented, raises an exception. The arguments are interpreted |
a0d0e21e LW |
7796 | as follows: if a given argument is numeric, the argument is passed as |
7797 | an int. If not, the pointer to the string value is passed. You are | |
7798 | responsible to make sure a string is pre-extended long enough to | |
a3cb178b | 7799 | receive any result that might be written into a string. You can't use a |
19799a22 | 7800 | string literal (or other read-only string) as an argument to C<syscall> |
a3cb178b GS |
7801 | because Perl has to assume that any string pointer might be written |
7802 | through. If your | |
a0d0e21e | 7803 | integer arguments are not literals and have never been interpreted in a |
7660c0ab | 7804 | numeric context, you may need to add C<0> to them to force them to look |
19799a22 | 7805 | like numbers. This emulates the C<syswrite> function (or vice versa): |
a0d0e21e | 7806 | |
5ed4f2ec | 7807 | require 'syscall.ph'; # may need to run h2ph |
a3cb178b GS |
7808 | $s = "hi there\n"; |
7809 | syscall(&SYS_write, fileno(STDOUT), $s, length $s); | |
a0d0e21e | 7810 | |
3b10bc60 | 7811 | Note that Perl supports passing of up to only 14 arguments to your syscall, |
7812 | which in practice should (usually) suffice. | |
a0d0e21e | 7813 | |
fb73857a | 7814 | Syscall returns whatever value returned by the system call it calls. |
19799a22 | 7815 | If the system call fails, C<syscall> returns C<-1> and sets C<$!> (errno). |
8f1da26d TC |
7816 | Note that some system calls I<can> legitimately return C<-1>. The proper |
7817 | way to handle such calls is to assign C<$!=0> before the call, then | |
7818 | check the value of C<$!> if C<syscall> returns C<-1>. | |
fb73857a | 7819 | |
7820 | There's a problem with C<syscall(&SYS_pipe)>: it returns the file | |
8f1da26d | 7821 | number of the read end of the pipe it creates, but there is no way |
b76cc8ba | 7822 | to retrieve the file number of the other end. You can avoid this |
19799a22 | 7823 | problem by using C<pipe> instead. |
fb73857a | 7824 | |
ea9eb35a BJ |
7825 | Portability issues: L<perlport/syscall>. |
7826 | ||
c07a80fd | 7827 | =item sysopen FILEHANDLE,FILENAME,MODE |
d74e8afc | 7828 | X<sysopen> |
c07a80fd | 7829 | |
7830 | =item sysopen FILEHANDLE,FILENAME,MODE,PERMS | |
7831 | ||
d9b04284 | 7832 | =for Pod::Functions +5.002 open a file, pipe, or descriptor |
c17cdb72 | 7833 | |
8f1da26d TC |
7834 | Opens the file whose filename is given by FILENAME, and associates it with |
7835 | FILEHANDLE. If FILEHANDLE is an expression, its value is used as the real | |
391b733c | 7836 | filehandle wanted; an undefined scalar will be suitably autovivified. This |
8f1da26d TC |
7837 | function calls the underlying operating system's I<open>(2) function with the |
7838 | parameters FILENAME, MODE, and PERMS. | |
c07a80fd | 7839 | |
7840 | The possible values and flag bits of the MODE parameter are | |
8f1da26d TC |
7841 | system-dependent; they are available via the standard module C<Fcntl>. See |
7842 | the documentation of your operating system's I<open>(2) syscall to see | |
7843 | which values and flag bits are available. You may combine several flags | |
ea2b5ef6 JH |
7844 | using the C<|>-operator. |
7845 | ||
7846 | Some of the most common values are C<O_RDONLY> for opening the file in | |
7847 | read-only mode, C<O_WRONLY> for opening the file in write-only mode, | |
c188b257 | 7848 | and C<O_RDWR> for opening the file in read-write mode. |
d74e8afc | 7849 | X<O_RDONLY> X<O_RDWR> X<O_WRONLY> |
ea2b5ef6 | 7850 | |
adf5897a | 7851 | For historical reasons, some values work on almost every system |
3b10bc60 | 7852 | supported by Perl: 0 means read-only, 1 means write-only, and 2 |
adf5897a | 7853 | means read/write. We know that these values do I<not> work under |
043fec90 | 7854 | OS/390 and on the Macintosh; you probably don't want to |
4af147f6 | 7855 | use them in new code. |
c07a80fd | 7856 | |
19799a22 | 7857 | If the file named by FILENAME does not exist and the C<open> call creates |
7660c0ab | 7858 | it (typically because MODE includes the C<O_CREAT> flag), then the value of |
5a964f20 | 7859 | PERMS specifies the permissions of the newly created file. If you omit |
19799a22 | 7860 | the PERMS argument to C<sysopen>, Perl uses the octal value C<0666>. |
5a964f20 | 7861 | These permission values need to be in octal, and are modified by your |
0591cd52 | 7862 | process's current C<umask>. |
d74e8afc | 7863 | X<O_CREAT> |
0591cd52 | 7864 | |
ea2b5ef6 JH |
7865 | In many systems the C<O_EXCL> flag is available for opening files in |
7866 | exclusive mode. This is B<not> locking: exclusiveness means here that | |
c188b257 PF |
7867 | if the file already exists, sysopen() fails. C<O_EXCL> may not work |
7868 | on network filesystems, and has no effect unless the C<O_CREAT> flag | |
7869 | is set as well. Setting C<O_CREAT|O_EXCL> prevents the file from | |
7870 | being opened if it is a symbolic link. It does not protect against | |
7871 | symbolic links in the file's path. | |
d74e8afc | 7872 | X<O_EXCL> |
c188b257 PF |
7873 | |
7874 | Sometimes you may want to truncate an already-existing file. This | |
7875 | can be done using the C<O_TRUNC> flag. The behavior of | |
7876 | C<O_TRUNC> with C<O_RDONLY> is undefined. | |
d74e8afc | 7877 | X<O_TRUNC> |
ea2b5ef6 | 7878 | |
19799a22 | 7879 | You should seldom if ever use C<0644> as argument to C<sysopen>, because |
2b5ab1e7 TC |
7880 | that takes away the user's option to have a more permissive umask. |
7881 | Better to omit it. See the perlfunc(1) entry on C<umask> for more | |
7882 | on this. | |
c07a80fd | 7883 | |
4af147f6 | 7884 | Note that C<sysopen> depends on the fdopen() C library function. |
e1020413 | 7885 | On many Unix systems, fdopen() is known to fail when file descriptors |
391b733c | 7886 | exceed a certain value, typically 255. If you need more file |
97cb92d6 | 7887 | descriptors than that, consider using the POSIX::open() function. |
4af147f6 | 7888 | |
2b5ab1e7 | 7889 | See L<perlopentut> for a kinder, gentler explanation of opening files. |
28757baa | 7890 | |
ea9eb35a BJ |
7891 | Portability issues: L<perlport/sysopen>. |
7892 | ||
a0d0e21e | 7893 | =item sysread FILEHANDLE,SCALAR,LENGTH,OFFSET |
d74e8afc | 7894 | X<sysread> |
a0d0e21e LW |
7895 | |
7896 | =item sysread FILEHANDLE,SCALAR,LENGTH | |
7897 | ||
c17cdb72 NC |
7898 | =for Pod::Functions fixed-length unbuffered input from a filehandle |
7899 | ||
3874323d | 7900 | Attempts to read LENGTH bytes of data into variable SCALAR from the |
3b10bc60 | 7901 | specified FILEHANDLE, using the read(2). It bypasses |
3874323d JH |
7902 | buffered IO, so mixing this with other kinds of reads, C<print>, |
7903 | C<write>, C<seek>, C<tell>, or C<eof> can cause confusion because the | |
7904 | perlio or stdio layers usually buffers data. Returns the number of | |
7905 | bytes actually read, C<0> at end of file, or undef if there was an | |
7906 | error (in the latter case C<$!> is also set). SCALAR will be grown or | |
7907 | shrunk so that the last byte actually read is the last byte of the | |
7908 | scalar after the read. | |
ff68c719 | 7909 | |
7910 | An OFFSET may be specified to place the read data at some place in the | |
7911 | string other than the beginning. A negative OFFSET specifies | |
9124316e JH |
7912 | placement at that many characters counting backwards from the end of |
7913 | the string. A positive OFFSET greater than the length of SCALAR | |
7914 | results in the string being padded to the required size with C<"\0"> | |
7915 | bytes before the result of the read is appended. | |
a0d0e21e | 7916 | |
2b5ab1e7 | 7917 | There is no syseof() function, which is ok, since eof() doesn't work |
80d38338 | 7918 | well on device files (like ttys) anyway. Use sysread() and check |
19799a22 | 7919 | for a return value for 0 to decide whether you're done. |
2b5ab1e7 | 7920 | |
3874323d JH |
7921 | Note that if the filehandle has been marked as C<:utf8> Unicode |
7922 | characters are read instead of bytes (the LENGTH, OFFSET, and the | |
5eadf7c5 | 7923 | return value of sysread() are in Unicode characters). |
3874323d JH |
7924 | The C<:encoding(...)> layer implicitly introduces the C<:utf8> layer. |
7925 | See L</binmode>, L</open>, and the C<open> pragma, L<open>. | |
7926 | ||
137443ea | 7927 | =item sysseek FILEHANDLE,POSITION,WHENCE |
d74e8afc | 7928 | X<sysseek> X<lseek> |
137443ea | 7929 | |
d9b04284 | 7930 | =for Pod::Functions +5.004 position I/O pointer on handle used with sysread and syswrite |
c17cdb72 | 7931 | |
8f1da26d TC |
7932 | Sets FILEHANDLE's system position in bytes using lseek(2). FILEHANDLE may |
7933 | be an expression whose value gives the name of the filehandle. The values | |
7934 | for WHENCE are C<0> to set the new position to POSITION; C<1> to set the it | |
7935 | to the current position plus POSITION; and C<2> to set it to EOF plus | |
7936 | POSITION, typically negative. | |
9124316e JH |
7937 | |
7938 | Note the I<in bytes>: even if the filehandle has been set to operate | |
740d4bb2 JW |
7939 | on characters (for example by using the C<:encoding(utf8)> I/O layer), |
7940 | tell() will return byte offsets, not character offsets (because | |
80d38338 | 7941 | implementing that would render sysseek() unacceptably slow). |
9124316e | 7942 | |
8f1da26d TC |
7943 | sysseek() bypasses normal buffered IO, so mixing it with reads other |
7944 | than C<sysread> (for example C<< <> >> or read()) C<print>, C<write>, | |
9124316e | 7945 | C<seek>, C<tell>, or C<eof> may cause confusion. |
86989e5d JH |
7946 | |
7947 | For WHENCE, you may also use the constants C<SEEK_SET>, C<SEEK_CUR>, | |
7948 | and C<SEEK_END> (start of the file, current position, end of the file) | |
7949 | from the Fcntl module. Use of the constants is also more portable | |
7950 | than relying on 0, 1, and 2. For example to define a "systell" function: | |
7951 | ||
5ed4f2ec | 7952 | use Fcntl 'SEEK_CUR'; |
7953 | sub systell { sysseek($_[0], 0, SEEK_CUR) } | |
8903cb82 | 7954 | |
7955 | Returns the new position, or the undefined value on failure. A position | |
19799a22 GS |
7956 | of zero is returned as the string C<"0 but true">; thus C<sysseek> returns |
7957 | true on success and false on failure, yet you can still easily determine | |
8903cb82 | 7958 | the new position. |
137443ea | 7959 | |
a0d0e21e | 7960 | =item system LIST |
d74e8afc | 7961 | X<system> X<shell> |
a0d0e21e | 7962 | |
8bf3b016 GS |
7963 | =item system PROGRAM LIST |
7964 | ||
c17cdb72 NC |
7965 | =for Pod::Functions run a separate program |
7966 | ||
19799a22 | 7967 | Does exactly the same thing as C<exec LIST>, except that a fork is |
8f1da26d | 7968 | done first and the parent process waits for the child process to |
80d38338 | 7969 | exit. Note that argument processing varies depending on the |
19799a22 GS |
7970 | number of arguments. If there is more than one argument in LIST, |
7971 | or if LIST is an array with more than one value, starts the program | |
7972 | given by the first element of the list with arguments given by the | |
7973 | rest of the list. If there is only one scalar argument, the argument | |
7974 | is checked for shell metacharacters, and if there are any, the | |
7975 | entire argument is passed to the system's command shell for parsing | |
7976 | (this is C</bin/sh -c> on Unix platforms, but varies on other | |
7977 | platforms). If there are no shell metacharacters in the argument, | |
7978 | it is split into words and passed directly to C<execvp>, which is | |
7979 | more efficient. | |
7980 | ||
e9fa405d | 7981 | Perl will attempt to flush all files opened for |
0f897271 GS |
7982 | output before any operation that may do a fork, but this may not be |
7983 | supported on some platforms (see L<perlport>). To be safe, you may need | |
7984 | to set C<$|> ($AUTOFLUSH in English) or call the C<autoflush()> method | |
7985 | of C<IO::Handle> on any open handles. | |
a2008d6d | 7986 | |
9d6eb86e | 7987 | The return value is the exit status of the program as returned by the |
25379e53 | 7988 | C<wait> call. To get the actual exit value, shift right by eight (see |
391b733c | 7989 | below). See also L</exec>. This is I<not> what you want to use to capture |
8f1da26d | 7990 | the output from a command; for that you should use merely backticks or |
d5a9bfb0 | 7991 | C<qx//>, as described in L<perlop/"`STRING`">. Return value of -1 |
25379e53 RGS |
7992 | indicates a failure to start the program or an error of the wait(2) system |
7993 | call (inspect $! for the reason). | |
a0d0e21e | 7994 | |
1af1c0d6 JV |
7995 | If you'd like to make C<system> (and many other bits of Perl) die on error, |
7996 | have a look at the L<autodie> pragma. | |
7997 | ||
19799a22 GS |
7998 | Like C<exec>, C<system> allows you to lie to a program about its name if |
7999 | you use the C<system PROGRAM LIST> syntax. Again, see L</exec>. | |
8bf3b016 | 8000 | |
4c2e8b59 BD |
8001 | Since C<SIGINT> and C<SIGQUIT> are ignored during the execution of |
8002 | C<system>, if you expect your program to terminate on receipt of these | |
8003 | signals you will need to arrange to do so yourself based on the return | |
8004 | value. | |
28757baa | 8005 | |
8006 | @args = ("command", "arg1", "arg2"); | |
54310121 | 8007 | system(@args) == 0 |
a9a5a0dc | 8008 | or die "system @args failed: $?" |
28757baa | 8009 | |
95da743b | 8010 | If you'd like to manually inspect C<system>'s failure, you can check all |
1af1c0d6 | 8011 | possible failure modes by inspecting C<$?> like this: |
28757baa | 8012 | |
4ef107a6 | 8013 | if ($? == -1) { |
a9a5a0dc | 8014 | print "failed to execute: $!\n"; |
4ef107a6 DM |
8015 | } |
8016 | elsif ($? & 127) { | |
a9a5a0dc VP |
8017 | printf "child died with signal %d, %s coredump\n", |
8018 | ($? & 127), ($? & 128) ? 'with' : 'without'; | |
4ef107a6 DM |
8019 | } |
8020 | else { | |
a9a5a0dc | 8021 | printf "child exited with value %d\n", $? >> 8; |
4ef107a6 DM |
8022 | } |
8023 | ||
3b10bc60 | 8024 | Alternatively, you may inspect the value of C<${^CHILD_ERROR_NATIVE}> |
8025 | with the C<W*()> calls from the POSIX module. | |
9d6eb86e | 8026 | |
3b10bc60 | 8027 | When C<system>'s arguments are executed indirectly by the shell, |
8028 | results and return codes are subject to its quirks. | |
c8db1d39 | 8029 | See L<perlop/"`STRING`"> and L</exec> for details. |
bb32b41a | 8030 | |
0a18a49b | 8031 | Since C<system> does a C<fork> and C<wait> it may affect a C<SIGCHLD> |
391b733c | 8032 | handler. See L<perlipc> for details. |
0a18a49b | 8033 | |
ea9eb35a BJ |
8034 | Portability issues: L<perlport/system>. |
8035 | ||
a0d0e21e | 8036 | =item syswrite FILEHANDLE,SCALAR,LENGTH,OFFSET |
d74e8afc | 8037 | X<syswrite> |
a0d0e21e LW |
8038 | |
8039 | =item syswrite FILEHANDLE,SCALAR,LENGTH | |
8040 | ||
145d37e2 GA |
8041 | =item syswrite FILEHANDLE,SCALAR |
8042 | ||
c17cdb72 NC |
8043 | =for Pod::Functions fixed-length unbuffered output to a filehandle |
8044 | ||
3874323d | 8045 | Attempts to write LENGTH bytes of data from variable SCALAR to the |
3b10bc60 | 8046 | specified FILEHANDLE, using write(2). If LENGTH is |
3874323d | 8047 | not specified, writes whole SCALAR. It bypasses buffered IO, so |
9124316e | 8048 | mixing this with reads (other than C<sysread())>, C<print>, C<write>, |
3874323d | 8049 | C<seek>, C<tell>, or C<eof> may cause confusion because the perlio and |
8f1da26d | 8050 | stdio layers usually buffer data. Returns the number of bytes |
3874323d JH |
8051 | actually written, or C<undef> if there was an error (in this case the |
8052 | errno variable C<$!> is also set). If the LENGTH is greater than the | |
3b10bc60 | 8053 | data available in the SCALAR after the OFFSET, only as much data as is |
3874323d | 8054 | available will be written. |
ff68c719 | 8055 | |
8056 | An OFFSET may be specified to write the data from some part of the | |
8057 | string other than the beginning. A negative OFFSET specifies writing | |
9124316e | 8058 | that many characters counting backwards from the end of the string. |
3b10bc60 | 8059 | If SCALAR is of length zero, you can only use an OFFSET of 0. |
9124316e | 8060 | |
8f1da26d | 8061 | B<WARNING>: If the filehandle is marked C<:utf8>, Unicode characters |
3b10bc60 | 8062 | encoded in UTF-8 are written instead of bytes, and the LENGTH, OFFSET, and |
8f1da26d | 8063 | return value of syswrite() are in (UTF8-encoded Unicode) characters. |
3874323d | 8064 | The C<:encoding(...)> layer implicitly introduces the C<:utf8> layer. |
8f1da26d TC |
8065 | Alternately, if the handle is not marked with an encoding but you |
8066 | attempt to write characters with code points over 255, raises an exception. | |
3874323d | 8067 | See L</binmode>, L</open>, and the C<open> pragma, L<open>. |
a0d0e21e LW |
8068 | |
8069 | =item tell FILEHANDLE | |
d74e8afc | 8070 | X<tell> |
a0d0e21e LW |
8071 | |
8072 | =item tell | |
8073 | ||
c17cdb72 NC |
8074 | =for Pod::Functions get current seekpointer on a filehandle |
8075 | ||
9124316e JH |
8076 | Returns the current position I<in bytes> for FILEHANDLE, or -1 on |
8077 | error. FILEHANDLE may be an expression whose value gives the name of | |
8078 | the actual filehandle. If FILEHANDLE is omitted, assumes the file | |
8079 | last read. | |
8080 | ||
8081 | Note the I<in bytes>: even if the filehandle has been set to | |
740d4bb2 JW |
8082 | operate on characters (for example by using the C<:encoding(utf8)> open |
8083 | layer), tell() will return byte offsets, not character offsets (because | |
8084 | that would render seek() and tell() rather slow). | |
2b5ab1e7 | 8085 | |
cfd73201 JH |
8086 | The return value of tell() for the standard streams like the STDIN |
8087 | depends on the operating system: it may return -1 or something else. | |
8088 | tell() on pipes, fifos, and sockets usually returns -1. | |
8089 | ||
19799a22 | 8090 | There is no C<systell> function. Use C<sysseek(FH, 0, 1)> for that. |
a0d0e21e | 8091 | |
3b10bc60 | 8092 | Do not use tell() (or other buffered I/O operations) on a filehandle |
8f1da26d | 8093 | that has been manipulated by sysread(), syswrite(), or sysseek(). |
59c9df15 | 8094 | Those functions ignore the buffering, while tell() does not. |
9124316e | 8095 | |
a0d0e21e | 8096 | =item telldir DIRHANDLE |
d74e8afc | 8097 | X<telldir> |
a0d0e21e | 8098 | |
c17cdb72 NC |
8099 | =for Pod::Functions get current seekpointer on a directory handle |
8100 | ||
19799a22 GS |
8101 | Returns the current position of the C<readdir> routines on DIRHANDLE. |
8102 | Value may be given to C<seekdir> to access a particular location in a | |
cf264981 SP |
8103 | directory. C<telldir> has the same caveats about possible directory |
8104 | compaction as the corresponding system library routine. | |
a0d0e21e | 8105 | |
4633a7c4 | 8106 | =item tie VARIABLE,CLASSNAME,LIST |
d74e8afc | 8107 | X<tie> |
a0d0e21e | 8108 | |
d9b04284 | 8109 | =for Pod::Functions +5.002 bind a variable to an object class |
c17cdb72 | 8110 | |
4633a7c4 LW |
8111 | This function binds a variable to a package class that will provide the |
8112 | implementation for the variable. VARIABLE is the name of the variable | |
8113 | to be enchanted. CLASSNAME is the name of a class implementing objects | |
64c33bad BG |
8114 | of correct type. Any additional arguments are passed to the |
8115 | appropriate constructor | |
8a059744 GS |
8116 | method of the class (meaning C<TIESCALAR>, C<TIEHANDLE>, C<TIEARRAY>, |
8117 | or C<TIEHASH>). Typically these are arguments such as might be passed | |
64c33bad BG |
8118 | to the C<dbm_open()> function of C. The object returned by the |
8119 | constructor is also returned by the C<tie> function, which would be useful | |
8a059744 | 8120 | if you want to access other methods in CLASSNAME. |
a0d0e21e | 8121 | |
19799a22 | 8122 | Note that functions such as C<keys> and C<values> may return huge lists |
1d2dff63 | 8123 | when used on large objects, like DBM files. You may prefer to use the |
19799a22 | 8124 | C<each> function to iterate over such. Example: |
a0d0e21e LW |
8125 | |
8126 | # print out history file offsets | |
4633a7c4 | 8127 | use NDBM_File; |
da0045b7 | 8128 | tie(%HIST, 'NDBM_File', '/usr/lib/news/history', 1, 0); |
a0d0e21e | 8129 | while (($key,$val) = each %HIST) { |
a9a5a0dc | 8130 | print $key, ' = ', unpack('L',$val), "\n"; |
a0d0e21e LW |
8131 | } |
8132 | untie(%HIST); | |
8133 | ||
aa689395 | 8134 | A class implementing a hash should have the following methods: |
a0d0e21e | 8135 | |
4633a7c4 | 8136 | TIEHASH classname, LIST |
a0d0e21e LW |
8137 | FETCH this, key |
8138 | STORE this, key, value | |
8139 | DELETE this, key | |
8a059744 | 8140 | CLEAR this |
a0d0e21e LW |
8141 | EXISTS this, key |
8142 | FIRSTKEY this | |
8143 | NEXTKEY this, lastkey | |
a3bcc51e | 8144 | SCALAR this |
8a059744 | 8145 | DESTROY this |
d7da42b7 | 8146 | UNTIE this |
a0d0e21e | 8147 | |
4633a7c4 | 8148 | A class implementing an ordinary array should have the following methods: |
a0d0e21e | 8149 | |
4633a7c4 | 8150 | TIEARRAY classname, LIST |
a0d0e21e LW |
8151 | FETCH this, key |
8152 | STORE this, key, value | |
8a059744 GS |
8153 | FETCHSIZE this |
8154 | STORESIZE this, count | |
8155 | CLEAR this | |
8156 | PUSH this, LIST | |
8157 | POP this | |
8158 | SHIFT this | |
8159 | UNSHIFT this, LIST | |
8160 | SPLICE this, offset, length, LIST | |
8161 | EXTEND this, count | |
7c25cd54 DM |
8162 | DELETE this, key |
8163 | EXISTS this, key | |
8a059744 | 8164 | DESTROY this |
d7da42b7 | 8165 | UNTIE this |
8a059744 | 8166 | |
3b10bc60 | 8167 | A class implementing a filehandle should have the following methods: |
8a059744 GS |
8168 | |
8169 | TIEHANDLE classname, LIST | |
8170 | READ this, scalar, length, offset | |
8171 | READLINE this | |
8172 | GETC this | |
8173 | WRITE this, scalar, length, offset | |
8174 | PRINT this, LIST | |
8175 | PRINTF this, format, LIST | |
e08f2115 GA |
8176 | BINMODE this |
8177 | EOF this | |
8178 | FILENO this | |
8179 | SEEK this, position, whence | |
8180 | TELL this | |
8181 | OPEN this, mode, LIST | |
8a059744 GS |
8182 | CLOSE this |
8183 | DESTROY this | |
d7da42b7 | 8184 | UNTIE this |
a0d0e21e | 8185 | |
4633a7c4 | 8186 | A class implementing a scalar should have the following methods: |
a0d0e21e | 8187 | |
4633a7c4 | 8188 | TIESCALAR classname, LIST |
54310121 | 8189 | FETCH this, |
a0d0e21e | 8190 | STORE this, value |
8a059744 | 8191 | DESTROY this |
d7da42b7 | 8192 | UNTIE this |
8a059744 GS |
8193 | |
8194 | Not all methods indicated above need be implemented. See L<perltie>, | |
2b5ab1e7 | 8195 | L<Tie::Hash>, L<Tie::Array>, L<Tie::Scalar>, and L<Tie::Handle>. |
a0d0e21e | 8196 | |
3b10bc60 | 8197 | Unlike C<dbmopen>, the C<tie> function will not C<use> or C<require> a module |
8198 | for you; you need to do that explicitly yourself. See L<DB_File> | |
19799a22 | 8199 | or the F<Config> module for interesting C<tie> implementations. |
4633a7c4 | 8200 | |
b687b08b | 8201 | For further details see L<perltie>, L<"tied VARIABLE">. |
cc6b7395 | 8202 | |
f3cbc334 | 8203 | =item tied VARIABLE |
d74e8afc | 8204 | X<tied> |
f3cbc334 | 8205 | |
c17cdb72 NC |
8206 | =for Pod::Functions get a reference to the object underlying a tied variable |
8207 | ||
f3cbc334 | 8208 | Returns a reference to the object underlying VARIABLE (the same value |
19799a22 | 8209 | that was originally returned by the C<tie> call that bound the variable |
f3cbc334 RS |
8210 | to a package.) Returns the undefined value if VARIABLE isn't tied to a |
8211 | package. | |
8212 | ||
a0d0e21e | 8213 | =item time |
d74e8afc | 8214 | X<time> X<epoch> |
a0d0e21e | 8215 | |
c17cdb72 NC |
8216 | =for Pod::Functions return number of seconds since 1970 |
8217 | ||
da0045b7 | 8218 | Returns the number of non-leap seconds since whatever time the system |
ef4d88db | 8219 | considers to be the epoch, suitable for feeding to C<gmtime> and |
391b733c | 8220 | C<localtime>. On most systems the epoch is 00:00:00 UTC, January 1, 1970; |
ef4d88db NC |
8221 | a prominent exception being Mac OS Classic which uses 00:00:00, January 1, |
8222 | 1904 in the current local time zone for its epoch. | |
a0d0e21e | 8223 | |
8f1da26d TC |
8224 | For measuring time in better granularity than one second, use the |
8225 | L<Time::HiRes> module from Perl 5.8 onwards (or from CPAN before then), or, | |
8226 | if you have gettimeofday(2), you may be able to use the C<syscall> | |
8227 | interface of Perl. See L<perlfaq8> for details. | |
68f8bed4 | 8228 | |
435fbc73 GS |
8229 | For date and time processing look at the many related modules on CPAN. |
8230 | For a comprehensive date and time representation look at the | |
8231 | L<DateTime> module. | |
8232 | ||
a0d0e21e | 8233 | =item times |
d74e8afc | 8234 | X<times> |
a0d0e21e | 8235 | |
c17cdb72 NC |
8236 | =for Pod::Functions return elapsed time for self and child processes |
8237 | ||
8f1da26d TC |
8238 | Returns a four-element list giving the user and system times in |
8239 | seconds for this process and any exited children of this process. | |
a0d0e21e LW |
8240 | |
8241 | ($user,$system,$cuser,$csystem) = times; | |
8242 | ||
dc19f4fb MJD |
8243 | In scalar context, C<times> returns C<$user>. |
8244 | ||
3b10bc60 | 8245 | Children's times are only included for terminated children. |
2a958fe2 | 8246 | |
ea9eb35a BJ |
8247 | Portability issues: L<perlport/times>. |
8248 | ||
a0d0e21e LW |
8249 | =item tr/// |
8250 | ||
c17cdb72 NC |
8251 | =for Pod::Functions transliterate a string |
8252 | ||
9f4b9cd0 | 8253 | The transliteration operator. Same as C<y///>. See |
cdf6c183 | 8254 | L<perlop/"Quote-Like Operators">. |
a0d0e21e LW |
8255 | |
8256 | =item truncate FILEHANDLE,LENGTH | |
d74e8afc | 8257 | X<truncate> |
a0d0e21e LW |
8258 | |
8259 | =item truncate EXPR,LENGTH | |
8260 | ||
c17cdb72 NC |
8261 | =for Pod::Functions shorten a file |
8262 | ||
a0d0e21e | 8263 | Truncates the file opened on FILEHANDLE, or named by EXPR, to the |
3b10bc60 | 8264 | specified length. Raises an exception if truncate isn't implemented |
8f1da26d | 8265 | on your system. Returns true if successful, C<undef> on error. |
a0d0e21e | 8266 | |
90ddc76f MS |
8267 | The behavior is undefined if LENGTH is greater than the length of the |
8268 | file. | |
8269 | ||
8577f58c | 8270 | The position in the file of FILEHANDLE is left unchanged. You may want to |
96090e4f | 8271 | call L<seek|/"seek FILEHANDLE,POSITION,WHENCE"> before writing to the file. |
8577f58c | 8272 | |
ea9eb35a BJ |
8273 | Portability issues: L<perlport/truncate>. |
8274 | ||
a0d0e21e | 8275 | =item uc EXPR |
d74e8afc | 8276 | X<uc> X<uppercase> X<toupper> |
a0d0e21e | 8277 | |
54310121 | 8278 | =item uc |
bbce6d69 | 8279 | |
c17cdb72 NC |
8280 | =for Pod::Functions return upper-case version of a string |
8281 | ||
a0d0e21e | 8282 | Returns an uppercased version of EXPR. This is the internal function |
3980dc9c | 8283 | implementing the C<\U> escape in double-quoted strings. |
983ffd37 | 8284 | It does not attempt to do titlecase mapping on initial letters. See |
3980dc9c | 8285 | L</ucfirst> for that. |
a0d0e21e | 8286 | |
7660c0ab | 8287 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 8288 | |
3980dc9c KW |
8289 | This function behaves the same way under various pragma, such as in a locale, |
8290 | as L</lc> does. | |
8291 | ||
a0d0e21e | 8292 | =item ucfirst EXPR |
d74e8afc | 8293 | X<ucfirst> X<uppercase> |
a0d0e21e | 8294 | |
54310121 | 8295 | =item ucfirst |
bbce6d69 | 8296 | |
c17cdb72 NC |
8297 | =for Pod::Functions return a string with just the next letter in upper case |
8298 | ||
ad0029c4 JH |
8299 | Returns the value of EXPR with the first character in uppercase |
8300 | (titlecase in Unicode). This is the internal function implementing | |
3980dc9c | 8301 | the C<\u> escape in double-quoted strings. |
a0d0e21e | 8302 | |
7660c0ab | 8303 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 8304 | |
3980dc9c KW |
8305 | This function behaves the same way under various pragma, such as in a locale, |
8306 | as L</lc> does. | |
8307 | ||
a0d0e21e | 8308 | =item umask EXPR |
d74e8afc | 8309 | X<umask> |
a0d0e21e LW |
8310 | |
8311 | =item umask | |
8312 | ||
c17cdb72 NC |
8313 | =for Pod::Functions set file creation mode mask |
8314 | ||
2f9daede | 8315 | Sets the umask for the process to EXPR and returns the previous value. |
eec2d3df GS |
8316 | If EXPR is omitted, merely returns the current umask. |
8317 | ||
0591cd52 NT |
8318 | The Unix permission C<rwxr-x---> is represented as three sets of three |
8319 | bits, or three octal digits: C<0750> (the leading 0 indicates octal | |
b5a41e52 | 8320 | and isn't one of the digits). The C<umask> value is such a number |
0591cd52 NT |
8321 | representing disabled permissions bits. The permission (or "mode") |
8322 | values you pass C<mkdir> or C<sysopen> are modified by your umask, so | |
8323 | even if you tell C<sysopen> to create a file with permissions C<0777>, | |
8f1da26d | 8324 | if your umask is C<0022>, then the file will actually be created with |
0591cd52 NT |
8325 | permissions C<0755>. If your C<umask> were C<0027> (group can't |
8326 | write; others can't read, write, or execute), then passing | |
8f1da26d TC |
8327 | C<sysopen> C<0666> would create a file with mode C<0640> (because |
8328 | C<0666 &~ 027> is C<0640>). | |
0591cd52 NT |
8329 | |
8330 | Here's some advice: supply a creation mode of C<0666> for regular | |
19799a22 GS |
8331 | files (in C<sysopen>) and one of C<0777> for directories (in |
8332 | C<mkdir>) and executable files. This gives users the freedom of | |
0591cd52 NT |
8333 | choice: if they want protected files, they might choose process umasks |
8334 | of C<022>, C<027>, or even the particularly antisocial mask of C<077>. | |
8335 | Programs should rarely if ever make policy decisions better left to | |
8336 | the user. The exception to this is when writing files that should be | |
8337 | kept private: mail files, web browser cookies, I<.rhosts> files, and | |
8338 | so on. | |
8339 | ||
f86cebdf | 8340 | If umask(2) is not implemented on your system and you are trying to |
3b10bc60 | 8341 | restrict access for I<yourself> (i.e., C<< (EXPR & 0700) > 0 >>), |
8342 | raises an exception. If umask(2) is not implemented and you are | |
eec2d3df GS |
8343 | not trying to restrict access for yourself, returns C<undef>. |
8344 | ||
8345 | Remember that a umask is a number, usually given in octal; it is I<not> a | |
8346 | string of octal digits. See also L</oct>, if all you have is a string. | |
a0d0e21e | 8347 | |
ea9eb35a BJ |
8348 | Portability issues: L<perlport/umask>. |
8349 | ||
a0d0e21e | 8350 | =item undef EXPR |
d74e8afc | 8351 | X<undef> X<undefine> |
a0d0e21e LW |
8352 | |
8353 | =item undef | |
8354 | ||
c17cdb72 NC |
8355 | =for Pod::Functions remove a variable or function definition |
8356 | ||
54310121 | 8357 | Undefines the value of EXPR, which must be an lvalue. Use only on a |
19799a22 | 8358 | scalar value, an array (using C<@>), a hash (using C<%>), a subroutine |
3b10bc60 | 8359 | (using C<&>), or a typeglob (using C<*>). Saying C<undef $hash{$key}> |
20408e3c | 8360 | will probably not do what you expect on most predefined variables or |
4509d391 | 8361 | DBM list values, so don't do that; see L</delete>. Always returns the |
20408e3c GS |
8362 | undefined value. You can omit the EXPR, in which case nothing is |
8363 | undefined, but you still get an undefined value that you could, for | |
3b10bc60 | 8364 | instance, return from a subroutine, assign to a variable, or pass as a |
20408e3c | 8365 | parameter. Examples: |
a0d0e21e LW |
8366 | |
8367 | undef $foo; | |
f86cebdf | 8368 | undef $bar{'blurfl'}; # Compare to: delete $bar{'blurfl'}; |
a0d0e21e | 8369 | undef @ary; |
aa689395 | 8370 | undef %hash; |
a0d0e21e | 8371 | undef &mysub; |
20408e3c | 8372 | undef *xyz; # destroys $xyz, @xyz, %xyz, &xyz, etc. |
54310121 | 8373 | return (wantarray ? (undef, $errmsg) : undef) if $they_blew_it; |
2f9daede TP |
8374 | select undef, undef, undef, 0.25; |
8375 | ($a, $b, undef, $c) = &foo; # Ignore third value returned | |
a0d0e21e | 8376 | |
5a964f20 TC |
8377 | Note that this is a unary operator, not a list operator. |
8378 | ||
a0d0e21e | 8379 | =item unlink LIST |
dd184578 | 8380 | X<unlink> X<delete> X<remove> X<rm> X<del> |
a0d0e21e | 8381 | |
54310121 | 8382 | =item unlink |
bbce6d69 | 8383 | |
c17cdb72 NC |
8384 | =for Pod::Functions remove one link to a file |
8385 | ||
391b733c FC |
8386 | Deletes a list of files. On success, it returns the number of files |
8387 | it successfully deleted. On failure, it returns false and sets C<$!> | |
40ea6f68 | 8388 | (errno): |
a0d0e21e | 8389 | |
40ea6f68 | 8390 | my $unlinked = unlink 'a', 'b', 'c'; |
a0d0e21e | 8391 | unlink @goners; |
40ea6f68 | 8392 | unlink glob "*.bak"; |
a0d0e21e | 8393 | |
40ea6f68 | 8394 | On error, C<unlink> will not tell you which files it could not remove. |
734c9e01 | 8395 | If you want to know which files you could not remove, try them one |
40ea6f68 | 8396 | at a time: |
a0d0e21e | 8397 | |
40ea6f68 | 8398 | foreach my $file ( @goners ) { |
8399 | unlink $file or warn "Could not unlink $file: $!"; | |
3b10bc60 | 8400 | } |
40ea6f68 | 8401 | |
8402 | Note: C<unlink> will not attempt to delete directories unless you are | |
391b733c | 8403 | superuser and the B<-U> flag is supplied to Perl. Even if these |
40ea6f68 | 8404 | conditions are met, be warned that unlinking a directory can inflict |
8405 | damage on your filesystem. Finally, using C<unlink> on directories is | |
8406 | not supported on many operating systems. Use C<rmdir> instead. | |
8407 | ||
8408 | If LIST is omitted, C<unlink> uses C<$_>. | |
bbce6d69 | 8409 | |
a0d0e21e | 8410 | =item unpack TEMPLATE,EXPR |
d74e8afc | 8411 | X<unpack> |
a0d0e21e | 8412 | |
13dcffc6 CS |
8413 | =item unpack TEMPLATE |
8414 | ||
c17cdb72 NC |
8415 | =for Pod::Functions convert binary structure into normal perl variables |
8416 | ||
19799a22 | 8417 | C<unpack> does the reverse of C<pack>: it takes a string |
2b6c5635 | 8418 | and expands it out into a list of values. |
19799a22 | 8419 | (In scalar context, it returns merely the first value produced.) |
2b6c5635 | 8420 | |
eae68503 | 8421 | If EXPR is omitted, unpacks the C<$_> string. |
3980dc9c | 8422 | See L<perlpacktut> for an introduction to this function. |
13dcffc6 | 8423 | |
2b6c5635 GS |
8424 | The string is broken into chunks described by the TEMPLATE. Each chunk |
8425 | is converted separately to a value. Typically, either the string is a result | |
f337b084 | 8426 | of C<pack>, or the characters of the string represent a C structure of some |
2b6c5635 GS |
8427 | kind. |
8428 | ||
19799a22 | 8429 | The TEMPLATE has the same format as in the C<pack> function. |
a0d0e21e LW |
8430 | Here's a subroutine that does substring: |
8431 | ||
8432 | sub substr { | |
5ed4f2ec | 8433 | my($what,$where,$howmuch) = @_; |
8434 | unpack("x$where a$howmuch", $what); | |
a0d0e21e LW |
8435 | } |
8436 | ||
8437 | and then there's | |
8438 | ||
f337b084 | 8439 | sub ordinal { unpack("W",$_[0]); } # same as ord() |
a0d0e21e | 8440 | |
2b6c5635 | 8441 | In addition to fields allowed in pack(), you may prefix a field with |
61eff3bc JH |
8442 | a %<number> to indicate that |
8443 | you want a <number>-bit checksum of the items instead of the items | |
2b6c5635 GS |
8444 | themselves. Default is a 16-bit checksum. Checksum is calculated by |
8445 | summing numeric values of expanded values (for string fields the sum of | |
8f1da26d | 8446 | C<ord($char)> is taken; for bit fields the sum of zeroes and ones). |
2b6c5635 GS |
8447 | |
8448 | For example, the following | |
a0d0e21e LW |
8449 | computes the same number as the System V sum program: |
8450 | ||
19799a22 | 8451 | $checksum = do { |
5ed4f2ec | 8452 | local $/; # slurp! |
8453 | unpack("%32W*",<>) % 65535; | |
19799a22 | 8454 | }; |
a0d0e21e LW |
8455 | |
8456 | The following efficiently counts the number of set bits in a bit vector: | |
8457 | ||
8458 | $setbits = unpack("%32b*", $selectmask); | |
8459 | ||
951ba7fe | 8460 | The C<p> and C<P> formats should be used with care. Since Perl |
3160c391 GS |
8461 | has no way of checking whether the value passed to C<unpack()> |
8462 | corresponds to a valid memory location, passing a pointer value that's | |
8463 | not known to be valid is likely to have disastrous consequences. | |
8464 | ||
49704364 WL |
8465 | If there are more pack codes or if the repeat count of a field or a group |
8466 | is larger than what the remainder of the input string allows, the result | |
3b10bc60 | 8467 | is not well defined: the repeat count may be decreased, or |
8468 | C<unpack()> may produce empty strings or zeros, or it may raise an exception. | |
8469 | If the input string is longer than one described by the TEMPLATE, | |
8470 | the remainder of that input string is ignored. | |
2b6c5635 | 8471 | |
851646ae | 8472 | See L</pack> for more examples and notes. |
5a929a98 | 8473 | |
532eee96 | 8474 | =item unshift ARRAY,LIST |
d74e8afc | 8475 | X<unshift> |
a0d0e21e | 8476 | |
f5a93a43 TC |
8477 | =item unshift EXPR,LIST |
8478 | ||
c17cdb72 NC |
8479 | =for Pod::Functions prepend more elements to the beginning of a list |
8480 | ||
19799a22 | 8481 | Does the opposite of a C<shift>. Or the opposite of a C<push>, |
a0d0e21e | 8482 | depending on how you look at it. Prepends list to the front of the |
8f1da26d | 8483 | array and returns the new number of elements in the array. |
a0d0e21e | 8484 | |
76e4c2bb | 8485 | unshift(@ARGV, '-e') unless $ARGV[0] =~ /^-/; |
a0d0e21e LW |
8486 | |
8487 | Note the LIST is prepended whole, not one element at a time, so the | |
19799a22 | 8488 | prepended elements stay in the same order. Use C<reverse> to do the |
a0d0e21e LW |
8489 | reverse. |
8490 | ||
f5a93a43 TC |
8491 | Starting with Perl 5.14, C<unshift> can take a scalar EXPR, which must hold |
8492 | a reference to an unblessed array. The argument will be dereferenced | |
8493 | automatically. This aspect of C<unshift> is considered highly | |
8494 | experimental. The exact behaviour may change in a future version of Perl. | |
cba5a3b0 | 8495 | |
bade7fbc TC |
8496 | To avoid confusing would-be users of your code who are running earlier |
8497 | versions of Perl with mysterious syntax errors, put this sort of thing at | |
8498 | the top of your file to signal that your code will work I<only> on Perls of | |
8499 | a recent vintage: | |
8500 | ||
8501 | use 5.014; # so push/pop/etc work on scalars (experimental) | |
8502 | ||
8503 | =item untie VARIABLE | |
8504 | X<untie> | |
8505 | ||
c17cdb72 NC |
8506 | =for Pod::Functions break a tie binding to a variable |
8507 | ||
bade7fbc TC |
8508 | Breaks the binding between a variable and a package. |
8509 | (See L<tie|/tie VARIABLE,CLASSNAME,LIST>.) | |
8510 | Has no effect if the variable is not tied. | |
8511 | ||
f6c8478c | 8512 | =item use Module VERSION LIST |
d74e8afc | 8513 | X<use> X<module> X<import> |
f6c8478c GS |
8514 | |
8515 | =item use Module VERSION | |
8516 | ||
a0d0e21e LW |
8517 | =item use Module LIST |
8518 | ||
8519 | =item use Module | |
8520 | ||
da0045b7 | 8521 | =item use VERSION |
8522 | ||
c17cdb72 NC |
8523 | =for Pod::Functions load in a module at compile time and import its namespace |
8524 | ||
a0d0e21e LW |
8525 | Imports some semantics into the current package from the named module, |
8526 | generally by aliasing certain subroutine or variable names into your | |
8527 | package. It is exactly equivalent to | |
8528 | ||
6d9d0573 | 8529 | BEGIN { require Module; Module->import( LIST ); } |
a0d0e21e | 8530 | |
54310121 | 8531 | except that Module I<must> be a bareword. |
08ed3542 | 8532 | The importation can be made conditional by using the L<if> module. |
da0045b7 | 8533 | |
bd12309b DG |
8534 | In the peculiar C<use VERSION> form, VERSION may be either a positive |
8535 | decimal fraction such as 5.006, which will be compared to C<$]>, or a v-string | |
8536 | of the form v5.6.1, which will be compared to C<$^V> (aka $PERL_VERSION). An | |
3b10bc60 | 8537 | exception is raised if VERSION is greater than the version of the |
c986422f RGS |
8538 | current Perl interpreter; Perl will not attempt to parse the rest of the |
8539 | file. Compare with L</require>, which can do a similar check at run time. | |
8540 | Symmetrically, C<no VERSION> allows you to specify that you want a version | |
3b10bc60 | 8541 | of Perl older than the specified one. |
3b825e41 RK |
8542 | |
8543 | Specifying VERSION as a literal of the form v5.6.1 should generally be | |
8544 | avoided, because it leads to misleading error messages under earlier | |
2e8342de RGS |
8545 | versions of Perl (that is, prior to 5.6.0) that do not support this |
8546 | syntax. The equivalent numeric version should be used instead. | |
fbc891ce | 8547 | |
5ed4f2ec | 8548 | use v5.6.1; # compile time version check |
8549 | use 5.6.1; # ditto | |
8550 | use 5.006_001; # ditto; preferred for backwards compatibility | |
16070b82 GS |
8551 | |
8552 | This is often useful if you need to check the current Perl version before | |
2e8342de RGS |
8553 | C<use>ing library modules that won't work with older versions of Perl. |
8554 | (We try not to do this more than we have to.) | |
da0045b7 | 8555 | |
4653ec93 FC |
8556 | C<use VERSION> also enables all features available in the requested |
8557 | version as defined by the C<feature> pragma, disabling any features | |
1b8bf4b9 | 8558 | not in the requested version's feature bundle. See L<feature>. |
3b10bc60 | 8559 | Similarly, if the specified Perl version is greater than or equal to |
e9fa405d | 8560 | 5.12.0, strictures are enabled lexically as |
4653ec93 | 8561 | with C<use strict>. Any explicit use of |
70397346 | 8562 | C<use strict> or C<no strict> overrides C<use VERSION>, even if it comes |
4653ec93 FC |
8563 | before it. In both cases, the F<feature.pm> and F<strict.pm> files are |
8564 | not actually loaded. | |
7dfde25d | 8565 | |
19799a22 | 8566 | The C<BEGIN> forces the C<require> and C<import> to happen at compile time. The |
7660c0ab | 8567 | C<require> makes sure the module is loaded into memory if it hasn't been |
3b10bc60 | 8568 | yet. The C<import> is not a builtin; it's just an ordinary static method |
19799a22 | 8569 | call into the C<Module> package to tell the module to import the list of |
a0d0e21e | 8570 | features back into the current package. The module can implement its |
19799a22 GS |
8571 | C<import> method any way it likes, though most modules just choose to |
8572 | derive their C<import> method via inheritance from the C<Exporter> class that | |
8573 | is defined in the C<Exporter> module. See L<Exporter>. If no C<import> | |
593b9c14 YST |
8574 | method can be found then the call is skipped, even if there is an AUTOLOAD |
8575 | method. | |
cb1a09d0 | 8576 | |
31686daf JP |
8577 | If you do not want to call the package's C<import> method (for instance, |
8578 | to stop your namespace from being altered), explicitly supply the empty list: | |
cb1a09d0 AD |
8579 | |
8580 | use Module (); | |
8581 | ||
8582 | That is exactly equivalent to | |
8583 | ||
5a964f20 | 8584 | BEGIN { require Module } |
a0d0e21e | 8585 | |
da0045b7 | 8586 | If the VERSION argument is present between Module and LIST, then the |
71be2cbc | 8587 | C<use> will call the VERSION method in class Module with the given |
8588 | version as an argument. The default VERSION method, inherited from | |
44dcb63b | 8589 | the UNIVERSAL class, croaks if the given version is larger than the |
b76cc8ba | 8590 | value of the variable C<$Module::VERSION>. |
f6c8478c GS |
8591 | |
8592 | Again, there is a distinction between omitting LIST (C<import> called | |
8593 | with no arguments) and an explicit empty LIST C<()> (C<import> not | |
8594 | called). Note that there is no comma after VERSION! | |
da0045b7 | 8595 | |
a0d0e21e LW |
8596 | Because this is a wide-open interface, pragmas (compiler directives) |
8597 | are also implemented this way. Currently implemented pragmas are: | |
8598 | ||
f3798619 | 8599 | use constant; |
4633a7c4 | 8600 | use diagnostics; |
f3798619 | 8601 | use integer; |
4438c4b7 JH |
8602 | use sigtrap qw(SEGV BUS); |
8603 | use strict qw(subs vars refs); | |
8604 | use subs qw(afunc blurfl); | |
8605 | use warnings qw(all); | |
58c7fc7c | 8606 | use sort qw(stable _quicksort _mergesort); |
a0d0e21e | 8607 | |
19799a22 | 8608 | Some of these pseudo-modules import semantics into the current |
5a964f20 TC |
8609 | block scope (like C<strict> or C<integer>, unlike ordinary modules, |
8610 | which import symbols into the current package (which are effective | |
8611 | through the end of the file). | |
a0d0e21e | 8612 | |
c362798e Z |
8613 | Because C<use> takes effect at compile time, it doesn't respect the |
8614 | ordinary flow control of the code being compiled. In particular, putting | |
8615 | a C<use> inside the false branch of a conditional doesn't prevent it | |
3b10bc60 | 8616 | from being processed. If a module or pragma only needs to be loaded |
c362798e Z |
8617 | conditionally, this can be done using the L<if> pragma: |
8618 | ||
8619 | use if $] < 5.008, "utf8"; | |
8620 | use if WANT_WARNINGS, warnings => qw(all); | |
8621 | ||
8f1da26d | 8622 | There's a corresponding C<no> declaration that unimports meanings imported |
19799a22 | 8623 | by C<use>, i.e., it calls C<unimport Module LIST> instead of C<import>. |
80d38338 TC |
8624 | It behaves just as C<import> does with VERSION, an omitted or empty LIST, |
8625 | or no unimport method being found. | |
a0d0e21e LW |
8626 | |
8627 | no integer; | |
8628 | no strict 'refs'; | |
4438c4b7 | 8629 | no warnings; |
a0d0e21e | 8630 | |
e0de7c21 | 8631 | Care should be taken when using the C<no VERSION> form of C<no>. It is |
8f1da26d | 8632 | I<only> meant to be used to assert that the running Perl is of a earlier |
e0de7c21 RS |
8633 | version than its argument and I<not> to undo the feature-enabling side effects |
8634 | of C<use VERSION>. | |
8635 | ||
ac634a9a | 8636 | See L<perlmodlib> for a list of standard modules and pragmas. See L<perlrun> |
3b10bc60 | 8637 | for the C<-M> and C<-m> command-line options to Perl that give C<use> |
31686daf | 8638 | functionality from the command-line. |
a0d0e21e LW |
8639 | |
8640 | =item utime LIST | |
d74e8afc | 8641 | X<utime> |
a0d0e21e | 8642 | |
c17cdb72 NC |
8643 | =for Pod::Functions set a file's last access and modify times |
8644 | ||
a0d0e21e | 8645 | Changes the access and modification times on each file of a list of |
8f1da26d | 8646 | files. The first two elements of the list must be the NUMERIC access |
a0d0e21e | 8647 | and modification times, in that order. Returns the number of files |
46cdf678 | 8648 | successfully changed. The inode change time of each file is set |
4bc2a53d | 8649 | to the current time. For example, this code has the same effect as the |
a4142048 WL |
8650 | Unix touch(1) command when the files I<already exist> and belong to |
8651 | the user running the program: | |
a0d0e21e LW |
8652 | |
8653 | #!/usr/bin/perl | |
2c21a326 GA |
8654 | $atime = $mtime = time; |
8655 | utime $atime, $mtime, @ARGV; | |
4bc2a53d | 8656 | |
e9fa405d | 8657 | Since Perl 5.8.0, if the first two elements of the list are C<undef>, |
3b10bc60 | 8658 | the utime(2) syscall from your C library is called with a null second |
391b733c | 8659 | argument. On most systems, this will set the file's access and |
80d38338 | 8660 | modification times to the current time (i.e., equivalent to the example |
3b10bc60 | 8661 | above) and will work even on files you don't own provided you have write |
a4142048 | 8662 | permission: |
c6f7b413 | 8663 | |
3b10bc60 | 8664 | for $file (@ARGV) { |
8665 | utime(undef, undef, $file) | |
8666 | || warn "couldn't touch $file: $!"; | |
8667 | } | |
c6f7b413 | 8668 | |
2c21a326 GA |
8669 | Under NFS this will use the time of the NFS server, not the time of |
8670 | the local machine. If there is a time synchronization problem, the | |
8671 | NFS server and local machine will have different times. The Unix | |
8672 | touch(1) command will in fact normally use this form instead of the | |
8673 | one shown in the first example. | |
8674 | ||
3b10bc60 | 8675 | Passing only one of the first two elements as C<undef> is |
8676 | equivalent to passing a 0 and will not have the effect | |
8677 | described when both are C<undef>. This also triggers an | |
2c21a326 GA |
8678 | uninitialized warning. |
8679 | ||
3b10bc60 | 8680 | On systems that support futimes(2), you may pass filehandles among the |
8681 | files. On systems that don't support futimes(2), passing filehandles raises | |
8682 | an exception. Filehandles must be passed as globs or glob references to be | |
8683 | recognized; barewords are considered filenames. | |
e96b369d | 8684 | |
ea9eb35a BJ |
8685 | Portability issues: L<perlport/utime>. |
8686 | ||
532eee96 | 8687 | =item values HASH |
d74e8afc | 8688 | X<values> |
a0d0e21e | 8689 | |
532eee96 | 8690 | =item values ARRAY |
aeedbbed | 8691 | |
f5a93a43 TC |
8692 | =item values EXPR |
8693 | ||
c17cdb72 NC |
8694 | =for Pod::Functions return a list of the values in a hash |
8695 | ||
bade7fbc TC |
8696 | In list context, returns a list consisting of all the values of the named |
8697 | hash. In Perl 5.12 or later only, will also return a list of the values of | |
8698 | an array; prior to that release, attempting to use an array argument will | |
8699 | produce a syntax error. In scalar context, returns the number of values. | |
504f80c1 | 8700 | |
7bf59113 YO |
8701 | Hash entries are returned in an apparently random order. The actual random |
8702 | order is specific to a given hash; the exact same series of operations | |
7161e5c2 | 8703 | on two hashes may result in a different order for each hash. Any insertion |
7bf59113 YO |
8704 | into the hash may change the order, as will any deletion, with the exception |
8705 | that the most recent key returned by C<each> or C<keys> may be deleted | |
7161e5c2 | 8706 | without changing the order. So long as a given hash is unmodified you may |
7bf59113 | 8707 | rely on C<keys>, C<values> and C<each> to repeatedly return the same order |
7161e5c2 FC |
8708 | as each other. See L<perlsec/"Algorithmic Complexity Attacks"> for |
8709 | details on why hash order is randomized. Aside from the guarantees | |
7bf59113 YO |
8710 | provided here the exact details of Perl's hash algorithm and the hash |
8711 | traversal order are subject to change in any release of Perl. | |
504f80c1 | 8712 | |
aeedbbed | 8713 | As a side effect, calling values() resets the HASH or ARRAY's internal |
391b733c FC |
8714 | iterator, see L</each>. (In particular, calling values() in void context |
8715 | resets the iterator with no other overhead. Apart from resetting the | |
bade7fbc TC |
8716 | iterator, C<values @array> in list context is the same as plain C<@array>. |
8717 | (We recommend that you use void context C<keys @array> for this, but | |
8718 | reasoned that taking C<values @array> out would require more | |
8719 | documentation than leaving it in.) | |
aeedbbed | 8720 | |
8ea1e5d4 GS |
8721 | Note that the values are not copied, which means modifying them will |
8722 | modify the contents of the hash: | |
2b5ab1e7 | 8723 | |
f7051f2c FC |
8724 | for (values %hash) { s/foo/bar/g } # modifies %hash values |
8725 | for (@hash{keys %hash}) { s/foo/bar/g } # same | |
2b5ab1e7 | 8726 | |
f5a93a43 TC |
8727 | Starting with Perl 5.14, C<values> can take a scalar EXPR, which must hold |
8728 | a reference to an unblessed hash or array. The argument will be | |
8729 | dereferenced automatically. This aspect of C<values> is considered highly | |
8730 | experimental. The exact behaviour may change in a future version of Perl. | |
cba5a3b0 DG |
8731 | |
8732 | for (values $hashref) { ... } | |
8733 | for (values $obj->get_arrayref) { ... } | |
8734 | ||
bade7fbc TC |
8735 | To avoid confusing would-be users of your code who are running earlier |
8736 | versions of Perl with mysterious syntax errors, put this sort of thing at | |
8737 | the top of your file to signal that your code will work I<only> on Perls of | |
8738 | a recent vintage: | |
8739 | ||
8740 | use 5.012; # so keys/values/each work on arrays | |
8741 | use 5.014; # so keys/values/each work on scalars (experimental) | |
8742 | ||
19799a22 | 8743 | See also C<keys>, C<each>, and C<sort>. |
a0d0e21e LW |
8744 | |
8745 | =item vec EXPR,OFFSET,BITS | |
d74e8afc | 8746 | X<vec> X<bit> X<bit vector> |
a0d0e21e | 8747 | |
c17cdb72 NC |
8748 | =for Pod::Functions test or set particular bits in a string |
8749 | ||
e69129f1 | 8750 | Treats the string in EXPR as a bit vector made up of elements of |
8f1da26d | 8751 | width BITS and returns the value of the element specified by OFFSET |
e69129f1 GS |
8752 | as an unsigned integer. BITS therefore specifies the number of bits |
8753 | that are reserved for each element in the bit vector. This must | |
8754 | be a power of two from 1 to 32 (or 64, if your platform supports | |
8755 | that). | |
c5a0f51a | 8756 | |
b76cc8ba | 8757 | If BITS is 8, "elements" coincide with bytes of the input string. |
c73032f5 IZ |
8758 | |
8759 | If BITS is 16 or more, bytes of the input string are grouped into chunks | |
8760 | of size BITS/8, and each group is converted to a number as with | |
b1866b2d | 8761 | pack()/unpack() with big-endian formats C<n>/C<N> (and analogously |
c73032f5 IZ |
8762 | for BITS==64). See L<"pack"> for details. |
8763 | ||
8764 | If bits is 4 or less, the string is broken into bytes, then the bits | |
8765 | of each byte are broken into 8/BITS groups. Bits of a byte are | |
8766 | numbered in a little-endian-ish way, as in C<0x01>, C<0x02>, | |
8767 | C<0x04>, C<0x08>, C<0x10>, C<0x20>, C<0x40>, C<0x80>. For example, | |
8768 | breaking the single input byte C<chr(0x36)> into two groups gives a list | |
8769 | C<(0x6, 0x3)>; breaking it into 4 groups gives C<(0x2, 0x1, 0x3, 0x0)>. | |
8770 | ||
81e118e0 JH |
8771 | C<vec> may also be assigned to, in which case parentheses are needed |
8772 | to give the expression the correct precedence as in | |
22dc801b | 8773 | |
8774 | vec($image, $max_x * $x + $y, 8) = 3; | |
a0d0e21e | 8775 | |
fe58ced6 MG |
8776 | If the selected element is outside the string, the value 0 is returned. |
8777 | If an element off the end of the string is written to, Perl will first | |
8778 | extend the string with sufficiently many zero bytes. It is an error | |
80d38338 | 8779 | to try to write off the beginning of the string (i.e., negative OFFSET). |
fac70343 | 8780 | |
2575c402 JW |
8781 | If the string happens to be encoded as UTF-8 internally (and thus has |
8782 | the UTF8 flag set), this is ignored by C<vec>, and it operates on the | |
8783 | internal byte string, not the conceptual character string, even if you | |
8784 | only have characters with values less than 256. | |
246fae53 | 8785 | |
fac70343 GS |
8786 | Strings created with C<vec> can also be manipulated with the logical |
8787 | operators C<|>, C<&>, C<^>, and C<~>. These operators will assume a bit | |
8788 | vector operation is desired when both operands are strings. | |
c5a0f51a | 8789 | See L<perlop/"Bitwise String Operators">. |
a0d0e21e | 8790 | |
7660c0ab | 8791 | The following code will build up an ASCII string saying C<'PerlPerlPerl'>. |
19799a22 | 8792 | The comments show the string after each step. Note that this code works |
cca87523 GS |
8793 | in the same way on big-endian or little-endian machines. |
8794 | ||
8795 | my $foo = ''; | |
5ed4f2ec | 8796 | vec($foo, 0, 32) = 0x5065726C; # 'Perl' |
e69129f1 GS |
8797 | |
8798 | # $foo eq "Perl" eq "\x50\x65\x72\x6C", 32 bits | |
5ed4f2ec | 8799 | print vec($foo, 0, 8); # prints 80 == 0x50 == ord('P') |
8800 | ||
8801 | vec($foo, 2, 16) = 0x5065; # 'PerlPe' | |
8802 | vec($foo, 3, 16) = 0x726C; # 'PerlPerl' | |
8803 | vec($foo, 8, 8) = 0x50; # 'PerlPerlP' | |
8804 | vec($foo, 9, 8) = 0x65; # 'PerlPerlPe' | |
8805 | vec($foo, 20, 4) = 2; # 'PerlPerlPe' . "\x02" | |
8806 | vec($foo, 21, 4) = 7; # 'PerlPerlPer' | |
8807 | # 'r' is "\x72" | |
8808 | vec($foo, 45, 2) = 3; # 'PerlPerlPer' . "\x0c" | |
8809 | vec($foo, 93, 1) = 1; # 'PerlPerlPer' . "\x2c" | |
8810 | vec($foo, 94, 1) = 1; # 'PerlPerlPerl' | |
8811 | # 'l' is "\x6c" | |
cca87523 | 8812 | |
19799a22 | 8813 | To transform a bit vector into a string or list of 0's and 1's, use these: |
a0d0e21e LW |
8814 | |
8815 | $bits = unpack("b*", $vector); | |
8816 | @bits = split(//, unpack("b*", $vector)); | |
8817 | ||
7660c0ab | 8818 | If you know the exact length in bits, it can be used in place of the C<*>. |
a0d0e21e | 8819 | |
e69129f1 GS |
8820 | Here is an example to illustrate how the bits actually fall in place: |
8821 | ||
f7051f2c FC |
8822 | #!/usr/bin/perl -wl |
8823 | ||
8824 | print <<'EOT'; | |
8825 | 0 1 2 3 | |
8826 | unpack("V",$_) 01234567890123456789012345678901 | |
8827 | ------------------------------------------------------------------ | |
8828 | EOT | |
8829 | ||
8830 | for $w (0..3) { | |
8831 | $width = 2**$w; | |
8832 | for ($shift=0; $shift < $width; ++$shift) { | |
8833 | for ($off=0; $off < 32/$width; ++$off) { | |
8834 | $str = pack("B*", "0"x32); | |
8835 | $bits = (1<<$shift); | |
8836 | vec($str, $off, $width) = $bits; | |
8837 | $res = unpack("b*",$str); | |
8838 | $val = unpack("V", $str); | |
8839 | write; | |
8840 | } | |
8841 | } | |
8842 | } | |
8843 | ||
8844 | format STDOUT = | |
8845 | vec($_,@#,@#) = @<< == @######### @>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> | |
8846 | $off, $width, $bits, $val, $res | |
8847 | . | |
8848 | __END__ | |
e69129f1 | 8849 | |
80d38338 TC |
8850 | Regardless of the machine architecture on which it runs, the |
8851 | example above should print the following table: | |
e69129f1 | 8852 | |
f7051f2c FC |
8853 | 0 1 2 3 |
8854 | unpack("V",$_) 01234567890123456789012345678901 | |
8855 | ------------------------------------------------------------------ | |
8856 | vec($_, 0, 1) = 1 == 1 10000000000000000000000000000000 | |
8857 | vec($_, 1, 1) = 1 == 2 01000000000000000000000000000000 | |
8858 | vec($_, 2, 1) = 1 == 4 00100000000000000000000000000000 | |
8859 | vec($_, 3, 1) = 1 == 8 00010000000000000000000000000000 | |
8860 | vec($_, 4, 1) = 1 == 16 00001000000000000000000000000000 | |
8861 | vec($_, 5, 1) = 1 == 32 00000100000000000000000000000000 | |
8862 | vec($_, 6, 1) = 1 == 64 00000010000000000000000000000000 | |
8863 | vec($_, 7, 1) = 1 == 128 00000001000000000000000000000000 | |
8864 | vec($_, 8, 1) = 1 == 256 00000000100000000000000000000000 | |
8865 | vec($_, 9, 1) = 1 == 512 00000000010000000000000000000000 | |
8866 | vec($_,10, 1) = 1 == 1024 00000000001000000000000000000000 | |
8867 | vec($_,11, 1) = 1 == 2048 00000000000100000000000000000000 | |
8868 | vec($_,12, 1) = 1 == 4096 00000000000010000000000000000000 | |
8869 | vec($_,13, 1) = 1 == 8192 00000000000001000000000000000000 | |
8870 | vec($_,14, 1) = 1 == 16384 00000000000000100000000000000000 | |
8871 | vec($_,15, 1) = 1 == 32768 00000000000000010000000000000000 | |
8872 | vec($_,16, 1) = 1 == 65536 00000000000000001000000000000000 | |
8873 | vec($_,17, 1) = 1 == 131072 00000000000000000100000000000000 | |
8874 | vec($_,18, 1) = 1 == 262144 00000000000000000010000000000000 | |
8875 | vec($_,19, 1) = 1 == 524288 00000000000000000001000000000000 | |
8876 | vec($_,20, 1) = 1 == 1048576 00000000000000000000100000000000 | |
8877 | vec($_,21, 1) = 1 == 2097152 00000000000000000000010000000000 | |
8878 | vec($_,22, 1) = 1 == 4194304 00000000000000000000001000000000 | |
8879 | vec($_,23, 1) = 1 == 8388608 00000000000000000000000100000000 | |
8880 | vec($_,24, 1) = 1 == 16777216 00000000000000000000000010000000 | |
8881 | vec($_,25, 1) = 1 == 33554432 00000000000000000000000001000000 | |
8882 | vec($_,26, 1) = 1 == 67108864 00000000000000000000000000100000 | |
8883 | vec($_,27, 1) = 1 == 134217728 00000000000000000000000000010000 | |
8884 | vec($_,28, 1) = 1 == 268435456 00000000000000000000000000001000 | |
8885 | vec($_,29, 1) = 1 == 536870912 00000000000000000000000000000100 | |
8886 | vec($_,30, 1) = 1 == 1073741824 00000000000000000000000000000010 | |
8887 | vec($_,31, 1) = 1 == 2147483648 00000000000000000000000000000001 | |
8888 | vec($_, 0, 2) = 1 == 1 10000000000000000000000000000000 | |
8889 | vec($_, 1, 2) = 1 == 4 00100000000000000000000000000000 | |
8890 | vec($_, 2, 2) = 1 == 16 00001000000000000000000000000000 | |
8891 | vec($_, 3, 2) = 1 == 64 00000010000000000000000000000000 | |
8892 | vec($_, 4, 2) = 1 == 256 00000000100000000000000000000000 | |
8893 | vec($_, 5, 2) = 1 == 1024 00000000001000000000000000000000 | |
8894 | vec($_, 6, 2) = 1 == 4096 00000000000010000000000000000000 | |
8895 | vec($_, 7, 2) = 1 == 16384 00000000000000100000000000000000 | |
8896 | vec($_, 8, 2) = 1 == 65536 00000000000000001000000000000000 | |
8897 | vec($_, 9, 2) = 1 == 262144 00000000000000000010000000000000 | |
8898 | vec($_,10, 2) = 1 == 1048576 00000000000000000000100000000000 | |
8899 | vec($_,11, 2) = 1 == 4194304 00000000000000000000001000000000 | |
8900 | vec($_,12, 2) = 1 == 16777216 00000000000000000000000010000000 | |
8901 | vec($_,13, 2) = 1 == 67108864 00000000000000000000000000100000 | |
8902 | vec($_,14, 2) = 1 == 268435456 00000000000000000000000000001000 | |
8903 | vec($_,15, 2) = 1 == 1073741824 00000000000000000000000000000010 | |
8904 | vec($_, 0, 2) = 2 == 2 01000000000000000000000000000000 | |
8905 | vec($_, 1, 2) = 2 == 8 00010000000000000000000000000000 | |
8906 | vec($_, 2, 2) = 2 == 32 00000100000000000000000000000000 | |
8907 | vec($_, 3, 2) = 2 == 128 00000001000000000000000000000000 | |
8908 | vec($_, 4, 2) = 2 == 512 00000000010000000000000000000000 | |
8909 | vec($_, 5, 2) = 2 == 2048 00000000000100000000000000000000 | |
8910 | vec($_, 6, 2) = 2 == 8192 00000000000001000000000000000000 | |
8911 | vec($_, 7, 2) = 2 == 32768 00000000000000010000000000000000 | |
8912 | vec($_, 8, 2) = 2 == 131072 00000000000000000100000000000000 | |
8913 | vec($_, 9, 2) = 2 == 524288 00000000000000000001000000000000 | |
8914 | vec($_,10, 2) = 2 == 2097152 00000000000000000000010000000000 | |
8915 | vec($_,11, 2) = 2 == 8388608 00000000000000000000000100000000 | |
8916 | vec($_,12, 2) = 2 == 33554432 00000000000000000000000001000000 | |
8917 | vec($_,13, 2) = 2 == 134217728 00000000000000000000000000010000 | |
8918 | vec($_,14, 2) = 2 == 536870912 00000000000000000000000000000100 | |
8919 | vec($_,15, 2) = 2 == 2147483648 00000000000000000000000000000001 | |
8920 | vec($_, 0, 4) = 1 == 1 10000000000000000000000000000000 | |
8921 | vec($_, 1, 4) = 1 == 16 00001000000000000000000000000000 | |
8922 | vec($_, 2, 4) = 1 == 256 00000000100000000000000000000000 | |
8923 | vec($_, 3, 4) = 1 == 4096 00000000000010000000000000000000 | |
8924 | vec($_, 4, 4) = 1 == 65536 00000000000000001000000000000000 | |
8925 | vec($_, 5, 4) = 1 == 1048576 00000000000000000000100000000000 | |
8926 | vec($_, 6, 4) = 1 == 16777216 00000000000000000000000010000000 | |
8927 | vec($_, 7, 4) = 1 == 268435456 00000000000000000000000000001000 | |
8928 | vec($_, 0, 4) = 2 == 2 01000000000000000000000000000000 | |
8929 | vec($_, 1, 4) = 2 == 32 00000100000000000000000000000000 | |
8930 | vec($_, 2, 4) = 2 == 512 00000000010000000000000000000000 | |
8931 | vec($_, 3, 4) = 2 == 8192 00000000000001000000000000000000 | |
8932 | vec($_, 4, 4) = 2 == 131072 00000000000000000100000000000000 | |
8933 | vec($_, 5, 4) = 2 == 2097152 00000000000000000000010000000000 | |
8934 | vec($_, 6, 4) = 2 == 33554432 00000000000000000000000001000000 | |
8935 | vec($_, 7, 4) = 2 == 536870912 00000000000000000000000000000100 | |
8936 | vec($_, 0, 4) = 4 == 4 00100000000000000000000000000000 | |
8937 | vec($_, 1, 4) = 4 == 64 00000010000000000000000000000000 | |
8938 | vec($_, 2, 4) = 4 == 1024 00000000001000000000000000000000 | |
8939 | vec($_, 3, 4) = 4 == 16384 00000000000000100000000000000000 | |
8940 | vec($_, 4, 4) = 4 == 262144 00000000000000000010000000000000 | |
8941 | vec($_, 5, 4) = 4 == 4194304 00000000000000000000001000000000 | |
8942 | vec($_, 6, 4) = 4 == 67108864 00000000000000000000000000100000 | |
8943 | vec($_, 7, 4) = 4 == 1073741824 00000000000000000000000000000010 | |
8944 | vec($_, 0, 4) = 8 == 8 00010000000000000000000000000000 | |
8945 | vec($_, 1, 4) = 8 == 128 00000001000000000000000000000000 | |
8946 | vec($_, 2, 4) = 8 == 2048 00000000000100000000000000000000 | |
8947 | vec($_, 3, 4) = 8 == 32768 00000000000000010000000000000000 | |
8948 | vec($_, 4, 4) = 8 == 524288 00000000000000000001000000000000 | |
8949 | vec($_, 5, 4) = 8 == 8388608 00000000000000000000000100000000 | |
8950 | vec($_, 6, 4) = 8 == 134217728 00000000000000000000000000010000 | |
8951 | vec($_, 7, 4) = 8 == 2147483648 00000000000000000000000000000001 | |
8952 | vec($_, 0, 8) = 1 == 1 10000000000000000000000000000000 | |
8953 | vec($_, 1, 8) = 1 == 256 00000000100000000000000000000000 | |
8954 | vec($_, 2, 8) = 1 == 65536 00000000000000001000000000000000 | |
8955 | vec($_, 3, 8) = 1 == 16777216 00000000000000000000000010000000 | |
8956 | vec($_, 0, 8) = 2 == 2 01000000000000000000000000000000 | |
8957 | vec($_, 1, 8) = 2 == 512 00000000010000000000000000000000 | |
8958 | vec($_, 2, 8) = 2 == 131072 00000000000000000100000000000000 | |
8959 | vec($_, 3, 8) = 2 == 33554432 00000000000000000000000001000000 | |
8960 | vec($_, 0, 8) = 4 == 4 00100000000000000000000000000000 | |
8961 | vec($_, 1, 8) = 4 == 1024 00000000001000000000000000000000 | |
8962 | vec($_, 2, 8) = 4 == 262144 00000000000000000010000000000000 | |
8963 | vec($_, 3, 8) = 4 == 67108864 00000000000000000000000000100000 | |
8964 | vec($_, 0, 8) = 8 == 8 00010000000000000000000000000000 | |
8965 | vec($_, 1, 8) = 8 == 2048 00000000000100000000000000000000 | |
8966 | vec($_, 2, 8) = 8 == 524288 00000000000000000001000000000000 | |
8967 | vec($_, 3, 8) = 8 == 134217728 00000000000000000000000000010000 | |
8968 | vec($_, 0, 8) = 16 == 16 00001000000000000000000000000000 | |
8969 | vec($_, 1, 8) = 16 == 4096 00000000000010000000000000000000 | |
8970 | vec($_, 2, 8) = 16 == 1048576 00000000000000000000100000000000 | |
8971 | vec($_, 3, 8) = 16 == 268435456 00000000000000000000000000001000 | |
8972 | vec($_, 0, 8) = 32 == 32 00000100000000000000000000000000 | |
8973 | vec($_, 1, 8) = 32 == 8192 00000000000001000000000000000000 | |
8974 | vec($_, 2, 8) = 32 == 2097152 00000000000000000000010000000000 | |
8975 | vec($_, 3, 8) = 32 == 536870912 00000000000000000000000000000100 | |
8976 | vec($_, 0, 8) = 64 == 64 00000010000000000000000000000000 | |
8977 | vec($_, 1, 8) = 64 == 16384 00000000000000100000000000000000 | |
8978 | vec($_, 2, 8) = 64 == 4194304 00000000000000000000001000000000 | |
8979 | vec($_, 3, 8) = 64 == 1073741824 00000000000000000000000000000010 | |
8980 | vec($_, 0, 8) = 128 == 128 00000001000000000000000000000000 | |
8981 | vec($_, 1, 8) = 128 == 32768 00000000000000010000000000000000 | |
8982 | vec($_, 2, 8) = 128 == 8388608 00000000000000000000000100000000 | |
8983 | vec($_, 3, 8) = 128 == 2147483648 00000000000000000000000000000001 | |
e69129f1 | 8984 | |
a0d0e21e | 8985 | =item wait |
d74e8afc | 8986 | X<wait> |
a0d0e21e | 8987 | |
c17cdb72 NC |
8988 | =for Pod::Functions wait for any child process to die |
8989 | ||
3b10bc60 | 8990 | Behaves like wait(2) on your system: it waits for a child |
2b5ab1e7 | 8991 | process to terminate and returns the pid of the deceased process, or |
e5218da5 | 8992 | C<-1> if there are no child processes. The status is returned in C<$?> |
ca8d723e | 8993 | and C<${^CHILD_ERROR_NATIVE}>. |
2b5ab1e7 TC |
8994 | Note that a return value of C<-1> could mean that child processes are |
8995 | being automatically reaped, as described in L<perlipc>. | |
a0d0e21e | 8996 | |
c69ca1d4 | 8997 | If you use wait in your handler for $SIG{CHLD} it may accidentally for the |
391b733c | 8998 | child created by qx() or system(). See L<perlipc> for details. |
0a18a49b | 8999 | |
ea9eb35a BJ |
9000 | Portability issues: L<perlport/wait>. |
9001 | ||
a0d0e21e | 9002 | =item waitpid PID,FLAGS |
d74e8afc | 9003 | X<waitpid> |
a0d0e21e | 9004 | |
2a364e7e | 9005 | =for Pod::Functions wait for a particular child process to die |
c17cdb72 | 9006 | |
2b5ab1e7 TC |
9007 | Waits for a particular child process to terminate and returns the pid of |
9008 | the deceased process, or C<-1> if there is no such child process. On some | |
9009 | systems, a value of 0 indicates that there are processes still running. | |
ca8d723e | 9010 | The status is returned in C<$?> and C<${^CHILD_ERROR_NATIVE}>. If you say |
a0d0e21e | 9011 | |
5f05dabc | 9012 | use POSIX ":sys_wait_h"; |
5a964f20 | 9013 | #... |
b76cc8ba | 9014 | do { |
a9a5a0dc | 9015 | $kid = waitpid(-1, WNOHANG); |
84b74420 | 9016 | } while $kid > 0; |
a0d0e21e | 9017 | |
2b5ab1e7 TC |
9018 | then you can do a non-blocking wait for all pending zombie processes. |
9019 | Non-blocking wait is available on machines supporting either the | |
3b10bc60 | 9020 | waitpid(2) or wait4(2) syscalls. However, waiting for a particular |
2b5ab1e7 TC |
9021 | pid with FLAGS of C<0> is implemented everywhere. (Perl emulates the |
9022 | system call by remembering the status values of processes that have | |
9023 | exited but have not been harvested by the Perl script yet.) | |
a0d0e21e | 9024 | |
2b5ab1e7 TC |
9025 | Note that on some systems, a return value of C<-1> could mean that child |
9026 | processes are being automatically reaped. See L<perlipc> for details, | |
9027 | and for other examples. | |
5a964f20 | 9028 | |
ea9eb35a BJ |
9029 | Portability issues: L<perlport/waitpid>. |
9030 | ||
a0d0e21e | 9031 | =item wantarray |
d74e8afc | 9032 | X<wantarray> X<context> |
a0d0e21e | 9033 | |
c17cdb72 NC |
9034 | =for Pod::Functions get void vs scalar vs list context of current subroutine call |
9035 | ||
cc37eb0b | 9036 | Returns true if the context of the currently executing subroutine or |
20f13e4a | 9037 | C<eval> is looking for a list value. Returns false if the context is |
cc37eb0b RGS |
9038 | looking for a scalar. Returns the undefined value if the context is |
9039 | looking for no value (void context). | |
a0d0e21e | 9040 | |
5ed4f2ec | 9041 | return unless defined wantarray; # don't bother doing more |
54310121 | 9042 | my @a = complex_calculation(); |
9043 | return wantarray ? @a : "@a"; | |
a0d0e21e | 9044 | |
20f13e4a | 9045 | C<wantarray()>'s result is unspecified in the top level of a file, |
3c10abe3 AG |
9046 | in a C<BEGIN>, C<UNITCHECK>, C<CHECK>, C<INIT> or C<END> block, or |
9047 | in a C<DESTROY> method. | |
20f13e4a | 9048 | |
19799a22 GS |
9049 | This function should have been named wantlist() instead. |
9050 | ||
a0d0e21e | 9051 | =item warn LIST |
d74e8afc | 9052 | X<warn> X<warning> X<STDERR> |
a0d0e21e | 9053 | |
c17cdb72 NC |
9054 | =for Pod::Functions print debugging info |
9055 | ||
2d6d0015 | 9056 | Prints the value of LIST to STDERR. If the last element of LIST does |
afd8c9c8 DM |
9057 | not end in a newline, it appends the same file/line number text as C<die> |
9058 | does. | |
774d564b | 9059 | |
a96d0188 | 9060 | If the output is empty and C<$@> already contains a value (typically from a |
7660c0ab | 9061 | previous eval) that value is used after appending C<"\t...caught"> |
19799a22 GS |
9062 | to C<$@>. This is useful for staying almost, but not entirely similar to |
9063 | C<die>. | |
43051805 | 9064 | |
7660c0ab | 9065 | If C<$@> is empty then the string C<"Warning: Something's wrong"> is used. |
43051805 | 9066 | |
774d564b | 9067 | No message is printed if there is a C<$SIG{__WARN__}> handler |
9068 | installed. It is the handler's responsibility to deal with the message | |
19799a22 | 9069 | as it sees fit (like, for instance, converting it into a C<die>). Most |
80d38338 | 9070 | handlers must therefore arrange to actually display the |
19799a22 | 9071 | warnings that they are not prepared to deal with, by calling C<warn> |
774d564b | 9072 | again in the handler. Note that this is quite safe and will not |
9073 | produce an endless loop, since C<__WARN__> hooks are not called from | |
9074 | inside one. | |
9075 | ||
9076 | You will find this behavior is slightly different from that of | |
9077 | C<$SIG{__DIE__}> handlers (which don't suppress the error text, but can | |
19799a22 | 9078 | instead call C<die> again to change it). |
774d564b | 9079 | |
9080 | Using a C<__WARN__> handler provides a powerful way to silence all | |
9081 | warnings (even the so-called mandatory ones). An example: | |
9082 | ||
9083 | # wipe out *all* compile-time warnings | |
9084 | BEGIN { $SIG{'__WARN__'} = sub { warn $_[0] if $DOWARN } } | |
9085 | my $foo = 10; | |
9086 | my $foo = 20; # no warning about duplicate my $foo, | |
9087 | # but hey, you asked for it! | |
9088 | # no compile-time or run-time warnings before here | |
9089 | $DOWARN = 1; | |
9090 | ||
9091 | # run-time warnings enabled after here | |
9092 | warn "\$foo is alive and $foo!"; # does show up | |
9093 | ||
8f1da26d | 9094 | See L<perlvar> for details on setting C<%SIG> entries and for more |
2b5ab1e7 TC |
9095 | examples. See the Carp module for other kinds of warnings using its |
9096 | carp() and cluck() functions. | |
a0d0e21e LW |
9097 | |
9098 | =item write FILEHANDLE | |
d74e8afc | 9099 | X<write> |
a0d0e21e LW |
9100 | |
9101 | =item write EXPR | |
9102 | ||
9103 | =item write | |
9104 | ||
c17cdb72 NC |
9105 | =for Pod::Functions print a picture record |
9106 | ||
5a964f20 | 9107 | Writes a formatted record (possibly multi-line) to the specified FILEHANDLE, |
a0d0e21e | 9108 | using the format associated with that file. By default the format for |
54310121 | 9109 | a file is the one having the same name as the filehandle, but the |
19799a22 | 9110 | format for the current output channel (see the C<select> function) may be set |
184e9718 | 9111 | explicitly by assigning the name of the format to the C<$~> variable. |
a0d0e21e | 9112 | |
8f1da26d TC |
9113 | Top of form processing is handled automatically: if there is insufficient |
9114 | room on the current page for the formatted record, the page is advanced by | |
dbaf95ac FC |
9115 | writing a form feed and a special top-of-page |
9116 | format is used to format the new | |
8f1da26d | 9117 | page header before the record is written. By default, the top-of-page |
dbaf95ac FC |
9118 | format is the name of the filehandle with "_TOP" appended, or "top" |
9119 | in the current package if the former does not exist. This would be a | |
8f1da26d TC |
9120 | problem with autovivified filehandles, but it may be dynamically set to the |
9121 | format of your choice by assigning the name to the C<$^> variable while | |
9122 | that filehandle is selected. The number of lines remaining on the current | |
9123 | page is in variable C<$->, which can be set to C<0> to force a new page. | |
a0d0e21e LW |
9124 | |
9125 | If FILEHANDLE is unspecified, output goes to the current default output | |
9126 | channel, which starts out as STDOUT but may be changed by the | |
19799a22 | 9127 | C<select> operator. If the FILEHANDLE is an EXPR, then the expression |
a0d0e21e LW |
9128 | is evaluated and the resulting string is used to look up the name of |
9129 | the FILEHANDLE at run time. For more on formats, see L<perlform>. | |
9130 | ||
19799a22 | 9131 | Note that write is I<not> the opposite of C<read>. Unfortunately. |
a0d0e21e LW |
9132 | |
9133 | =item y/// | |
9134 | ||
c17cdb72 NC |
9135 | =for Pod::Functions transliterate a string |
9136 | ||
9f4b9cd0 | 9137 | The transliteration operator. Same as C<tr///>. See |
cdf6c183 | 9138 | L<perlop/"Quote-Like Operators">. |
a0d0e21e LW |
9139 | |
9140 | =back | |
8f1da26d | 9141 | |
8f0d6a61 RS |
9142 | =head2 Non-function Keywords by Cross-reference |
9143 | ||
1336785e RS |
9144 | =head3 perldata |
9145 | ||
9146 | =over | |
9147 | ||
9148 | =item __DATA__ | |
9149 | ||
9150 | =item __END__ | |
9151 | ||
de9ddc26 | 9152 | These keywords are documented in L<perldata/"Special Literals">. |
1336785e RS |
9153 | |
9154 | =back | |
9155 | ||
9156 | =head3 perlmod | |
9157 | ||
9158 | =over | |
9159 | ||
9160 | =item BEGIN | |
9161 | ||
9162 | =item CHECK | |
9163 | ||
1336785e RS |
9164 | =item END |
9165 | ||
9166 | =item INIT | |
9167 | ||
9168 | =item UNITCHECK | |
9169 | ||
de9ddc26 | 9170 | These compile phase keywords are documented in L<perlmod/"BEGIN, UNITCHECK, CHECK, INIT and END">. |
1336785e RS |
9171 | |
9172 | =back | |
9173 | ||
081753c8 NC |
9174 | =head3 perlobj |
9175 | ||
9176 | =over | |
9177 | ||
9178 | =item DESTROY | |
9179 | ||
de9ddc26 | 9180 | This method keyword is documented in L<perlobj/"Destructors">. |
081753c8 NC |
9181 | |
9182 | =back | |
9183 | ||
8f0d6a61 RS |
9184 | =head3 perlop |
9185 | ||
9186 | =over | |
9187 | ||
9188 | =item and | |
9189 | ||
9190 | =item cmp | |
9191 | ||
9192 | =item eq | |
9193 | ||
9194 | =item ge | |
9195 | ||
9196 | =item gt | |
9197 | ||
8f0d6a61 RS |
9198 | =item le |
9199 | ||
9200 | =item lt | |
9201 | ||
9202 | =item ne | |
9203 | ||
9204 | =item not | |
9205 | ||
9206 | =item or | |
9207 | ||
9208 | =item x | |
9209 | ||
9210 | =item xor | |
9211 | ||
9212 | These operators are documented in L<perlop>. | |
9213 | ||
9214 | =back | |
9215 | ||
1336785e RS |
9216 | =head3 perlsub |
9217 | ||
9218 | =over | |
9219 | ||
9220 | =item AUTOLOAD | |
9221 | ||
de9ddc26 | 9222 | This keyword is documented in L<perlsub/"Autoloading">. |
1336785e RS |
9223 | |
9224 | =back | |
9225 | ||
41cf8e73 | 9226 | =head3 perlsyn |
8f0d6a61 RS |
9227 | |
9228 | =over | |
9229 | ||
9230 | =item else | |
9231 | ||
9232 | =item elseif | |
9233 | ||
9234 | =item elsif | |
9235 | ||
9236 | =item for | |
9237 | ||
9238 | =item foreach | |
9239 | ||
21f8b926 KW |
9240 | =item if |
9241 | ||
8f0d6a61 RS |
9242 | =item unless |
9243 | ||
9244 | =item until | |
9245 | ||
9246 | =item while | |
9247 | ||
de9ddc26 | 9248 | These flow-control keywords are documented in L<perlsyn/"Compound Statements">. |
8f0d6a61 RS |
9249 | |
9250 | =back | |
9251 | ||
dba7b065 NC |
9252 | =over |
9253 | ||
9254 | =item default | |
9255 | ||
9256 | =item given | |
9257 | ||
9258 | =item when | |
9259 | ||
9260 | These flow-control keywords related to the experimental switch feature are | |
2248d90c | 9261 | documented in L<perlsyn/"Switch Statements">. |
dba7b065 NC |
9262 | |
9263 | =back | |
9264 | ||
8f1da26d | 9265 | =cut |