Commit | Line | Data |
---|---|---|
a0d0e21e LW |
1 | =head1 NAME |
2 | ||
3 | perlfunc - Perl builtin functions | |
4 | ||
5 | =head1 DESCRIPTION | |
6 | ||
7 | The functions in this section can serve as terms in an expression. | |
8 | They fall into two major categories: list operators and named unary | |
9 | operators. These differ in their precedence relationship with a | |
10 | following comma. (See the precedence table in L<perlop>.) List | |
11 | operators take more than one argument, while unary operators can never | |
12 | take more than one argument. Thus, a comma terminates the argument of | |
13 | a unary operator, but merely separates the arguments of a list | |
14 | operator. A unary operator generally provides a scalar context to its | |
2b5ab1e7 | 15 | argument, while a list operator may provide either scalar or list |
a0d0e21e | 16 | contexts for its arguments. If it does both, the scalar arguments will |
5f05dabc | 17 | be first, and the list argument will follow. (Note that there can ever |
0f31cffe | 18 | be only one such list argument.) For instance, splice() has three scalar |
2b5ab1e7 TC |
19 | arguments followed by a list, whereas gethostbyname() has four scalar |
20 | arguments. | |
a0d0e21e LW |
21 | |
22 | In the syntax descriptions that follow, list operators that expect a | |
23 | list (and provide list context for the elements of the list) are shown | |
24 | with LIST as an argument. Such a list may consist of any combination | |
25 | of scalar arguments or list values; the list values will be included | |
26 | in the list as if each individual element were interpolated at that | |
27 | point in the list, forming a longer single-dimensional list value. | |
28 | Elements of the LIST should be separated by commas. | |
29 | ||
30 | Any function in the list below may be used either with or without | |
31 | parentheses around its arguments. (The syntax descriptions omit the | |
5f05dabc | 32 | parentheses.) If you use the parentheses, the simple (but occasionally |
19799a22 | 33 | surprising) rule is this: It I<looks> like a function, therefore it I<is> a |
a0d0e21e LW |
34 | function, and precedence doesn't matter. Otherwise it's a list |
35 | operator or unary operator, and precedence does matter. And whitespace | |
36 | between the function and left parenthesis doesn't count--so you need to | |
37 | be careful sometimes: | |
38 | ||
68dc0745 | 39 | print 1+2+4; # Prints 7. |
40 | print(1+2) + 4; # Prints 3. | |
41 | print (1+2)+4; # Also prints 3! | |
42 | print +(1+2)+4; # Prints 7. | |
43 | print ((1+2)+4); # Prints 7. | |
a0d0e21e LW |
44 | |
45 | If you run Perl with the B<-w> switch it can warn you about this. For | |
46 | example, the third line above produces: | |
47 | ||
48 | print (...) interpreted as function at - line 1. | |
49 | Useless use of integer addition in void context at - line 1. | |
50 | ||
2b5ab1e7 TC |
51 | A few functions take no arguments at all, and therefore work as neither |
52 | unary nor list operators. These include such functions as C<time> | |
53 | and C<endpwent>. For example, C<time+86_400> always means | |
54 | C<time() + 86_400>. | |
55 | ||
a0d0e21e | 56 | For functions that can be used in either a scalar or list context, |
54310121 | 57 | nonabortive failure is generally indicated in a scalar context by |
a0d0e21e LW |
58 | returning the undefined value, and in a list context by returning the |
59 | null list. | |
60 | ||
5a964f20 TC |
61 | Remember the following important rule: There is B<no rule> that relates |
62 | the behavior of an expression in list context to its behavior in scalar | |
63 | context, or vice versa. It might do two totally different things. | |
a0d0e21e | 64 | Each operator and function decides which sort of value it would be most |
2b5ab1e7 | 65 | appropriate to return in scalar context. Some operators return the |
5a964f20 | 66 | length of the list that would have been returned in list context. Some |
a0d0e21e LW |
67 | operators return the first value in the list. Some operators return the |
68 | last value in the list. Some operators return a count of successful | |
69 | operations. In general, they do what you want, unless you want | |
70 | consistency. | |
71 | ||
d1be9408 | 72 | A named array in scalar context is quite different from what would at |
5a964f20 TC |
73 | first glance appear to be a list in scalar context. You can't get a list |
74 | like C<(1,2,3)> into being in scalar context, because the compiler knows | |
75 | the context at compile time. It would generate the scalar comma operator | |
76 | there, not the list construction version of the comma. That means it | |
77 | was never a list to start with. | |
78 | ||
79 | In general, functions in Perl that serve as wrappers for system calls | |
f86cebdf | 80 | of the same name (like chown(2), fork(2), closedir(2), etc.) all return |
5a964f20 TC |
81 | true when they succeed and C<undef> otherwise, as is usually mentioned |
82 | in the descriptions below. This is different from the C interfaces, | |
19799a22 GS |
83 | which return C<-1> on failure. Exceptions to this rule are C<wait>, |
84 | C<waitpid>, and C<syscall>. System calls also set the special C<$!> | |
5a964f20 TC |
85 | variable on failure. Other functions do not, except accidentally. |
86 | ||
cb1a09d0 AD |
87 | =head2 Perl Functions by Category |
88 | ||
89 | Here are Perl's functions (including things that look like | |
5a964f20 | 90 | functions, like some keywords and named operators) |
cb1a09d0 AD |
91 | arranged by category. Some functions appear in more |
92 | than one place. | |
93 | ||
13a2d996 | 94 | =over 4 |
cb1a09d0 AD |
95 | |
96 | =item Functions for SCALARs or strings | |
97 | ||
22fae026 | 98 | C<chomp>, C<chop>, C<chr>, C<crypt>, C<hex>, C<index>, C<lc>, C<lcfirst>, |
945c54fd JH |
99 | C<length>, C<oct>, C<ord>, C<pack>, C<q/STRING/>, C<qq/STRING/>, C<reverse>, |
100 | C<rindex>, C<sprintf>, C<substr>, C<tr///>, C<uc>, C<ucfirst>, C<y///> | |
cb1a09d0 AD |
101 | |
102 | =item Regular expressions and pattern matching | |
103 | ||
ab4f32c2 | 104 | C<m//>, C<pos>, C<quotemeta>, C<s///>, C<split>, C<study>, C<qr//> |
cb1a09d0 AD |
105 | |
106 | =item Numeric functions | |
107 | ||
22fae026 TM |
108 | C<abs>, C<atan2>, C<cos>, C<exp>, C<hex>, C<int>, C<log>, C<oct>, C<rand>, |
109 | C<sin>, C<sqrt>, C<srand> | |
cb1a09d0 AD |
110 | |
111 | =item Functions for real @ARRAYs | |
112 | ||
22fae026 | 113 | C<pop>, C<push>, C<shift>, C<splice>, C<unshift> |
cb1a09d0 AD |
114 | |
115 | =item Functions for list data | |
116 | ||
ab4f32c2 | 117 | C<grep>, C<join>, C<map>, C<qw/STRING/>, C<reverse>, C<sort>, C<unpack> |
cb1a09d0 AD |
118 | |
119 | =item Functions for real %HASHes | |
120 | ||
22fae026 | 121 | C<delete>, C<each>, C<exists>, C<keys>, C<values> |
cb1a09d0 AD |
122 | |
123 | =item Input and output functions | |
124 | ||
22fae026 TM |
125 | C<binmode>, C<close>, C<closedir>, C<dbmclose>, C<dbmopen>, C<die>, C<eof>, |
126 | C<fileno>, C<flock>, C<format>, C<getc>, C<print>, C<printf>, C<read>, | |
127 | C<readdir>, C<rewinddir>, C<seek>, C<seekdir>, C<select>, C<syscall>, | |
128 | C<sysread>, C<sysseek>, C<syswrite>, C<tell>, C<telldir>, C<truncate>, | |
129 | C<warn>, C<write> | |
cb1a09d0 AD |
130 | |
131 | =item Functions for fixed length data or records | |
132 | ||
22fae026 | 133 | C<pack>, C<read>, C<syscall>, C<sysread>, C<syswrite>, C<unpack>, C<vec> |
cb1a09d0 AD |
134 | |
135 | =item Functions for filehandles, files, or directories | |
136 | ||
22fae026 | 137 | C<-I<X>>, C<chdir>, C<chmod>, C<chown>, C<chroot>, C<fcntl>, C<glob>, |
5ff3f7a4 | 138 | C<ioctl>, C<link>, C<lstat>, C<mkdir>, C<open>, C<opendir>, |
1e278fd9 JH |
139 | C<readlink>, C<rename>, C<rmdir>, C<stat>, C<symlink>, C<sysopen>, |
140 | C<umask>, C<unlink>, C<utime> | |
cb1a09d0 AD |
141 | |
142 | =item Keywords related to the control flow of your perl program | |
143 | ||
98293880 JH |
144 | C<caller>, C<continue>, C<die>, C<do>, C<dump>, C<eval>, C<exit>, |
145 | C<goto>, C<last>, C<next>, C<redo>, C<return>, C<sub>, C<wantarray> | |
cb1a09d0 | 146 | |
54310121 | 147 | =item Keywords related to scoping |
cb1a09d0 | 148 | |
4375e838 | 149 | C<caller>, C<import>, C<local>, C<my>, C<our>, C<package>, C<use> |
cb1a09d0 AD |
150 | |
151 | =item Miscellaneous functions | |
152 | ||
4375e838 | 153 | C<defined>, C<dump>, C<eval>, C<formline>, C<local>, C<my>, C<our>, C<reset>, |
22fae026 | 154 | C<scalar>, C<undef>, C<wantarray> |
cb1a09d0 AD |
155 | |
156 | =item Functions for processes and process groups | |
157 | ||
22fae026 | 158 | C<alarm>, C<exec>, C<fork>, C<getpgrp>, C<getppid>, C<getpriority>, C<kill>, |
ab4f32c2 | 159 | C<pipe>, C<qx/STRING/>, C<setpgrp>, C<setpriority>, C<sleep>, C<system>, |
22fae026 | 160 | C<times>, C<wait>, C<waitpid> |
cb1a09d0 AD |
161 | |
162 | =item Keywords related to perl modules | |
163 | ||
22fae026 | 164 | C<do>, C<import>, C<no>, C<package>, C<require>, C<use> |
cb1a09d0 AD |
165 | |
166 | =item Keywords related to classes and object-orientedness | |
167 | ||
22fae026 TM |
168 | C<bless>, C<dbmclose>, C<dbmopen>, C<package>, C<ref>, C<tie>, C<tied>, |
169 | C<untie>, C<use> | |
cb1a09d0 AD |
170 | |
171 | =item Low-level socket functions | |
172 | ||
22fae026 TM |
173 | C<accept>, C<bind>, C<connect>, C<getpeername>, C<getsockname>, |
174 | C<getsockopt>, C<listen>, C<recv>, C<send>, C<setsockopt>, C<shutdown>, | |
737dd4b4 | 175 | C<socket>, C<socketpair> |
cb1a09d0 AD |
176 | |
177 | =item System V interprocess communication functions | |
178 | ||
22fae026 TM |
179 | C<msgctl>, C<msgget>, C<msgrcv>, C<msgsnd>, C<semctl>, C<semget>, C<semop>, |
180 | C<shmctl>, C<shmget>, C<shmread>, C<shmwrite> | |
cb1a09d0 AD |
181 | |
182 | =item Fetching user and group info | |
183 | ||
22fae026 TM |
184 | C<endgrent>, C<endhostent>, C<endnetent>, C<endpwent>, C<getgrent>, |
185 | C<getgrgid>, C<getgrnam>, C<getlogin>, C<getpwent>, C<getpwnam>, | |
186 | C<getpwuid>, C<setgrent>, C<setpwent> | |
cb1a09d0 AD |
187 | |
188 | =item Fetching network info | |
189 | ||
22fae026 TM |
190 | C<endprotoent>, C<endservent>, C<gethostbyaddr>, C<gethostbyname>, |
191 | C<gethostent>, C<getnetbyaddr>, C<getnetbyname>, C<getnetent>, | |
192 | C<getprotobyname>, C<getprotobynumber>, C<getprotoent>, | |
193 | C<getservbyname>, C<getservbyport>, C<getservent>, C<sethostent>, | |
194 | C<setnetent>, C<setprotoent>, C<setservent> | |
cb1a09d0 AD |
195 | |
196 | =item Time-related functions | |
197 | ||
22fae026 | 198 | C<gmtime>, C<localtime>, C<time>, C<times> |
cb1a09d0 | 199 | |
37798a01 | 200 | =item Functions new in perl5 |
201 | ||
22fae026 | 202 | C<abs>, C<bless>, C<chomp>, C<chr>, C<exists>, C<formline>, C<glob>, |
b76cc8ba | 203 | C<import>, C<lc>, C<lcfirst>, C<map>, C<my>, C<no>, C<our>, C<prototype>, |
4375e838 | 204 | C<qx>, C<qw>, C<readline>, C<readpipe>, C<ref>, C<sub*>, C<sysopen>, C<tie>, |
22fae026 | 205 | C<tied>, C<uc>, C<ucfirst>, C<untie>, C<use> |
37798a01 | 206 | |
207 | * - C<sub> was a keyword in perl4, but in perl5 it is an | |
5a964f20 | 208 | operator, which can be used in expressions. |
37798a01 | 209 | |
210 | =item Functions obsoleted in perl5 | |
211 | ||
22fae026 | 212 | C<dbmclose>, C<dbmopen> |
37798a01 | 213 | |
cb1a09d0 AD |
214 | =back |
215 | ||
60f9f73c JH |
216 | =head2 Portability |
217 | ||
2b5ab1e7 TC |
218 | Perl was born in Unix and can therefore access all common Unix |
219 | system calls. In non-Unix environments, the functionality of some | |
220 | Unix system calls may not be available, or details of the available | |
221 | functionality may differ slightly. The Perl functions affected | |
60f9f73c JH |
222 | by this are: |
223 | ||
224 | C<-X>, C<binmode>, C<chmod>, C<chown>, C<chroot>, C<crypt>, | |
225 | C<dbmclose>, C<dbmopen>, C<dump>, C<endgrent>, C<endhostent>, | |
226 | C<endnetent>, C<endprotoent>, C<endpwent>, C<endservent>, C<exec>, | |
227 | C<fcntl>, C<flock>, C<fork>, C<getgrent>, C<getgrgid>, C<gethostent>, | |
228 | C<getlogin>, C<getnetbyaddr>, C<getnetbyname>, C<getnetent>, | |
229 | C<getppid>, C<getprgp>, C<getpriority>, C<getprotobynumber>, | |
230 | C<getprotoent>, C<getpwent>, C<getpwnam>, C<getpwuid>, | |
231 | C<getservbyport>, C<getservent>, C<getsockopt>, C<glob>, C<ioctl>, | |
232 | C<kill>, C<link>, C<lstat>, C<msgctl>, C<msgget>, C<msgrcv>, | |
2b5ab1e7 | 233 | C<msgsnd>, C<open>, C<pipe>, C<readlink>, C<rename>, C<select>, C<semctl>, |
60f9f73c JH |
234 | C<semget>, C<semop>, C<setgrent>, C<sethostent>, C<setnetent>, |
235 | C<setpgrp>, C<setpriority>, C<setprotoent>, C<setpwent>, | |
236 | C<setservent>, C<setsockopt>, C<shmctl>, C<shmget>, C<shmread>, | |
737dd4b4 | 237 | C<shmwrite>, C<socket>, C<socketpair>, |
80cbd5ad JH |
238 | C<stat>, C<symlink>, C<syscall>, C<sysopen>, C<system>, |
239 | C<times>, C<truncate>, C<umask>, C<unlink>, | |
2b5ab1e7 | 240 | C<utime>, C<wait>, C<waitpid> |
60f9f73c JH |
241 | |
242 | For more information about the portability of these functions, see | |
243 | L<perlport> and other available platform-specific documentation. | |
244 | ||
cb1a09d0 AD |
245 | =head2 Alphabetical Listing of Perl Functions |
246 | ||
a0d0e21e LW |
247 | =over 8 |
248 | ||
22fae026 | 249 | =item I<-X> FILEHANDLE |
a0d0e21e | 250 | |
22fae026 | 251 | =item I<-X> EXPR |
a0d0e21e | 252 | |
22fae026 | 253 | =item I<-X> |
a0d0e21e LW |
254 | |
255 | A file test, where X is one of the letters listed below. This unary | |
256 | operator takes one argument, either a filename or a filehandle, and | |
257 | tests the associated file to see if something is true about it. If the | |
7660c0ab | 258 | argument is omitted, tests C<$_>, except for C<-t>, which tests STDIN. |
19799a22 | 259 | Unless otherwise documented, it returns C<1> for true and C<''> for false, or |
a0d0e21e LW |
260 | the undefined value if the file doesn't exist. Despite the funny |
261 | names, precedence is the same as any other named unary operator, and | |
262 | the argument may be parenthesized like any other unary operator. The | |
263 | operator may be any of: | |
7e778d91 IZ |
264 | 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> |
265 | 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 LW |
266 | |
267 | -r File is readable by effective uid/gid. | |
268 | -w File is writable by effective uid/gid. | |
269 | -x File is executable by effective uid/gid. | |
270 | -o File is owned by effective uid. | |
271 | ||
272 | -R File is readable by real uid/gid. | |
273 | -W File is writable by real uid/gid. | |
274 | -X File is executable by real uid/gid. | |
275 | -O File is owned by real uid. | |
276 | ||
277 | -e File exists. | |
8e7e0aa8 MJD |
278 | -z File has zero size (is empty). |
279 | -s File has nonzero size (returns size in bytes). | |
a0d0e21e LW |
280 | |
281 | -f File is a plain file. | |
282 | -d File is a directory. | |
283 | -l File is a symbolic link. | |
9c4d0f16 | 284 | -p File is a named pipe (FIFO), or Filehandle is a pipe. |
a0d0e21e LW |
285 | -S File is a socket. |
286 | -b File is a block special file. | |
287 | -c File is a character special file. | |
288 | -t Filehandle is opened to a tty. | |
289 | ||
290 | -u File has setuid bit set. | |
291 | -g File has setgid bit set. | |
292 | -k File has sticky bit set. | |
293 | ||
121910a4 | 294 | -T File is an ASCII text file (heuristic guess). |
2cdbc966 | 295 | -B File is a "binary" file (opposite of -T). |
a0d0e21e | 296 | |
95a3fe12 | 297 | -M Script start time minus file modification time, in days. |
a0d0e21e | 298 | -A Same for access time. |
95a3fe12 | 299 | -C Same for inode change time (Unix, may differ for other platforms) |
a0d0e21e | 300 | |
a0d0e21e LW |
301 | Example: |
302 | ||
303 | while (<>) { | |
5b3eff12 | 304 | chomp; |
a0d0e21e | 305 | next unless -f $_; # ignore specials |
5a964f20 | 306 | #... |
a0d0e21e LW |
307 | } |
308 | ||
5ff3f7a4 GS |
309 | The interpretation of the file permission operators C<-r>, C<-R>, |
310 | C<-w>, C<-W>, C<-x>, and C<-X> is by default based solely on the mode | |
311 | of the file and the uids and gids of the user. There may be other | |
312 | reasons you can't actually read, write, or execute the file. Such | |
313 | reasons may be for example network filesystem access controls, ACLs | |
314 | (access control lists), read-only filesystems, and unrecognized | |
315 | executable formats. | |
316 | ||
2b5ab1e7 TC |
317 | Also note that, for the superuser on the local filesystems, the C<-r>, |
318 | C<-R>, C<-w>, and C<-W> tests always return 1, and C<-x> and C<-X> return 1 | |
5ff3f7a4 GS |
319 | if any execute bit is set in the mode. Scripts run by the superuser |
320 | may thus need to do a stat() to determine the actual mode of the file, | |
2b5ab1e7 | 321 | or temporarily set their effective uid to something else. |
5ff3f7a4 GS |
322 | |
323 | If you are using ACLs, there is a pragma called C<filetest> that may | |
324 | produce more accurate results than the bare stat() mode bits. | |
5ff3f7a4 GS |
325 | When under the C<use filetest 'access'> the above-mentioned filetests |
326 | will test whether the permission can (not) be granted using the | |
468541a8 | 327 | access() family of system calls. Also note that the C<-x> and C<-X> may |
5ff3f7a4 GS |
328 | under this pragma return true even if there are no execute permission |
329 | bits set (nor any extra execute permission ACLs). This strangeness is | |
330 | due to the underlying system calls' definitions. Read the | |
331 | documentation for the C<filetest> pragma for more information. | |
332 | ||
a0d0e21e LW |
333 | Note that C<-s/a/b/> does not do a negated substitution. Saying |
334 | C<-exp($foo)> still works as expected, however--only single letters | |
335 | following a minus are interpreted as file tests. | |
336 | ||
337 | The C<-T> and C<-B> switches work as follows. The first block or so of the | |
338 | file is examined for odd characters such as strange control codes or | |
61eff3bc | 339 | characters with the high bit set. If too many strange characters (>30%) |
a0d0e21e LW |
340 | are found, it's a C<-B> file, otherwise it's a C<-T> file. Also, any file |
341 | containing null in the first block is considered a binary file. If C<-T> | |
9124316e | 342 | or C<-B> is used on a filehandle, the current IO buffer is examined |
19799a22 | 343 | rather than the first block. Both C<-T> and C<-B> return true on a null |
54310121 | 344 | file, or a file at EOF when testing a filehandle. Because you have to |
4633a7c4 LW |
345 | read a file to do the C<-T> test, on most occasions you want to use a C<-f> |
346 | against the file first, as in C<next unless -f $file && -T $file>. | |
a0d0e21e | 347 | |
19799a22 | 348 | If any of the file tests (or either the C<stat> or C<lstat> operators) are given |
28757baa | 349 | the special filehandle consisting of a solitary underline, then the stat |
a0d0e21e LW |
350 | structure of the previous file test (or stat operator) is used, saving |
351 | a system call. (This doesn't work with C<-t>, and you need to remember | |
352 | that lstat() and C<-l> will leave values in the stat structure for the | |
5c9aa243 RGS |
353 | symbolic link, not the real file.) (Also, if the stat buffer was filled by |
354 | a C<lstat> call, C<-T> and C<-B> will reset it with the results of C<stat _>). | |
355 | Example: | |
a0d0e21e LW |
356 | |
357 | print "Can do.\n" if -r $a || -w _ || -x _; | |
358 | ||
359 | stat($filename); | |
360 | print "Readable\n" if -r _; | |
361 | print "Writable\n" if -w _; | |
362 | print "Executable\n" if -x _; | |
363 | print "Setuid\n" if -u _; | |
364 | print "Setgid\n" if -g _; | |
365 | print "Sticky\n" if -k _; | |
366 | print "Text\n" if -T _; | |
367 | print "Binary\n" if -B _; | |
368 | ||
369 | =item abs VALUE | |
370 | ||
54310121 | 371 | =item abs |
bbce6d69 | 372 | |
a0d0e21e | 373 | Returns the absolute value of its argument. |
7660c0ab | 374 | If VALUE is omitted, uses C<$_>. |
a0d0e21e LW |
375 | |
376 | =item accept NEWSOCKET,GENERICSOCKET | |
377 | ||
f86cebdf | 378 | Accepts an incoming socket connect, just as the accept(2) system call |
19799a22 | 379 | does. Returns the packed address if it succeeded, false otherwise. |
2b5ab1e7 | 380 | See the example in L<perlipc/"Sockets: Client/Server Communication">. |
a0d0e21e | 381 | |
8d2a6795 GS |
382 | On systems that support a close-on-exec flag on files, the flag will |
383 | be set for the newly opened file descriptor, as determined by the | |
384 | value of $^F. See L<perlvar/$^F>. | |
385 | ||
a0d0e21e LW |
386 | =item alarm SECONDS |
387 | ||
54310121 | 388 | =item alarm |
bbce6d69 | 389 | |
a0d0e21e | 390 | Arranges to have a SIGALRM delivered to this process after the |
d400eac8 JH |
391 | specified number of wallclock seconds have elapsed. If SECONDS is not |
392 | specified, the value stored in C<$_> is used. (On some machines, | |
393 | unfortunately, the elapsed time may be up to one second less or more | |
394 | than you specified because of how seconds are counted, and process | |
395 | scheduling may delay the delivery of the signal even further.) | |
396 | ||
397 | Only one timer may be counting at once. Each call disables the | |
398 | previous timer, and an argument of C<0> may be supplied to cancel the | |
399 | previous timer without starting a new one. The returned value is the | |
400 | amount of time remaining on the previous timer. | |
a0d0e21e | 401 | |
4633a7c4 | 402 | For delays of finer granularity than one second, you may use Perl's |
19799a22 GS |
403 | four-argument version of select() leaving the first three arguments |
404 | undefined, or you might be able to use the C<syscall> interface to | |
83df6a1d JH |
405 | access setitimer(2) if your system supports it. The Time::HiRes |
406 | module (from CPAN, and starting from Perl 5.8 part of the standard | |
407 | distribution) may also prove useful. | |
2b5ab1e7 | 408 | |
68f8bed4 JH |
409 | It is usually a mistake to intermix C<alarm> and C<sleep> calls. |
410 | (C<sleep> may be internally implemented in your system with C<alarm>) | |
a0d0e21e | 411 | |
19799a22 GS |
412 | If you want to use C<alarm> to time out a system call you need to use an |
413 | C<eval>/C<die> pair. You can't rely on the alarm causing the system call to | |
f86cebdf | 414 | fail with C<$!> set to C<EINTR> because Perl sets up signal handlers to |
19799a22 | 415 | restart system calls on some systems. Using C<eval>/C<die> always works, |
5a964f20 | 416 | modulo the caveats given in L<perlipc/"Signals">. |
ff68c719 | 417 | |
418 | eval { | |
f86cebdf | 419 | local $SIG{ALRM} = sub { die "alarm\n" }; # NB: \n required |
36477c24 | 420 | alarm $timeout; |
ff68c719 | 421 | $nread = sysread SOCKET, $buffer, $size; |
36477c24 | 422 | alarm 0; |
ff68c719 | 423 | }; |
ff68c719 | 424 | if ($@) { |
f86cebdf | 425 | die unless $@ eq "alarm\n"; # propagate unexpected errors |
ff68c719 | 426 | # timed out |
427 | } | |
428 | else { | |
429 | # didn't | |
430 | } | |
431 | ||
a0d0e21e LW |
432 | =item atan2 Y,X |
433 | ||
434 | Returns the arctangent of Y/X in the range -PI to PI. | |
435 | ||
ca6e1c26 | 436 | For the tangent operation, you may use the C<Math::Trig::tan> |
28757baa | 437 | function, or use the familiar relation: |
438 | ||
439 | sub tan { sin($_[0]) / cos($_[0]) } | |
440 | ||
a0d0e21e LW |
441 | =item bind SOCKET,NAME |
442 | ||
443 | Binds a network address to a socket, just as the bind system call | |
19799a22 | 444 | does. Returns true if it succeeded, false otherwise. NAME should be a |
4633a7c4 LW |
445 | packed address of the appropriate type for the socket. See the examples in |
446 | L<perlipc/"Sockets: Client/Server Communication">. | |
a0d0e21e | 447 | |
fae2c0fb | 448 | =item binmode FILEHANDLE, LAYER |
1c1fc3ea | 449 | |
a0d0e21e LW |
450 | =item binmode FILEHANDLE |
451 | ||
1cbfc93d NIS |
452 | Arranges for FILEHANDLE to be read or written in "binary" or "text" |
453 | mode on systems where the run-time libraries distinguish between | |
454 | binary and text files. If FILEHANDLE is an expression, the value is | |
455 | taken as the name of the filehandle. Returns true on success, | |
456 | C<undef> on failure. | |
457 | ||
fae2c0fb | 458 | If LAYER is omitted or specified as C<:raw> the filehandle is made |
0226bbdb NIS |
459 | suitable for passing binary data. This includes turning off possible CRLF |
460 | translation and marking it as bytes (as opposed to Unicode characters). | |
461 | Note that as desipite what may be implied in I<"Programming Perl"> | |
462 | (the Camel) or elsewhere C<:raw> is I<not> the simply inverse of C<:crlf> | |
fae2c0fb | 463 | -- other layers which would affect binary nature of the stream are |
0226bbdb NIS |
464 | I<also> disabled. See L<PerlIO>, L<perlrun> and the discussion about the |
465 | PERLIO environment variable. | |
01e6739c | 466 | |
fae2c0fb RGS |
467 | I<The LAYER parameter of the binmode() function is described as "DISCIPLINE" |
468 | in "Programming Perl, 3rd Edition". However, since the publishing of this | |
469 | book, by many known as "Camel III", the consensus of the naming of this | |
470 | functionality has moved from "discipline" to "layer". All documentation | |
471 | of this version of Perl therefore refers to "layers" rather than to | |
472 | "disciplines". Now back to the regularly scheduled documentation...> | |
473 | ||
01e6739c NIS |
474 | On some systems (in general, DOS and Windows-based systems) binmode() |
475 | is necessary when you're not working with a text file. For the sake | |
476 | of portability it is a good idea to always use it when appropriate, | |
477 | and to never use it when it isn't appropriate. | |
478 | ||
479 | In other words: regardless of platform, use binmode() on binary files | |
480 | (like for example images). | |
481 | ||
fae2c0fb | 482 | If LAYER is present it is a single string, but may contain |
01e6739c | 483 | multiple directives. The directives alter the behaviour of the |
fae2c0fb | 484 | file handle. When LAYER is present using binmode on text |
01e6739c NIS |
485 | file makes sense. |
486 | ||
487 | To mark FILEHANDLE as UTF-8, use C<:utf8>. | |
1cbfc93d NIS |
488 | |
489 | The C<:bytes>, C<:crlf>, and C<:utf8>, and any other directives of the | |
fae2c0fb RGS |
490 | form C<:...>, are called I/O I<layers>. The C<open> pragma can be used to |
491 | establish default I/O layers. See L<open>. | |
1cbfc93d | 492 | |
ed53a2bb | 493 | In general, binmode() should be called after open() but before any I/O |
01e6739c NIS |
494 | is done on the filehandle. Calling binmode() will normally flush any |
495 | pending buffered output data (and perhaps pending input data) on the | |
fae2c0fb | 496 | handle. An exception to this is the C<:encoding> layer that |
01e6739c | 497 | changes the default character encoding of the handle, see L<open>. |
fae2c0fb | 498 | The C<:encoding> layer sometimes needs to be called in |
ed53a2bb | 499 | mid-stream, and it doesn't flush the stream. |
16fe6d59 | 500 | |
19799a22 | 501 | The operating system, device drivers, C libraries, and Perl run-time |
30168b04 GS |
502 | system all work together to let the programmer treat a single |
503 | character (C<\n>) as the line terminator, irrespective of the external | |
504 | representation. On many operating systems, the native text file | |
505 | representation matches the internal representation, but on some | |
506 | platforms the external representation of C<\n> is made up of more than | |
507 | one character. | |
508 | ||
68bd7414 NIS |
509 | Mac OS, all variants of Unix, and Stream_LF files on VMS use a single |
510 | character to end each line in the external representation of text (even | |
5e12dbfa | 511 | though that single character is CARRIAGE RETURN on Mac OS and LINE FEED |
01e6739c NIS |
512 | on Unix and most VMS files). In other systems like OS/2, DOS and the |
513 | various flavors of MS-Windows your program sees a C<\n> as a simple C<\cJ>, | |
514 | but what's stored in text files are the two characters C<\cM\cJ>. That | |
515 | means that, if you don't use binmode() on these systems, C<\cM\cJ> | |
516 | sequences on disk will be converted to C<\n> on input, and any C<\n> in | |
517 | your program will be converted back to C<\cM\cJ> on output. This is what | |
518 | you want for text files, but it can be disastrous for binary files. | |
30168b04 GS |
519 | |
520 | Another consequence of using binmode() (on some systems) is that | |
521 | special end-of-file markers will be seen as part of the data stream. | |
522 | For systems from the Microsoft family this means that if your binary | |
4375e838 | 523 | data contains C<\cZ>, the I/O subsystem will regard it as the end of |
30168b04 GS |
524 | the file, unless you use binmode(). |
525 | ||
526 | binmode() is not only important for readline() and print() operations, | |
527 | but also when using read(), seek(), sysread(), syswrite() and tell() | |
528 | (see L<perlport> for more details). See the C<$/> and C<$\> variables | |
529 | in L<perlvar> for how to manually set your input and output | |
530 | line-termination sequences. | |
a0d0e21e | 531 | |
4633a7c4 | 532 | =item bless REF,CLASSNAME |
a0d0e21e LW |
533 | |
534 | =item bless REF | |
535 | ||
2b5ab1e7 TC |
536 | This function tells the thingy referenced by REF that it is now an object |
537 | in the CLASSNAME package. If CLASSNAME is omitted, the current package | |
19799a22 | 538 | is used. Because a C<bless> is often the last thing in a constructor, |
2b5ab1e7 TC |
539 | it returns the reference for convenience. Always use the two-argument |
540 | version if the function doing the blessing might be inherited by a | |
541 | derived class. See L<perltoot> and L<perlobj> for more about the blessing | |
542 | (and blessings) of objects. | |
a0d0e21e | 543 | |
57668c4d | 544 | Consider always blessing objects in CLASSNAMEs that are mixed case. |
2b5ab1e7 TC |
545 | Namespaces with all lowercase names are considered reserved for |
546 | Perl pragmata. Builtin types have all uppercase names, so to prevent | |
547 | confusion, you may wish to avoid such package names as well. Make sure | |
548 | that CLASSNAME is a true value. | |
60ad88b8 GS |
549 | |
550 | See L<perlmod/"Perl Modules">. | |
551 | ||
a0d0e21e LW |
552 | =item caller EXPR |
553 | ||
554 | =item caller | |
555 | ||
5a964f20 | 556 | Returns the context of the current subroutine call. In scalar context, |
28757baa | 557 | returns the caller's package name if there is a caller, that is, if |
19799a22 | 558 | we're in a subroutine or C<eval> or C<require>, and the undefined value |
5a964f20 | 559 | otherwise. In list context, returns |
a0d0e21e | 560 | |
748a9306 | 561 | ($package, $filename, $line) = caller; |
a0d0e21e LW |
562 | |
563 | With EXPR, it returns some extra information that the debugger uses to | |
564 | print a stack trace. The value of EXPR indicates how many call frames | |
565 | to go back before the current one. | |
566 | ||
f3aa04c2 | 567 | ($package, $filename, $line, $subroutine, $hasargs, |
e476b1b5 | 568 | $wantarray, $evaltext, $is_require, $hints, $bitmask) = caller($i); |
e7ea3e70 | 569 | |
951ba7fe | 570 | Here $subroutine may be C<(eval)> if the frame is not a subroutine |
19799a22 | 571 | call, but an C<eval>. In such a case additional elements $evaltext and |
7660c0ab | 572 | C<$is_require> are set: C<$is_require> is true if the frame is created by a |
19799a22 | 573 | C<require> or C<use> statement, $evaltext contains the text of the |
277ddfaf | 574 | C<eval EXPR> statement. In particular, for an C<eval BLOCK> statement, |
951ba7fe | 575 | $filename is C<(eval)>, but $evaltext is undefined. (Note also that |
0fc9dec4 RGS |
576 | each C<use> statement creates a C<require> frame inside an C<eval EXPR> |
577 | frame.) $subroutine may also be C<(unknown)> if this particular | |
578 | subroutine happens to have been deleted from the symbol table. | |
579 | C<$hasargs> is true if a new instance of C<@_> was set up for the frame. | |
580 | C<$hints> and C<$bitmask> contain pragmatic hints that the caller was | |
581 | compiled with. The C<$hints> and C<$bitmask> values are subject to change | |
582 | between versions of Perl, and are not meant for external use. | |
748a9306 LW |
583 | |
584 | Furthermore, when called from within the DB package, caller returns more | |
7660c0ab | 585 | detailed information: it sets the list variable C<@DB::args> to be the |
54310121 | 586 | arguments with which the subroutine was invoked. |
748a9306 | 587 | |
7660c0ab | 588 | Be aware that the optimizer might have optimized call frames away before |
19799a22 | 589 | C<caller> had a chance to get the information. That means that C<caller(N)> |
7660c0ab | 590 | might not return information about the call frame you expect it do, for |
b76cc8ba | 591 | C<< N > 1 >>. In particular, C<@DB::args> might have information from the |
19799a22 | 592 | previous time C<caller> was called. |
7660c0ab | 593 | |
a0d0e21e LW |
594 | =item chdir EXPR |
595 | ||
ffce7b87 | 596 | Changes the working directory to EXPR, if possible. If EXPR is omitted, |
0bfc1ec4 | 597 | changes to the directory specified by C<$ENV{HOME}>, if set; if not, |
ffce7b87 | 598 | changes to the directory specified by C<$ENV{LOGDIR}>. (Under VMS, the |
b4ad75f0 AMS |
599 | variable C<$ENV{SYS$LOGIN}> is also checked, and used if it is set.) If |
600 | neither is set, C<chdir> does nothing. It returns true upon success, | |
601 | false otherwise. See the example under C<die>. | |
a0d0e21e LW |
602 | |
603 | =item chmod LIST | |
604 | ||
605 | Changes the permissions of a list of files. The first element of the | |
4633a7c4 | 606 | list must be the numerical mode, which should probably be an octal |
2f9daede TP |
607 | number, and which definitely should I<not> a string of octal digits: |
608 | C<0644> is okay, C<'0644'> is not. Returns the number of files | |
dc848c6f | 609 | successfully changed. See also L</oct>, if all you have is a string. |
a0d0e21e LW |
610 | |
611 | $cnt = chmod 0755, 'foo', 'bar'; | |
612 | chmod 0755, @executables; | |
f86cebdf GS |
613 | $mode = '0644'; chmod $mode, 'foo'; # !!! sets mode to |
614 | # --w----r-T | |
2f9daede TP |
615 | $mode = '0644'; chmod oct($mode), 'foo'; # this is better |
616 | $mode = 0644; chmod $mode, 'foo'; # this is best | |
a0d0e21e | 617 | |
ca6e1c26 JH |
618 | You can also import the symbolic C<S_I*> constants from the Fcntl |
619 | module: | |
620 | ||
621 | use Fcntl ':mode'; | |
622 | ||
623 | chmod S_IRWXU|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH, @executables; | |
624 | # This is identical to the chmod 0755 of the above example. | |
625 | ||
a0d0e21e LW |
626 | =item chomp VARIABLE |
627 | ||
313c9f5c | 628 | =item chomp( LIST ) |
a0d0e21e LW |
629 | |
630 | =item chomp | |
631 | ||
2b5ab1e7 TC |
632 | This safer version of L</chop> removes any trailing string |
633 | that corresponds to the current value of C<$/> (also known as | |
28757baa | 634 | $INPUT_RECORD_SEPARATOR in the C<English> module). It returns the total |
635 | number of characters removed from all its arguments. It's often used to | |
636 | remove the newline from the end of an input record when you're worried | |
2b5ab1e7 TC |
637 | that the final record may be missing its newline. When in paragraph |
638 | mode (C<$/ = "">), it removes all trailing newlines from the string. | |
4c5a6083 GS |
639 | When in slurp mode (C<$/ = undef>) or fixed-length record mode (C<$/> is |
640 | a reference to an integer or the like, see L<perlvar>) chomp() won't | |
b76cc8ba | 641 | remove anything. |
19799a22 | 642 | If VARIABLE is omitted, it chomps C<$_>. Example: |
a0d0e21e LW |
643 | |
644 | while (<>) { | |
645 | chomp; # avoid \n on last field | |
646 | @array = split(/:/); | |
5a964f20 | 647 | # ... |
a0d0e21e LW |
648 | } |
649 | ||
4bf21a6d RD |
650 | If VARIABLE is a hash, it chomps the hash's values, but not its keys. |
651 | ||
a0d0e21e LW |
652 | You can actually chomp anything that's an lvalue, including an assignment: |
653 | ||
654 | chomp($cwd = `pwd`); | |
655 | chomp($answer = <STDIN>); | |
656 | ||
657 | If you chomp a list, each element is chomped, and the total number of | |
658 | characters removed is returned. | |
659 | ||
15e44fd8 RGS |
660 | Note that parentheses are necessary when you're chomping anything |
661 | that is not a simple variable. This is because C<chomp $cwd = `pwd`;> | |
662 | is interpreted as C<(chomp $cwd) = `pwd`;>, rather than as | |
663 | C<chomp( $cwd = `pwd` )> which you might expect. Similarly, | |
664 | C<chomp $a, $b> is interpreted as C<chomp($a), $b> rather than | |
665 | as C<chomp($a, $b)>. | |
666 | ||
a0d0e21e LW |
667 | =item chop VARIABLE |
668 | ||
313c9f5c | 669 | =item chop( LIST ) |
a0d0e21e LW |
670 | |
671 | =item chop | |
672 | ||
673 | Chops off the last character of a string and returns the character | |
5b3eff12 | 674 | chopped. It is much more efficient than C<s/.$//s> because it neither |
7660c0ab | 675 | scans nor copies the string. If VARIABLE is omitted, chops C<$_>. |
4bf21a6d RD |
676 | If VARIABLE is a hash, it chops the hash's values, but not its keys. |
677 | ||
5b3eff12 | 678 | You can actually chop anything that's an lvalue, including an assignment. |
a0d0e21e LW |
679 | |
680 | If you chop a list, each element is chopped. Only the value of the | |
19799a22 | 681 | last C<chop> is returned. |
a0d0e21e | 682 | |
19799a22 | 683 | Note that C<chop> returns the last character. To return all but the last |
748a9306 LW |
684 | character, use C<substr($string, 0, -1)>. |
685 | ||
15e44fd8 RGS |
686 | See also L</chomp>. |
687 | ||
a0d0e21e LW |
688 | =item chown LIST |
689 | ||
690 | Changes the owner (and group) of a list of files. The first two | |
19799a22 GS |
691 | elements of the list must be the I<numeric> uid and gid, in that |
692 | order. A value of -1 in either position is interpreted by most | |
693 | systems to leave that value unchanged. Returns the number of files | |
694 | successfully changed. | |
a0d0e21e LW |
695 | |
696 | $cnt = chown $uid, $gid, 'foo', 'bar'; | |
697 | chown $uid, $gid, @filenames; | |
698 | ||
54310121 | 699 | Here's an example that looks up nonnumeric uids in the passwd file: |
a0d0e21e LW |
700 | |
701 | print "User: "; | |
19799a22 | 702 | chomp($user = <STDIN>); |
5a964f20 | 703 | print "Files: "; |
19799a22 | 704 | chomp($pattern = <STDIN>); |
a0d0e21e LW |
705 | |
706 | ($login,$pass,$uid,$gid) = getpwnam($user) | |
707 | or die "$user not in passwd file"; | |
708 | ||
5a964f20 | 709 | @ary = glob($pattern); # expand filenames |
a0d0e21e LW |
710 | chown $uid, $gid, @ary; |
711 | ||
54310121 | 712 | On most systems, you are not allowed to change the ownership of the |
4633a7c4 LW |
713 | file unless you're the superuser, although you should be able to change |
714 | the group to any of your secondary groups. On insecure systems, these | |
715 | restrictions may be relaxed, but this is not a portable assumption. | |
19799a22 GS |
716 | On POSIX systems, you can detect this condition this way: |
717 | ||
718 | use POSIX qw(sysconf _PC_CHOWN_RESTRICTED); | |
719 | $can_chown_giveaway = not sysconf(_PC_CHOWN_RESTRICTED); | |
4633a7c4 | 720 | |
a0d0e21e LW |
721 | =item chr NUMBER |
722 | ||
54310121 | 723 | =item chr |
bbce6d69 | 724 | |
a0d0e21e | 725 | Returns the character represented by that NUMBER in the character set. |
a0ed51b3 | 726 | For example, C<chr(65)> is C<"A"> in either ASCII or Unicode, and |
121910a4 JH |
727 | chr(0x263a) is a Unicode smiley face. Note that characters from 127 |
728 | to 255 (inclusive) are by default not encoded in Unicode for backward | |
729 | compatibility reasons (but see L<encoding>). | |
aaa68c4a | 730 | |
b76cc8ba | 731 | For the reverse, use L</ord>. |
121910a4 | 732 | See L<perlunicode> and L<encoding> for more about Unicode. |
a0d0e21e | 733 | |
7660c0ab | 734 | If NUMBER is omitted, uses C<$_>. |
bbce6d69 | 735 | |
a0d0e21e LW |
736 | =item chroot FILENAME |
737 | ||
54310121 | 738 | =item chroot |
bbce6d69 | 739 | |
5a964f20 | 740 | This function works like the system call by the same name: it makes the |
4633a7c4 | 741 | named directory the new root directory for all further pathnames that |
951ba7fe | 742 | begin with a C</> by your process and all its children. (It doesn't |
28757baa | 743 | change your current working directory, which is unaffected.) For security |
4633a7c4 | 744 | reasons, this call is restricted to the superuser. If FILENAME is |
19799a22 | 745 | omitted, does a C<chroot> to C<$_>. |
a0d0e21e LW |
746 | |
747 | =item close FILEHANDLE | |
748 | ||
6a518fbc TP |
749 | =item close |
750 | ||
9124316e JH |
751 | Closes the file or pipe associated with the file handle, returning |
752 | true only if IO buffers are successfully flushed and closes the system | |
753 | file descriptor. Closes the currently selected filehandle if the | |
754 | argument is omitted. | |
fb73857a | 755 | |
756 | You don't have to close FILEHANDLE if you are immediately going to do | |
19799a22 GS |
757 | another C<open> on it, because C<open> will close it for you. (See |
758 | C<open>.) However, an explicit C<close> on an input file resets the line | |
759 | counter (C<$.>), while the implicit close done by C<open> does not. | |
fb73857a | 760 | |
19799a22 GS |
761 | If the file handle came from a piped open C<close> will additionally |
762 | return false if one of the other system calls involved fails or if the | |
fb73857a | 763 | program exits with non-zero status. (If the only problem was that the |
b76cc8ba | 764 | program exited non-zero C<$!> will be set to C<0>.) Closing a pipe |
2b5ab1e7 | 765 | also waits for the process executing on the pipe to complete, in case you |
b76cc8ba | 766 | want to look at the output of the pipe afterwards, and |
2b5ab1e7 | 767 | implicitly puts the exit status value of that command into C<$?>. |
5a964f20 | 768 | |
73689b13 GS |
769 | Prematurely closing the read end of a pipe (i.e. before the process |
770 | writing to it at the other end has closed it) will result in a | |
771 | SIGPIPE being delivered to the writer. If the other end can't | |
772 | handle that, be sure to read all the data before closing the pipe. | |
773 | ||
fb73857a | 774 | Example: |
a0d0e21e | 775 | |
fb73857a | 776 | open(OUTPUT, '|sort >foo') # pipe to sort |
777 | or die "Can't start sort: $!"; | |
5a964f20 | 778 | #... # print stuff to output |
fb73857a | 779 | close OUTPUT # wait for sort to finish |
780 | or warn $! ? "Error closing sort pipe: $!" | |
781 | : "Exit status $? from sort"; | |
782 | open(INPUT, 'foo') # get sort's results | |
783 | or die "Can't open 'foo' for input: $!"; | |
a0d0e21e | 784 | |
5a964f20 TC |
785 | FILEHANDLE may be an expression whose value can be used as an indirect |
786 | filehandle, usually the real filehandle name. | |
a0d0e21e LW |
787 | |
788 | =item closedir DIRHANDLE | |
789 | ||
19799a22 | 790 | Closes a directory opened by C<opendir> and returns the success of that |
5a964f20 TC |
791 | system call. |
792 | ||
793 | DIRHANDLE may be an expression whose value can be used as an indirect | |
794 | dirhandle, usually the real dirhandle name. | |
a0d0e21e LW |
795 | |
796 | =item connect SOCKET,NAME | |
797 | ||
798 | Attempts to connect to a remote socket, just as the connect system call | |
19799a22 | 799 | does. Returns true if it succeeded, false otherwise. NAME should be a |
4633a7c4 LW |
800 | packed address of the appropriate type for the socket. See the examples in |
801 | L<perlipc/"Sockets: Client/Server Communication">. | |
a0d0e21e | 802 | |
cb1a09d0 AD |
803 | =item continue BLOCK |
804 | ||
805 | Actually a flow control statement rather than a function. If there is a | |
98293880 JH |
806 | C<continue> BLOCK attached to a BLOCK (typically in a C<while> or |
807 | C<foreach>), it is always executed just before the conditional is about to | |
808 | be evaluated again, just like the third part of a C<for> loop in C. Thus | |
cb1a09d0 AD |
809 | it can be used to increment a loop variable, even when the loop has been |
810 | continued via the C<next> statement (which is similar to the C C<continue> | |
811 | statement). | |
812 | ||
98293880 | 813 | C<last>, C<next>, or C<redo> may appear within a C<continue> |
19799a22 GS |
814 | block. C<last> and C<redo> will behave as if they had been executed within |
815 | the main block. So will C<next>, but since it will execute a C<continue> | |
1d2dff63 GS |
816 | block, it may be more entertaining. |
817 | ||
818 | while (EXPR) { | |
819 | ### redo always comes here | |
820 | do_something; | |
821 | } continue { | |
822 | ### next always comes here | |
823 | do_something_else; | |
824 | # then back the top to re-check EXPR | |
825 | } | |
826 | ### last always comes here | |
827 | ||
828 | Omitting the C<continue> section is semantically equivalent to using an | |
19799a22 | 829 | empty one, logically enough. In that case, C<next> goes directly back |
1d2dff63 GS |
830 | to check the condition at the top of the loop. |
831 | ||
a0d0e21e LW |
832 | =item cos EXPR |
833 | ||
d6217f1e GS |
834 | =item cos |
835 | ||
5a964f20 | 836 | Returns the cosine of EXPR (expressed in radians). If EXPR is omitted, |
7660c0ab | 837 | takes cosine of C<$_>. |
a0d0e21e | 838 | |
ca6e1c26 | 839 | For the inverse cosine operation, you may use the C<Math::Trig::acos()> |
28757baa | 840 | function, or use this relation: |
841 | ||
842 | sub acos { atan2( sqrt(1 - $_[0] * $_[0]), $_[0] ) } | |
843 | ||
a0d0e21e LW |
844 | =item crypt PLAINTEXT,SALT |
845 | ||
f86cebdf | 846 | Encrypts a string exactly like the crypt(3) function in the C library |
4633a7c4 LW |
847 | (assuming that you actually have a version there that has not been |
848 | extirpated as a potential munition). This can prove useful for checking | |
849 | the password file for lousy passwords, amongst other things. Only the | |
850 | guys wearing white hats should do this. | |
a0d0e21e | 851 | |
85c16d83 JH |
852 | Note that C<crypt> is intended to be a one-way function, much like |
853 | breaking eggs to make an omelette. There is no (known) corresponding | |
854 | decrypt function (in other words, the crypt() is a one-way hash | |
855 | function). As a result, this function isn't all that useful for | |
11155c91 | 856 | cryptography. (For that, see your nearby CPAN mirror.) |
2f9daede | 857 | |
85c16d83 JH |
858 | When verifying an existing encrypted string you should use the |
859 | encrypted text as the salt (like C<crypt($plain, $crypted) eq | |
860 | $crypted>). This allows your code to work with the standard C<crypt> | |
861 | and with more exotic implementations. In other words, do not assume | |
862 | anything about the returned string itself, or how many bytes in | |
863 | the encrypted string matter. | |
864 | ||
865 | Traditionally the result is a string of 13 bytes: two first bytes of | |
866 | the salt, followed by 11 bytes from the set C<[./0-9A-Za-z]>, and only | |
867 | the first eight bytes of the encrypted string mattered, but | |
868 | alternative hashing schemes (like MD5), higher level security schemes | |
869 | (like C2), and implementations on non-UNIX platforms may produce | |
870 | different strings. | |
871 | ||
872 | When choosing a new salt create a random two character string whose | |
873 | characters come from the set C<[./0-9A-Za-z]> (like C<join '', ('.', | |
874 | '/', 0..9, 'A'..'Z', 'a'..'z')[rand 64, rand 64]>). | |
e71965be | 875 | |
a0d0e21e LW |
876 | Here's an example that makes sure that whoever runs this program knows |
877 | their own password: | |
878 | ||
879 | $pwd = (getpwuid($<))[1]; | |
a0d0e21e LW |
880 | |
881 | system "stty -echo"; | |
882 | print "Password: "; | |
e71965be | 883 | chomp($word = <STDIN>); |
a0d0e21e LW |
884 | print "\n"; |
885 | system "stty echo"; | |
886 | ||
e71965be | 887 | if (crypt($word, $pwd) ne $pwd) { |
a0d0e21e LW |
888 | die "Sorry...\n"; |
889 | } else { | |
890 | print "ok\n"; | |
54310121 | 891 | } |
a0d0e21e | 892 | |
9f8f0c9d | 893 | Of course, typing in your own password to whoever asks you |
748a9306 | 894 | for it is unwise. |
a0d0e21e | 895 | |
19799a22 GS |
896 | The L<crypt> function is unsuitable for encrypting large quantities |
897 | of data, not least of all because you can't get the information | |
898 | back. Look at the F<by-module/Crypt> and F<by-module/PGP> directories | |
899 | on your favorite CPAN mirror for a slew of potentially useful | |
900 | modules. | |
901 | ||
f2791508 JH |
902 | If using crypt() on a Unicode string (which I<potentially> has |
903 | characters with codepoints above 255), Perl tries to make sense | |
904 | of the situation by trying to downgrade (a copy of the string) | |
905 | the string back to an eight-bit byte string before calling crypt() | |
906 | (on that copy). If that works, good. If not, crypt() dies with | |
907 | C<Wide character in crypt>. | |
85c16d83 | 908 | |
aa689395 | 909 | =item dbmclose HASH |
a0d0e21e | 910 | |
19799a22 | 911 | [This function has been largely superseded by the C<untie> function.] |
a0d0e21e | 912 | |
aa689395 | 913 | Breaks the binding between a DBM file and a hash. |
a0d0e21e | 914 | |
19799a22 | 915 | =item dbmopen HASH,DBNAME,MASK |
a0d0e21e | 916 | |
19799a22 | 917 | [This function has been largely superseded by the C<tie> function.] |
a0d0e21e | 918 | |
7b8d334a | 919 | This binds a dbm(3), ndbm(3), sdbm(3), gdbm(3), or Berkeley DB file to a |
19799a22 GS |
920 | hash. HASH is the name of the hash. (Unlike normal C<open>, the first |
921 | argument is I<not> a filehandle, even though it looks like one). DBNAME | |
aa689395 | 922 | is the name of the database (without the F<.dir> or F<.pag> extension if |
923 | any). If the database does not exist, it is created with protection | |
19799a22 GS |
924 | specified by MASK (as modified by the C<umask>). If your system supports |
925 | only the older DBM functions, you may perform only one C<dbmopen> in your | |
aa689395 | 926 | program. In older versions of Perl, if your system had neither DBM nor |
19799a22 | 927 | ndbm, calling C<dbmopen> produced a fatal error; it now falls back to |
aa689395 | 928 | sdbm(3). |
929 | ||
930 | If you don't have write access to the DBM file, you can only read hash | |
931 | variables, not set them. If you want to test whether you can write, | |
19799a22 | 932 | either use file tests or try setting a dummy hash entry inside an C<eval>, |
aa689395 | 933 | which will trap the error. |
a0d0e21e | 934 | |
19799a22 GS |
935 | Note that functions such as C<keys> and C<values> may return huge lists |
936 | when used on large DBM files. You may prefer to use the C<each> | |
a0d0e21e LW |
937 | function to iterate over large DBM files. Example: |
938 | ||
939 | # print out history file offsets | |
940 | dbmopen(%HIST,'/usr/lib/news/history',0666); | |
941 | while (($key,$val) = each %HIST) { | |
942 | print $key, ' = ', unpack('L',$val), "\n"; | |
943 | } | |
944 | dbmclose(%HIST); | |
945 | ||
cb1a09d0 | 946 | See also L<AnyDBM_File> for a more general description of the pros and |
184e9718 | 947 | cons of the various dbm approaches, as well as L<DB_File> for a particularly |
cb1a09d0 | 948 | rich implementation. |
4633a7c4 | 949 | |
2b5ab1e7 TC |
950 | You can control which DBM library you use by loading that library |
951 | before you call dbmopen(): | |
952 | ||
953 | use DB_File; | |
954 | dbmopen(%NS_Hist, "$ENV{HOME}/.netscape/history.db") | |
955 | or die "Can't open netscape history file: $!"; | |
956 | ||
a0d0e21e LW |
957 | =item defined EXPR |
958 | ||
54310121 | 959 | =item defined |
bbce6d69 | 960 | |
2f9daede TP |
961 | Returns a Boolean value telling whether EXPR has a value other than |
962 | the undefined value C<undef>. If EXPR is not present, C<$_> will be | |
963 | checked. | |
964 | ||
965 | Many operations return C<undef> to indicate failure, end of file, | |
966 | system error, uninitialized variable, and other exceptional | |
967 | conditions. This function allows you to distinguish C<undef> from | |
968 | other values. (A simple Boolean test will not distinguish among | |
7660c0ab | 969 | C<undef>, zero, the empty string, and C<"0">, which are all equally |
2f9daede | 970 | false.) Note that since C<undef> is a valid scalar, its presence |
19799a22 | 971 | doesn't I<necessarily> indicate an exceptional condition: C<pop> |
2f9daede TP |
972 | returns C<undef> when its argument is an empty array, I<or> when the |
973 | element to return happens to be C<undef>. | |
974 | ||
f10b0346 GS |
975 | You may also use C<defined(&func)> to check whether subroutine C<&func> |
976 | has ever been defined. The return value is unaffected by any forward | |
847c7ebe DD |
977 | declarations of C<&foo>. Note that a subroutine which is not defined |
978 | may still be callable: its package may have an C<AUTOLOAD> method that | |
979 | makes it spring into existence the first time that it is called -- see | |
980 | L<perlsub>. | |
f10b0346 GS |
981 | |
982 | Use of C<defined> on aggregates (hashes and arrays) is deprecated. It | |
983 | used to report whether memory for that aggregate has ever been | |
984 | allocated. This behavior may disappear in future versions of Perl. | |
985 | You should instead use a simple test for size: | |
986 | ||
987 | if (@an_array) { print "has array elements\n" } | |
988 | if (%a_hash) { print "has hash members\n" } | |
2f9daede TP |
989 | |
990 | When used on a hash element, it tells you whether the value is defined, | |
dc848c6f | 991 | not whether the key exists in the hash. Use L</exists> for the latter |
2f9daede | 992 | purpose. |
a0d0e21e LW |
993 | |
994 | Examples: | |
995 | ||
996 | print if defined $switch{'D'}; | |
997 | print "$val\n" while defined($val = pop(@ary)); | |
998 | die "Can't readlink $sym: $!" | |
999 | unless defined($value = readlink $sym); | |
a0d0e21e | 1000 | sub foo { defined &$bar ? &$bar(@_) : die "No bar"; } |
2f9daede | 1001 | $debugging = 0 unless defined $debugging; |
a0d0e21e | 1002 | |
19799a22 | 1003 | Note: Many folks tend to overuse C<defined>, and then are surprised to |
7660c0ab | 1004 | discover that the number C<0> and C<""> (the zero-length string) are, in fact, |
2f9daede | 1005 | defined values. For example, if you say |
a5f75d66 AD |
1006 | |
1007 | "ab" =~ /a(.*)b/; | |
1008 | ||
7660c0ab | 1009 | The pattern match succeeds, and C<$1> is defined, despite the fact that it |
a5f75d66 | 1010 | matched "nothing". But it didn't really match nothing--rather, it |
2b5ab1e7 | 1011 | matched something that happened to be zero characters long. This is all |
a5f75d66 | 1012 | very above-board and honest. When a function returns an undefined value, |
2f9daede | 1013 | it's an admission that it couldn't give you an honest answer. So you |
19799a22 | 1014 | should use C<defined> only when you're questioning the integrity of what |
7660c0ab | 1015 | you're trying to do. At other times, a simple comparison to C<0> or C<""> is |
2f9daede TP |
1016 | what you want. |
1017 | ||
dc848c6f | 1018 | See also L</undef>, L</exists>, L</ref>. |
2f9daede | 1019 | |
a0d0e21e LW |
1020 | =item delete EXPR |
1021 | ||
01020589 GS |
1022 | Given an expression that specifies a hash element, array element, hash slice, |
1023 | or array slice, deletes the specified element(s) from the hash or array. | |
8216c1fd | 1024 | In the case of an array, if the array elements happen to be at the end, |
b76cc8ba | 1025 | the size of the array will shrink to the highest element that tests |
8216c1fd | 1026 | true for exists() (or 0 if no such element exists). |
a0d0e21e | 1027 | |
01020589 GS |
1028 | Returns each element so deleted or the undefined value if there was no such |
1029 | element. Deleting from C<$ENV{}> modifies the environment. Deleting from | |
1030 | a hash tied to a DBM file deletes the entry from the DBM file. Deleting | |
1031 | from a C<tie>d hash or array may not necessarily return anything. | |
1032 | ||
8ea97a1e GS |
1033 | Deleting an array element effectively returns that position of the array |
1034 | to its initial, uninitialized state. Subsequently testing for the same | |
8216c1fd GS |
1035 | element with exists() will return false. Note that deleting array |
1036 | elements in the middle of an array will not shift the index of the ones | |
1037 | after them down--use splice() for that. See L</exists>. | |
8ea97a1e | 1038 | |
01020589 | 1039 | The following (inefficiently) deletes all the values of %HASH and @ARRAY: |
a0d0e21e | 1040 | |
5f05dabc | 1041 | foreach $key (keys %HASH) { |
1042 | delete $HASH{$key}; | |
a0d0e21e LW |
1043 | } |
1044 | ||
01020589 GS |
1045 | foreach $index (0 .. $#ARRAY) { |
1046 | delete $ARRAY[$index]; | |
1047 | } | |
1048 | ||
1049 | And so do these: | |
5f05dabc | 1050 | |
01020589 GS |
1051 | delete @HASH{keys %HASH}; |
1052 | ||
9740c838 | 1053 | delete @ARRAY[0 .. $#ARRAY]; |
5f05dabc | 1054 | |
2b5ab1e7 | 1055 | But both of these are slower than just assigning the empty list |
01020589 GS |
1056 | or undefining %HASH or @ARRAY: |
1057 | ||
1058 | %HASH = (); # completely empty %HASH | |
1059 | undef %HASH; # forget %HASH ever existed | |
2b5ab1e7 | 1060 | |
01020589 GS |
1061 | @ARRAY = (); # completely empty @ARRAY |
1062 | undef @ARRAY; # forget @ARRAY ever existed | |
2b5ab1e7 TC |
1063 | |
1064 | Note that the EXPR can be arbitrarily complicated as long as the final | |
01020589 GS |
1065 | operation is a hash element, array element, hash slice, or array slice |
1066 | lookup: | |
a0d0e21e LW |
1067 | |
1068 | delete $ref->[$x][$y]{$key}; | |
5f05dabc | 1069 | delete @{$ref->[$x][$y]}{$key1, $key2, @morekeys}; |
a0d0e21e | 1070 | |
01020589 GS |
1071 | delete $ref->[$x][$y][$index]; |
1072 | delete @{$ref->[$x][$y]}[$index1, $index2, @moreindices]; | |
1073 | ||
a0d0e21e LW |
1074 | =item die LIST |
1075 | ||
19799a22 GS |
1076 | Outside an C<eval>, prints the value of LIST to C<STDERR> and |
1077 | exits with the current value of C<$!> (errno). If C<$!> is C<0>, | |
61eff3bc JH |
1078 | exits with the value of C<<< ($? >> 8) >>> (backtick `command` |
1079 | status). If C<<< ($? >> 8) >>> is C<0>, exits with C<255>. Inside | |
19799a22 GS |
1080 | an C<eval(),> the error message is stuffed into C<$@> and the |
1081 | C<eval> is terminated with the undefined value. This makes | |
1082 | C<die> the way to raise an exception. | |
a0d0e21e LW |
1083 | |
1084 | Equivalent examples: | |
1085 | ||
1086 | die "Can't cd to spool: $!\n" unless chdir '/usr/spool/news'; | |
54310121 | 1087 | chdir '/usr/spool/news' or die "Can't cd to spool: $!\n" |
a0d0e21e | 1088 | |
ccac6780 | 1089 | If the last element of LIST does not end in a newline, the current |
df37ec69 WW |
1090 | script line number and input line number (if any) are also printed, |
1091 | and a newline is supplied. Note that the "input line number" (also | |
1092 | known as "chunk") is subject to whatever notion of "line" happens to | |
1093 | be currently in effect, and is also available as the special variable | |
1094 | C<$.>. See L<perlvar/"$/"> and L<perlvar/"$.">. | |
1095 | ||
1096 | Hint: sometimes appending C<", stopped"> to your message will cause it | |
1097 | to make better sense when the string C<"at foo line 123"> is appended. | |
1098 | Suppose you are running script "canasta". | |
a0d0e21e LW |
1099 | |
1100 | die "/etc/games is no good"; | |
1101 | die "/etc/games is no good, stopped"; | |
1102 | ||
1103 | produce, respectively | |
1104 | ||
1105 | /etc/games is no good at canasta line 123. | |
1106 | /etc/games is no good, stopped at canasta line 123. | |
1107 | ||
2b5ab1e7 | 1108 | See also exit(), warn(), and the Carp module. |
a0d0e21e | 1109 | |
7660c0ab A |
1110 | If LIST is empty and C<$@> already contains a value (typically from a |
1111 | previous eval) that value is reused after appending C<"\t...propagated">. | |
fb73857a | 1112 | This is useful for propagating exceptions: |
1113 | ||
1114 | eval { ... }; | |
1115 | die unless $@ =~ /Expected exception/; | |
1116 | ||
ad216e65 JH |
1117 | If LIST is empty and C<$@> contains an object reference that has a |
1118 | C<PROPAGATE> method, that method will be called with additional file | |
1119 | and line number parameters. The return value replaces the value in | |
67408cae | 1120 | C<$@>. ie. as if C<<$@ = eval { $@->PROPAGATE(__FILE__, __LINE__) };>> |
ad216e65 JH |
1121 | were called. |
1122 | ||
7660c0ab | 1123 | If C<$@> is empty then the string C<"Died"> is used. |
fb73857a | 1124 | |
52531d10 GS |
1125 | die() can also be called with a reference argument. If this happens to be |
1126 | trapped within an eval(), $@ contains the reference. This behavior permits | |
1127 | a more elaborate exception handling implementation using objects that | |
4375e838 | 1128 | maintain arbitrary state about the nature of the exception. Such a scheme |
52531d10 GS |
1129 | is sometimes preferable to matching particular string values of $@ using |
1130 | regular expressions. Here's an example: | |
1131 | ||
1132 | eval { ... ; die Some::Module::Exception->new( FOO => "bar" ) }; | |
1133 | if ($@) { | |
1134 | if (ref($@) && UNIVERSAL::isa($@,"Some::Module::Exception")) { | |
1135 | # handle Some::Module::Exception | |
1136 | } | |
1137 | else { | |
1138 | # handle all other possible exceptions | |
1139 | } | |
1140 | } | |
1141 | ||
19799a22 | 1142 | Because perl will stringify uncaught exception messages before displaying |
52531d10 GS |
1143 | them, you may want to overload stringification operations on such custom |
1144 | exception objects. See L<overload> for details about that. | |
1145 | ||
19799a22 GS |
1146 | You can arrange for a callback to be run just before the C<die> |
1147 | does its deed, by setting the C<$SIG{__DIE__}> hook. The associated | |
1148 | handler will be called with the error text and can change the error | |
1149 | message, if it sees fit, by calling C<die> again. See | |
1150 | L<perlvar/$SIG{expr}> for details on setting C<%SIG> entries, and | |
1151 | L<"eval BLOCK"> for some examples. Although this feature was meant | |
1152 | to be run only right before your program was to exit, this is not | |
1153 | currently the case--the C<$SIG{__DIE__}> hook is currently called | |
1154 | even inside eval()ed blocks/strings! If one wants the hook to do | |
1155 | nothing in such situations, put | |
fb73857a | 1156 | |
1157 | die @_ if $^S; | |
1158 | ||
19799a22 GS |
1159 | as the first line of the handler (see L<perlvar/$^S>). Because |
1160 | this promotes strange action at a distance, this counterintuitive | |
b76cc8ba | 1161 | behavior may be fixed in a future release. |
774d564b | 1162 | |
a0d0e21e LW |
1163 | =item do BLOCK |
1164 | ||
1165 | Not really a function. Returns the value of the last command in the | |
1166 | sequence of commands indicated by BLOCK. When modified by a loop | |
98293880 JH |
1167 | modifier, executes the BLOCK once before testing the loop condition. |
1168 | (On other statements the loop modifiers test the conditional first.) | |
a0d0e21e | 1169 | |
4968c1e4 | 1170 | C<do BLOCK> does I<not> count as a loop, so the loop control statements |
2b5ab1e7 TC |
1171 | C<next>, C<last>, or C<redo> cannot be used to leave or restart the block. |
1172 | See L<perlsyn> for alternative strategies. | |
4968c1e4 | 1173 | |
a0d0e21e LW |
1174 | =item do SUBROUTINE(LIST) |
1175 | ||
1176 | A deprecated form of subroutine call. See L<perlsub>. | |
1177 | ||
1178 | =item do EXPR | |
1179 | ||
1180 | Uses the value of EXPR as a filename and executes the contents of the | |
1181 | file as a Perl script. Its primary use is to include subroutines | |
1182 | from a Perl subroutine library. | |
1183 | ||
1184 | do 'stat.pl'; | |
1185 | ||
1186 | is just like | |
1187 | ||
986b19de | 1188 | eval `cat stat.pl`; |
a0d0e21e | 1189 | |
2b5ab1e7 TC |
1190 | except that it's more efficient and concise, keeps track of the current |
1191 | filename for error messages, searches the @INC libraries, and updates | |
1192 | C<%INC> if the file is found. See L<perlvar/Predefined Names> for these | |
1193 | variables. It also differs in that code evaluated with C<do FILENAME> | |
1194 | cannot see lexicals in the enclosing scope; C<eval STRING> does. It's the | |
1195 | same, however, in that it does reparse the file every time you call it, | |
1196 | so you probably don't want to do this inside a loop. | |
a0d0e21e | 1197 | |
8e30cc93 | 1198 | If C<do> cannot read the file, it returns undef and sets C<$!> to the |
2b5ab1e7 | 1199 | error. If C<do> can read the file but cannot compile it, it |
8e30cc93 MG |
1200 | returns undef and sets an error message in C<$@>. If the file is |
1201 | successfully compiled, C<do> returns the value of the last expression | |
1202 | evaluated. | |
1203 | ||
a0d0e21e | 1204 | Note that inclusion of library modules is better done with the |
19799a22 | 1205 | C<use> and C<require> operators, which also do automatic error checking |
4633a7c4 | 1206 | and raise an exception if there's a problem. |
a0d0e21e | 1207 | |
5a964f20 TC |
1208 | You might like to use C<do> to read in a program configuration |
1209 | file. Manual error checking can be done this way: | |
1210 | ||
b76cc8ba | 1211 | # read in config files: system first, then user |
f86cebdf | 1212 | for $file ("/share/prog/defaults.rc", |
b76cc8ba | 1213 | "$ENV{HOME}/.someprogrc") |
2b5ab1e7 | 1214 | { |
5a964f20 | 1215 | unless ($return = do $file) { |
f86cebdf GS |
1216 | warn "couldn't parse $file: $@" if $@; |
1217 | warn "couldn't do $file: $!" unless defined $return; | |
1218 | warn "couldn't run $file" unless $return; | |
5a964f20 TC |
1219 | } |
1220 | } | |
1221 | ||
a0d0e21e LW |
1222 | =item dump LABEL |
1223 | ||
1614b0e3 JD |
1224 | =item dump |
1225 | ||
19799a22 GS |
1226 | This function causes an immediate core dump. See also the B<-u> |
1227 | command-line switch in L<perlrun>, which does the same thing. | |
1228 | Primarily this is so that you can use the B<undump> program (not | |
1229 | supplied) to turn your core dump into an executable binary after | |
1230 | having initialized all your variables at the beginning of the | |
1231 | program. When the new binary is executed it will begin by executing | |
1232 | a C<goto LABEL> (with all the restrictions that C<goto> suffers). | |
1233 | Think of it as a goto with an intervening core dump and reincarnation. | |
1234 | If C<LABEL> is omitted, restarts the program from the top. | |
1235 | ||
1236 | B<WARNING>: Any files opened at the time of the dump will I<not> | |
1237 | be open any more when the program is reincarnated, with possible | |
b76cc8ba | 1238 | resulting confusion on the part of Perl. |
19799a22 GS |
1239 | |
1240 | This function is now largely obsolete, partly because it's very | |
1241 | hard to convert a core file into an executable, and because the | |
1242 | real compiler backends for generating portable bytecode and compilable | |
ac206dc8 RGS |
1243 | C code have superseded it. That's why you should now invoke it as |
1244 | C<CORE::dump()>, if you don't want to be warned against a possible | |
1245 | typo. | |
19799a22 GS |
1246 | |
1247 | If you're looking to use L<dump> to speed up your program, consider | |
1248 | generating bytecode or native C code as described in L<perlcc>. If | |
1249 | you're just trying to accelerate a CGI script, consider using the | |
210b36aa | 1250 | C<mod_perl> extension to B<Apache>, or the CPAN module, CGI::Fast. |
19799a22 | 1251 | You might also consider autoloading or selfloading, which at least |
b76cc8ba | 1252 | make your program I<appear> to run faster. |
5a964f20 | 1253 | |
aa689395 | 1254 | =item each HASH |
1255 | ||
5a964f20 | 1256 | When called in list context, returns a 2-element list consisting of the |
aa689395 | 1257 | key and value for the next element of a hash, so that you can iterate over |
74fc8b5f | 1258 | it. When called in scalar context, returns only the key for the next |
e902a979 | 1259 | element in the hash. |
2f9daede | 1260 | |
ab192400 GS |
1261 | Entries are returned in an apparently random order. The actual random |
1262 | order is subject to change in future versions of perl, but it is guaranteed | |
19799a22 | 1263 | to be in the same order as either the C<keys> or C<values> function |
ab192400 GS |
1264 | would produce on the same (unmodified) hash. |
1265 | ||
1266 | When the hash is entirely read, a null array is returned in list context | |
19799a22 GS |
1267 | (which when assigned produces a false (C<0>) value), and C<undef> in |
1268 | scalar context. The next call to C<each> after that will start iterating | |
1269 | again. There is a single iterator for each hash, shared by all C<each>, | |
1270 | C<keys>, and C<values> function calls in the program; it can be reset by | |
2f9daede TP |
1271 | reading all the elements from the hash, or by evaluating C<keys HASH> or |
1272 | C<values HASH>. If you add or delete elements of a hash while you're | |
74fc8b5f MJD |
1273 | iterating over it, you may get entries skipped or duplicated, so |
1274 | don't. Exception: It is always safe to delete the item most recently | |
1275 | returned by C<each()>, which means that the following code will work: | |
1276 | ||
1277 | while (($key, $value) = each %hash) { | |
1278 | print $key, "\n"; | |
1279 | delete $hash{$key}; # This is safe | |
1280 | } | |
aa689395 | 1281 | |
f86cebdf | 1282 | The following prints out your environment like the printenv(1) program, |
aa689395 | 1283 | only in a different order: |
a0d0e21e LW |
1284 | |
1285 | while (($key,$value) = each %ENV) { | |
1286 | print "$key=$value\n"; | |
1287 | } | |
1288 | ||
19799a22 | 1289 | See also C<keys>, C<values> and C<sort>. |
a0d0e21e LW |
1290 | |
1291 | =item eof FILEHANDLE | |
1292 | ||
4633a7c4 LW |
1293 | =item eof () |
1294 | ||
a0d0e21e LW |
1295 | =item eof |
1296 | ||
1297 | Returns 1 if the next read on FILEHANDLE will return end of file, or if | |
1298 | FILEHANDLE is not open. FILEHANDLE may be an expression whose value | |
5a964f20 | 1299 | gives the real filehandle. (Note that this function actually |
19799a22 | 1300 | reads a character and then C<ungetc>s it, so isn't very useful in an |
748a9306 | 1301 | interactive context.) Do not read from a terminal file (or call |
19799a22 | 1302 | C<eof(FILEHANDLE)> on it) after end-of-file is reached. File types such |
748a9306 LW |
1303 | as terminals may lose the end-of-file condition if you do. |
1304 | ||
820475bd GS |
1305 | An C<eof> without an argument uses the last file read. Using C<eof()> |
1306 | with empty parentheses is very different. It refers to the pseudo file | |
1307 | formed from the files listed on the command line and accessed via the | |
61eff3bc JH |
1308 | C<< <> >> operator. Since C<< <> >> isn't explicitly opened, |
1309 | as a normal filehandle is, an C<eof()> before C<< <> >> has been | |
820475bd | 1310 | used will cause C<@ARGV> to be examined to determine if input is |
67408cae | 1311 | available. Similarly, an C<eof()> after C<< <> >> has returned |
efdd0218 RB |
1312 | end-of-file will assume you are processing another C<@ARGV> list, |
1313 | and if you haven't set C<@ARGV>, will read input from C<STDIN>; | |
1314 | see L<perlop/"I/O Operators">. | |
820475bd | 1315 | |
61eff3bc | 1316 | In a C<< while (<>) >> loop, C<eof> or C<eof(ARGV)> can be used to |
820475bd GS |
1317 | detect the end of each file, C<eof()> will only detect the end of the |
1318 | last file. Examples: | |
a0d0e21e | 1319 | |
748a9306 LW |
1320 | # reset line numbering on each input file |
1321 | while (<>) { | |
b76cc8ba | 1322 | next if /^\s*#/; # skip comments |
748a9306 | 1323 | print "$.\t$_"; |
5a964f20 TC |
1324 | } continue { |
1325 | close ARGV if eof; # Not eof()! | |
748a9306 LW |
1326 | } |
1327 | ||
a0d0e21e LW |
1328 | # insert dashes just before last line of last file |
1329 | while (<>) { | |
5a964f20 | 1330 | if (eof()) { # check for end of current file |
a0d0e21e | 1331 | print "--------------\n"; |
2b5ab1e7 | 1332 | close(ARGV); # close or last; is needed if we |
748a9306 | 1333 | # are reading from the terminal |
a0d0e21e LW |
1334 | } |
1335 | print; | |
1336 | } | |
1337 | ||
a0d0e21e | 1338 | Practical hint: you almost never need to use C<eof> in Perl, because the |
3ce0d271 GS |
1339 | input operators typically return C<undef> when they run out of data, or if |
1340 | there was an error. | |
a0d0e21e LW |
1341 | |
1342 | =item eval EXPR | |
1343 | ||
1344 | =item eval BLOCK | |
1345 | ||
c7cc6f1c GS |
1346 | In the first form, the return value of EXPR is parsed and executed as if it |
1347 | were a little Perl program. The value of the expression (which is itself | |
5a964f20 | 1348 | determined within scalar context) is first parsed, and if there weren't any |
be3174d2 GS |
1349 | errors, executed in the lexical context of the current Perl program, so |
1350 | that any variable settings or subroutine and format definitions remain | |
1351 | afterwards. Note that the value is parsed every time the eval executes. | |
1352 | If EXPR is omitted, evaluates C<$_>. This form is typically used to | |
1353 | delay parsing and subsequent execution of the text of EXPR until run time. | |
c7cc6f1c GS |
1354 | |
1355 | In the second form, the code within the BLOCK is parsed only once--at the | |
1356 | same time the code surrounding the eval itself was parsed--and executed | |
1357 | within the context of the current Perl program. This form is typically | |
1358 | used to trap exceptions more efficiently than the first (see below), while | |
1359 | also providing the benefit of checking the code within BLOCK at compile | |
1360 | time. | |
1361 | ||
1362 | The final semicolon, if any, may be omitted from the value of EXPR or within | |
1363 | the BLOCK. | |
1364 | ||
1365 | In both forms, the value returned is the value of the last expression | |
5a964f20 | 1366 | evaluated inside the mini-program; a return statement may be also used, just |
c7cc6f1c | 1367 | as with subroutines. The expression providing the return value is evaluated |
5a964f20 | 1368 | in void, scalar, or list context, depending on the context of the eval itself. |
c7cc6f1c | 1369 | See L</wantarray> for more on how the evaluation context can be determined. |
a0d0e21e | 1370 | |
19799a22 GS |
1371 | If there is a syntax error or runtime error, or a C<die> statement is |
1372 | executed, an undefined value is returned by C<eval>, and C<$@> is set to the | |
a0d0e21e | 1373 | error message. If there was no error, C<$@> is guaranteed to be a null |
19799a22 | 1374 | string. Beware that using C<eval> neither silences perl from printing |
c7cc6f1c | 1375 | warnings to STDERR, nor does it stuff the text of warning messages into C<$@>. |
d9984052 A |
1376 | To do either of those, you have to use the C<$SIG{__WARN__}> facility, or |
1377 | turn off warnings inside the BLOCK or EXPR using S<C<no warnings 'all'>>. | |
1378 | See L</warn>, L<perlvar>, L<warnings> and L<perllexwarn>. | |
a0d0e21e | 1379 | |
19799a22 GS |
1380 | Note that, because C<eval> traps otherwise-fatal errors, it is useful for |
1381 | determining whether a particular feature (such as C<socket> or C<symlink>) | |
a0d0e21e LW |
1382 | is implemented. It is also Perl's exception trapping mechanism, where |
1383 | the die operator is used to raise exceptions. | |
1384 | ||
1385 | If the code to be executed doesn't vary, you may use the eval-BLOCK | |
1386 | form to trap run-time errors without incurring the penalty of | |
1387 | recompiling each time. The error, if any, is still returned in C<$@>. | |
1388 | Examples: | |
1389 | ||
54310121 | 1390 | # make divide-by-zero nonfatal |
a0d0e21e LW |
1391 | eval { $answer = $a / $b; }; warn $@ if $@; |
1392 | ||
1393 | # same thing, but less efficient | |
1394 | eval '$answer = $a / $b'; warn $@ if $@; | |
1395 | ||
1396 | # a compile-time error | |
5a964f20 | 1397 | eval { $answer = }; # WRONG |
a0d0e21e LW |
1398 | |
1399 | # a run-time error | |
1400 | eval '$answer ='; # sets $@ | |
1401 | ||
2b5ab1e7 TC |
1402 | Due to the current arguably broken state of C<__DIE__> hooks, when using |
1403 | the C<eval{}> form as an exception trap in libraries, you may wish not | |
1404 | to trigger any C<__DIE__> hooks that user code may have installed. | |
1405 | You can use the C<local $SIG{__DIE__}> construct for this purpose, | |
1406 | as shown in this example: | |
774d564b | 1407 | |
1408 | # a very private exception trap for divide-by-zero | |
f86cebdf GS |
1409 | eval { local $SIG{'__DIE__'}; $answer = $a / $b; }; |
1410 | warn $@ if $@; | |
774d564b | 1411 | |
1412 | This is especially significant, given that C<__DIE__> hooks can call | |
19799a22 | 1413 | C<die> again, which has the effect of changing their error messages: |
774d564b | 1414 | |
1415 | # __DIE__ hooks may modify error messages | |
1416 | { | |
f86cebdf GS |
1417 | local $SIG{'__DIE__'} = |
1418 | sub { (my $x = $_[0]) =~ s/foo/bar/g; die $x }; | |
c7cc6f1c GS |
1419 | eval { die "foo lives here" }; |
1420 | print $@ if $@; # prints "bar lives here" | |
774d564b | 1421 | } |
1422 | ||
19799a22 | 1423 | Because this promotes action at a distance, this counterintuitive behavior |
2b5ab1e7 TC |
1424 | may be fixed in a future release. |
1425 | ||
19799a22 | 1426 | With an C<eval>, you should be especially careful to remember what's |
a0d0e21e LW |
1427 | being looked at when: |
1428 | ||
1429 | eval $x; # CASE 1 | |
1430 | eval "$x"; # CASE 2 | |
1431 | ||
1432 | eval '$x'; # CASE 3 | |
1433 | eval { $x }; # CASE 4 | |
1434 | ||
5a964f20 | 1435 | eval "\$$x++"; # CASE 5 |
a0d0e21e LW |
1436 | $$x++; # CASE 6 |
1437 | ||
2f9daede | 1438 | Cases 1 and 2 above behave identically: they run the code contained in |
19799a22 | 1439 | the variable $x. (Although case 2 has misleading double quotes making |
2f9daede | 1440 | the reader wonder what else might be happening (nothing is).) Cases 3 |
7660c0ab | 1441 | and 4 likewise behave in the same way: they run the code C<'$x'>, which |
19799a22 | 1442 | does nothing but return the value of $x. (Case 4 is preferred for |
2f9daede TP |
1443 | purely visual reasons, but it also has the advantage of compiling at |
1444 | compile-time instead of at run-time.) Case 5 is a place where | |
19799a22 | 1445 | normally you I<would> like to use double quotes, except that in this |
2f9daede TP |
1446 | particular situation, you can just use symbolic references instead, as |
1447 | in case 6. | |
a0d0e21e | 1448 | |
4968c1e4 | 1449 | C<eval BLOCK> does I<not> count as a loop, so the loop control statements |
2b5ab1e7 | 1450 | C<next>, C<last>, or C<redo> cannot be used to leave or restart the block. |
4968c1e4 | 1451 | |
a0d0e21e LW |
1452 | =item exec LIST |
1453 | ||
8bf3b016 GS |
1454 | =item exec PROGRAM LIST |
1455 | ||
19799a22 GS |
1456 | The C<exec> function executes a system command I<and never returns>-- |
1457 | use C<system> instead of C<exec> if you want it to return. It fails and | |
1458 | returns false only if the command does not exist I<and> it is executed | |
fb73857a | 1459 | directly instead of via your system's command shell (see below). |
a0d0e21e | 1460 | |
19799a22 GS |
1461 | Since it's a common mistake to use C<exec> instead of C<system>, Perl |
1462 | warns you if there is a following statement which isn't C<die>, C<warn>, | |
1463 | or C<exit> (if C<-w> is set - but you always do that). If you | |
1464 | I<really> want to follow an C<exec> with some other statement, you | |
55d729e4 GS |
1465 | can use one of these styles to avoid the warning: |
1466 | ||
5a964f20 TC |
1467 | exec ('foo') or print STDERR "couldn't exec foo: $!"; |
1468 | { exec ('foo') }; print STDERR "couldn't exec foo: $!"; | |
55d729e4 | 1469 | |
5a964f20 | 1470 | If there is more than one argument in LIST, or if LIST is an array |
f86cebdf | 1471 | with more than one value, calls execvp(3) with the arguments in LIST. |
5a964f20 TC |
1472 | If there is only one scalar argument or an array with one element in it, |
1473 | the argument is checked for shell metacharacters, and if there are any, | |
1474 | the entire argument is passed to the system's command shell for parsing | |
1475 | (this is C</bin/sh -c> on Unix platforms, but varies on other platforms). | |
1476 | If there are no shell metacharacters in the argument, it is split into | |
b76cc8ba | 1477 | words and passed directly to C<execvp>, which is more efficient. |
19799a22 | 1478 | Examples: |
a0d0e21e | 1479 | |
19799a22 GS |
1480 | exec '/bin/echo', 'Your arguments are: ', @ARGV; |
1481 | exec "sort $outfile | uniq"; | |
a0d0e21e LW |
1482 | |
1483 | If you don't really want to execute the first argument, but want to lie | |
1484 | to the program you are executing about its own name, you can specify | |
1485 | the program you actually want to run as an "indirect object" (without a | |
1486 | comma) in front of the LIST. (This always forces interpretation of the | |
54310121 | 1487 | LIST as a multivalued list, even if there is only a single scalar in |
a0d0e21e LW |
1488 | the list.) Example: |
1489 | ||
1490 | $shell = '/bin/csh'; | |
1491 | exec $shell '-sh'; # pretend it's a login shell | |
1492 | ||
1493 | or, more directly, | |
1494 | ||
1495 | exec {'/bin/csh'} '-sh'; # pretend it's a login shell | |
1496 | ||
bb32b41a GS |
1497 | When the arguments get executed via the system shell, results will |
1498 | be subject to its quirks and capabilities. See L<perlop/"`STRING`"> | |
1499 | for details. | |
1500 | ||
19799a22 GS |
1501 | Using an indirect object with C<exec> or C<system> is also more |
1502 | secure. This usage (which also works fine with system()) forces | |
1503 | interpretation of the arguments as a multivalued list, even if the | |
1504 | list had just one argument. That way you're safe from the shell | |
1505 | expanding wildcards or splitting up words with whitespace in them. | |
5a964f20 TC |
1506 | |
1507 | @args = ( "echo surprise" ); | |
1508 | ||
2b5ab1e7 | 1509 | exec @args; # subject to shell escapes |
f86cebdf | 1510 | # if @args == 1 |
2b5ab1e7 | 1511 | exec { $args[0] } @args; # safe even with one-arg list |
5a964f20 TC |
1512 | |
1513 | The first version, the one without the indirect object, ran the I<echo> | |
1514 | program, passing it C<"surprise"> an argument. The second version | |
1515 | didn't--it tried to run a program literally called I<"echo surprise">, | |
1516 | didn't find it, and set C<$?> to a non-zero value indicating failure. | |
1517 | ||
0f897271 GS |
1518 | Beginning with v5.6.0, Perl will attempt to flush all files opened for |
1519 | output before the exec, but this may not be supported on some platforms | |
1520 | (see L<perlport>). To be safe, you may need to set C<$|> ($AUTOFLUSH | |
1521 | in English) or call the C<autoflush()> method of C<IO::Handle> on any | |
1522 | open handles in order to avoid lost output. | |
1523 | ||
19799a22 | 1524 | Note that C<exec> will not call your C<END> blocks, nor will it call |
7660c0ab A |
1525 | any C<DESTROY> methods in your objects. |
1526 | ||
a0d0e21e LW |
1527 | =item exists EXPR |
1528 | ||
01020589 | 1529 | Given an expression that specifies a hash element or array element, |
8ea97a1e GS |
1530 | returns true if the specified element in the hash or array has ever |
1531 | been initialized, even if the corresponding value is undefined. The | |
1532 | element is not autovivified if it doesn't exist. | |
a0d0e21e | 1533 | |
01020589 GS |
1534 | print "Exists\n" if exists $hash{$key}; |
1535 | print "Defined\n" if defined $hash{$key}; | |
1536 | print "True\n" if $hash{$key}; | |
1537 | ||
1538 | print "Exists\n" if exists $array[$index]; | |
1539 | print "Defined\n" if defined $array[$index]; | |
1540 | print "True\n" if $array[$index]; | |
a0d0e21e | 1541 | |
8ea97a1e | 1542 | A hash or array element can be true only if it's defined, and defined if |
a0d0e21e LW |
1543 | it exists, but the reverse doesn't necessarily hold true. |
1544 | ||
afebc493 GS |
1545 | Given an expression that specifies the name of a subroutine, |
1546 | returns true if the specified subroutine has ever been declared, even | |
1547 | if it is undefined. Mentioning a subroutine name for exists or defined | |
847c7ebe DD |
1548 | does not count as declaring it. Note that a subroutine which does not |
1549 | exist may still be callable: its package may have an C<AUTOLOAD> | |
1550 | method that makes it spring into existence the first time that it is | |
1551 | called -- see L<perlsub>. | |
afebc493 GS |
1552 | |
1553 | print "Exists\n" if exists &subroutine; | |
1554 | print "Defined\n" if defined &subroutine; | |
1555 | ||
a0d0e21e | 1556 | Note that the EXPR can be arbitrarily complicated as long as the final |
afebc493 | 1557 | operation is a hash or array key lookup or subroutine name: |
a0d0e21e | 1558 | |
2b5ab1e7 TC |
1559 | if (exists $ref->{A}->{B}->{$key}) { } |
1560 | if (exists $hash{A}{B}{$key}) { } | |
1561 | ||
01020589 GS |
1562 | if (exists $ref->{A}->{B}->[$ix]) { } |
1563 | if (exists $hash{A}{B}[$ix]) { } | |
1564 | ||
afebc493 GS |
1565 | if (exists &{$ref->{A}{B}{$key}}) { } |
1566 | ||
01020589 GS |
1567 | Although the deepest nested array or hash will not spring into existence |
1568 | just because its existence was tested, any intervening ones will. | |
61eff3bc | 1569 | Thus C<< $ref->{"A"} >> and C<< $ref->{"A"}->{"B"} >> will spring |
01020589 GS |
1570 | into existence due to the existence test for the $key element above. |
1571 | This happens anywhere the arrow operator is used, including even: | |
5a964f20 | 1572 | |
2b5ab1e7 TC |
1573 | undef $ref; |
1574 | if (exists $ref->{"Some key"}) { } | |
1575 | print $ref; # prints HASH(0x80d3d5c) | |
1576 | ||
1577 | This surprising autovivification in what does not at first--or even | |
1578 | second--glance appear to be an lvalue context may be fixed in a future | |
5a964f20 | 1579 | release. |
a0d0e21e | 1580 | |
afebc493 GS |
1581 | Use of a subroutine call, rather than a subroutine name, as an argument |
1582 | to exists() is an error. | |
1583 | ||
1584 | exists ⊂ # OK | |
1585 | exists &sub(); # Error | |
1586 | ||
a0d0e21e LW |
1587 | =item exit EXPR |
1588 | ||
2b5ab1e7 | 1589 | Evaluates EXPR and exits immediately with that value. Example: |
a0d0e21e LW |
1590 | |
1591 | $ans = <STDIN>; | |
1592 | exit 0 if $ans =~ /^[Xx]/; | |
1593 | ||
19799a22 | 1594 | See also C<die>. If EXPR is omitted, exits with C<0> status. The only |
2b5ab1e7 TC |
1595 | universally recognized values for EXPR are C<0> for success and C<1> |
1596 | for error; other values are subject to interpretation depending on the | |
1597 | environment in which the Perl program is running. For example, exiting | |
1598 | 69 (EX_UNAVAILABLE) from a I<sendmail> incoming-mail filter will cause | |
1599 | the mailer to return the item undelivered, but that's not true everywhere. | |
a0d0e21e | 1600 | |
19799a22 GS |
1601 | Don't use C<exit> to abort a subroutine if there's any chance that |
1602 | someone might want to trap whatever error happened. Use C<die> instead, | |
1603 | which can be trapped by an C<eval>. | |
28757baa | 1604 | |
19799a22 | 1605 | The exit() function does not always exit immediately. It calls any |
2b5ab1e7 | 1606 | defined C<END> routines first, but these C<END> routines may not |
19799a22 | 1607 | themselves abort the exit. Likewise any object destructors that need to |
2b5ab1e7 TC |
1608 | be called are called before the real exit. If this is a problem, you |
1609 | can call C<POSIX:_exit($status)> to avoid END and destructor processing. | |
87275199 | 1610 | See L<perlmod> for details. |
5a964f20 | 1611 | |
a0d0e21e LW |
1612 | =item exp EXPR |
1613 | ||
54310121 | 1614 | =item exp |
bbce6d69 | 1615 | |
b76cc8ba | 1616 | Returns I<e> (the natural logarithm base) to the power of EXPR. |
a0d0e21e LW |
1617 | If EXPR is omitted, gives C<exp($_)>. |
1618 | ||
1619 | =item fcntl FILEHANDLE,FUNCTION,SCALAR | |
1620 | ||
f86cebdf | 1621 | Implements the fcntl(2) function. You'll probably have to say |
a0d0e21e LW |
1622 | |
1623 | use Fcntl; | |
1624 | ||
0ade1984 | 1625 | first to get the correct constant definitions. Argument processing and |
b76cc8ba | 1626 | value return works just like C<ioctl> below. |
a0d0e21e LW |
1627 | For example: |
1628 | ||
1629 | use Fcntl; | |
5a964f20 TC |
1630 | fcntl($filehandle, F_GETFL, $packed_return_buffer) |
1631 | or die "can't fcntl F_GETFL: $!"; | |
1632 | ||
19799a22 | 1633 | You don't have to check for C<defined> on the return from C<fnctl>. |
951ba7fe GS |
1634 | Like C<ioctl>, it maps a C<0> return from the system call into |
1635 | C<"0 but true"> in Perl. This string is true in boolean context and C<0> | |
2b5ab1e7 TC |
1636 | in numeric context. It is also exempt from the normal B<-w> warnings |
1637 | on improper numeric conversions. | |
5a964f20 | 1638 | |
19799a22 | 1639 | Note that C<fcntl> will produce a fatal error if used on a machine that |
2b5ab1e7 TC |
1640 | doesn't implement fcntl(2). See the Fcntl module or your fcntl(2) |
1641 | manpage to learn what functions are available on your system. | |
a0d0e21e LW |
1642 | |
1643 | =item fileno FILEHANDLE | |
1644 | ||
2b5ab1e7 TC |
1645 | Returns the file descriptor for a filehandle, or undefined if the |
1646 | filehandle is not open. This is mainly useful for constructing | |
19799a22 | 1647 | bitmaps for C<select> and low-level POSIX tty-handling operations. |
2b5ab1e7 TC |
1648 | If FILEHANDLE is an expression, the value is taken as an indirect |
1649 | filehandle, generally its name. | |
5a964f20 | 1650 | |
b76cc8ba | 1651 | You can use this to find out whether two handles refer to the |
5a964f20 TC |
1652 | same underlying descriptor: |
1653 | ||
1654 | if (fileno(THIS) == fileno(THAT)) { | |
1655 | print "THIS and THAT are dups\n"; | |
b76cc8ba NIS |
1656 | } |
1657 | ||
1658 | (Filehandles connected to memory objects via new features of C<open> may | |
1659 | return undefined even though they are open.) | |
1660 | ||
a0d0e21e LW |
1661 | |
1662 | =item flock FILEHANDLE,OPERATION | |
1663 | ||
19799a22 GS |
1664 | Calls flock(2), or an emulation of it, on FILEHANDLE. Returns true |
1665 | for success, false on failure. Produces a fatal error if used on a | |
2b5ab1e7 | 1666 | machine that doesn't implement flock(2), fcntl(2) locking, or lockf(3). |
19799a22 | 1667 | C<flock> is Perl's portable file locking interface, although it locks |
2b5ab1e7 TC |
1668 | only entire files, not records. |
1669 | ||
1670 | Two potentially non-obvious but traditional C<flock> semantics are | |
1671 | that it waits indefinitely until the lock is granted, and that its locks | |
1672 | B<merely advisory>. Such discretionary locks are more flexible, but offer | |
19799a22 GS |
1673 | fewer guarantees. This means that files locked with C<flock> may be |
1674 | modified by programs that do not also use C<flock>. See L<perlport>, | |
2b5ab1e7 TC |
1675 | your port's specific documentation, or your system-specific local manpages |
1676 | for details. It's best to assume traditional behavior if you're writing | |
1677 | portable programs. (But if you're not, you should as always feel perfectly | |
1678 | free to write for your own system's idiosyncrasies (sometimes called | |
1679 | "features"). Slavish adherence to portability concerns shouldn't get | |
1680 | in the way of your getting your job done.) | |
a3cb178b | 1681 | |
8ebc5c01 | 1682 | OPERATION is one of LOCK_SH, LOCK_EX, or LOCK_UN, possibly combined with |
1683 | LOCK_NB. These constants are traditionally valued 1, 2, 8 and 4, but | |
ea3105be | 1684 | you can use the symbolic names if you import them from the Fcntl module, |
68dc0745 | 1685 | either individually, or as a group using the ':flock' tag. LOCK_SH |
1686 | requests a shared lock, LOCK_EX requests an exclusive lock, and LOCK_UN | |
ea3105be GS |
1687 | releases a previously requested lock. If LOCK_NB is bitwise-or'ed with |
1688 | LOCK_SH or LOCK_EX then C<flock> will return immediately rather than blocking | |
68dc0745 | 1689 | waiting for the lock (check the return status to see if you got it). |
1690 | ||
2b5ab1e7 TC |
1691 | To avoid the possibility of miscoordination, Perl now flushes FILEHANDLE |
1692 | before locking or unlocking it. | |
8ebc5c01 | 1693 | |
f86cebdf | 1694 | Note that the emulation built with lockf(3) doesn't provide shared |
8ebc5c01 | 1695 | locks, and it requires that FILEHANDLE be open with write intent. These |
2b5ab1e7 | 1696 | are the semantics that lockf(3) implements. Most if not all systems |
f86cebdf | 1697 | implement lockf(3) in terms of fcntl(2) locking, though, so the |
8ebc5c01 | 1698 | differing semantics shouldn't bite too many people. |
1699 | ||
becacb53 TM |
1700 | Note that the fcntl(2) emulation of flock(3) requires that FILEHANDLE |
1701 | be open with read intent to use LOCK_SH and requires that it be open | |
1702 | with write intent to use LOCK_EX. | |
1703 | ||
19799a22 GS |
1704 | Note also that some versions of C<flock> cannot lock things over the |
1705 | network; you would need to use the more system-specific C<fcntl> for | |
f86cebdf GS |
1706 | that. If you like you can force Perl to ignore your system's flock(2) |
1707 | function, and so provide its own fcntl(2)-based emulation, by passing | |
8ebc5c01 | 1708 | the switch C<-Ud_flock> to the F<Configure> program when you configure |
1709 | perl. | |
4633a7c4 LW |
1710 | |
1711 | Here's a mailbox appender for BSD systems. | |
a0d0e21e | 1712 | |
7e1af8bc | 1713 | use Fcntl ':flock'; # import LOCK_* constants |
a0d0e21e LW |
1714 | |
1715 | sub lock { | |
7e1af8bc | 1716 | flock(MBOX,LOCK_EX); |
a0d0e21e LW |
1717 | # and, in case someone appended |
1718 | # while we were waiting... | |
1719 | seek(MBOX, 0, 2); | |
1720 | } | |
1721 | ||
1722 | sub unlock { | |
7e1af8bc | 1723 | flock(MBOX,LOCK_UN); |
a0d0e21e LW |
1724 | } |
1725 | ||
1726 | open(MBOX, ">>/usr/spool/mail/$ENV{'USER'}") | |
1727 | or die "Can't open mailbox: $!"; | |
1728 | ||
1729 | lock(); | |
1730 | print MBOX $msg,"\n\n"; | |
1731 | unlock(); | |
1732 | ||
2b5ab1e7 TC |
1733 | On systems that support a real flock(), locks are inherited across fork() |
1734 | calls, whereas those that must resort to the more capricious fcntl() | |
1735 | function lose the locks, making it harder to write servers. | |
1736 | ||
cb1a09d0 | 1737 | See also L<DB_File> for other flock() examples. |
a0d0e21e LW |
1738 | |
1739 | =item fork | |
1740 | ||
2b5ab1e7 TC |
1741 | Does a fork(2) system call to create a new process running the |
1742 | same program at the same point. It returns the child pid to the | |
1743 | parent process, C<0> to the child process, or C<undef> if the fork is | |
1744 | unsuccessful. File descriptors (and sometimes locks on those descriptors) | |
1745 | are shared, while everything else is copied. On most systems supporting | |
1746 | fork(), great care has gone into making it extremely efficient (for | |
1747 | example, using copy-on-write technology on data pages), making it the | |
1748 | dominant paradigm for multitasking over the last few decades. | |
5a964f20 | 1749 | |
0f897271 GS |
1750 | Beginning with v5.6.0, Perl will attempt to flush all files opened for |
1751 | output before forking the child process, but this may not be supported | |
1752 | on some platforms (see L<perlport>). To be safe, you may need to set | |
1753 | C<$|> ($AUTOFLUSH in English) or call the C<autoflush()> method of | |
1754 | C<IO::Handle> on any open handles in order to avoid duplicate output. | |
a0d0e21e | 1755 | |
19799a22 | 1756 | If you C<fork> without ever waiting on your children, you will |
2b5ab1e7 TC |
1757 | accumulate zombies. On some systems, you can avoid this by setting |
1758 | C<$SIG{CHLD}> to C<"IGNORE">. See also L<perlipc> for more examples of | |
1759 | forking and reaping moribund children. | |
cb1a09d0 | 1760 | |
28757baa | 1761 | Note that if your forked child inherits system file descriptors like |
1762 | STDIN and STDOUT that are actually connected by a pipe or socket, even | |
2b5ab1e7 | 1763 | if you exit, then the remote server (such as, say, a CGI script or a |
19799a22 | 1764 | backgrounded job launched from a remote shell) won't think you're done. |
2b5ab1e7 | 1765 | You should reopen those to F</dev/null> if it's any issue. |
28757baa | 1766 | |
cb1a09d0 AD |
1767 | =item format |
1768 | ||
19799a22 | 1769 | Declare a picture format for use by the C<write> function. For |
cb1a09d0 AD |
1770 | example: |
1771 | ||
54310121 | 1772 | format Something = |
cb1a09d0 AD |
1773 | Test: @<<<<<<<< @||||| @>>>>> |
1774 | $str, $%, '$' . int($num) | |
1775 | . | |
1776 | ||
1777 | $str = "widget"; | |
184e9718 | 1778 | $num = $cost/$quantity; |
cb1a09d0 AD |
1779 | $~ = 'Something'; |
1780 | write; | |
1781 | ||
1782 | See L<perlform> for many details and examples. | |
1783 | ||
8903cb82 | 1784 | =item formline PICTURE,LIST |
a0d0e21e | 1785 | |
5a964f20 | 1786 | This is an internal function used by C<format>s, though you may call it, |
a0d0e21e LW |
1787 | too. It formats (see L<perlform>) a list of values according to the |
1788 | contents of PICTURE, placing the output into the format output | |
7660c0ab | 1789 | accumulator, C<$^A> (or C<$ACCUMULATOR> in English). |
19799a22 | 1790 | Eventually, when a C<write> is done, the contents of |
a0d0e21e | 1791 | C<$^A> are written to some filehandle, but you could also read C<$^A> |
7660c0ab | 1792 | yourself and then set C<$^A> back to C<"">. Note that a format typically |
19799a22 | 1793 | does one C<formline> per line of form, but the C<formline> function itself |
748a9306 | 1794 | doesn't care how many newlines are embedded in the PICTURE. This means |
4633a7c4 | 1795 | that the C<~> and C<~~> tokens will treat the entire PICTURE as a single line. |
748a9306 LW |
1796 | You may therefore need to use multiple formlines to implement a single |
1797 | record format, just like the format compiler. | |
1798 | ||
19799a22 | 1799 | Be careful if you put double quotes around the picture, because an C<@> |
748a9306 | 1800 | character may be taken to mean the beginning of an array name. |
19799a22 | 1801 | C<formline> always returns true. See L<perlform> for other examples. |
a0d0e21e LW |
1802 | |
1803 | =item getc FILEHANDLE | |
1804 | ||
1805 | =item getc | |
1806 | ||
1807 | Returns the next character from the input file attached to FILEHANDLE, | |
2b5ab1e7 TC |
1808 | or the undefined value at end of file, or if there was an error. |
1809 | If FILEHANDLE is omitted, reads from STDIN. This is not particularly | |
1810 | efficient. However, it cannot be used by itself to fetch single | |
1811 | characters without waiting for the user to hit enter. For that, try | |
1812 | something more like: | |
4633a7c4 LW |
1813 | |
1814 | if ($BSD_STYLE) { | |
1815 | system "stty cbreak </dev/tty >/dev/tty 2>&1"; | |
1816 | } | |
1817 | else { | |
54310121 | 1818 | system "stty", '-icanon', 'eol', "\001"; |
4633a7c4 LW |
1819 | } |
1820 | ||
1821 | $key = getc(STDIN); | |
1822 | ||
1823 | if ($BSD_STYLE) { | |
1824 | system "stty -cbreak </dev/tty >/dev/tty 2>&1"; | |
1825 | } | |
1826 | else { | |
5f05dabc | 1827 | system "stty", 'icanon', 'eol', '^@'; # ASCII null |
4633a7c4 LW |
1828 | } |
1829 | print "\n"; | |
1830 | ||
54310121 | 1831 | Determination of whether $BSD_STYLE should be set |
1832 | is left as an exercise to the reader. | |
cb1a09d0 | 1833 | |
19799a22 | 1834 | The C<POSIX::getattr> function can do this more portably on |
2b5ab1e7 TC |
1835 | systems purporting POSIX compliance. See also the C<Term::ReadKey> |
1836 | module from your nearest CPAN site; details on CPAN can be found on | |
1837 | L<perlmodlib/CPAN>. | |
a0d0e21e LW |
1838 | |
1839 | =item getlogin | |
1840 | ||
5a964f20 TC |
1841 | Implements the C library function of the same name, which on most |
1842 | systems returns the current login from F</etc/utmp>, if any. If null, | |
19799a22 | 1843 | use C<getpwuid>. |
a0d0e21e | 1844 | |
f86702cc | 1845 | $login = getlogin || getpwuid($<) || "Kilroy"; |
a0d0e21e | 1846 | |
19799a22 GS |
1847 | Do not consider C<getlogin> for authentication: it is not as |
1848 | secure as C<getpwuid>. | |
4633a7c4 | 1849 | |
a0d0e21e LW |
1850 | =item getpeername SOCKET |
1851 | ||
1852 | Returns the packed sockaddr address of other end of the SOCKET connection. | |
1853 | ||
4633a7c4 LW |
1854 | use Socket; |
1855 | $hersockaddr = getpeername(SOCK); | |
19799a22 | 1856 | ($port, $iaddr) = sockaddr_in($hersockaddr); |
4633a7c4 LW |
1857 | $herhostname = gethostbyaddr($iaddr, AF_INET); |
1858 | $herstraddr = inet_ntoa($iaddr); | |
a0d0e21e LW |
1859 | |
1860 | =item getpgrp PID | |
1861 | ||
47e29363 | 1862 | Returns the current process group for the specified PID. Use |
7660c0ab | 1863 | a PID of C<0> to get the current process group for the |
4633a7c4 | 1864 | current process. Will raise an exception if used on a machine that |
f86cebdf | 1865 | doesn't implement getpgrp(2). If PID is omitted, returns process |
19799a22 | 1866 | group of current process. Note that the POSIX version of C<getpgrp> |
7660c0ab | 1867 | does not accept a PID argument, so only C<PID==0> is truly portable. |
a0d0e21e LW |
1868 | |
1869 | =item getppid | |
1870 | ||
1871 | Returns the process id of the parent process. | |
1872 | ||
4d76a344 RGS |
1873 | Note for Linux users: on Linux, the C functions C<getpid()> and |
1874 | C<getppid()> return different values from different threads. In order to | |
1875 | be portable, this behavior is not reflected by the perl-level function | |
1876 | C<getppid()>, that returns a consistent value across threads. If you want | |
e3256f86 RGS |
1877 | to call the underlying C<getppid()>, you may use the CPAN module |
1878 | C<Linux::Pid>. | |
4d76a344 | 1879 | |
a0d0e21e LW |
1880 | =item getpriority WHICH,WHO |
1881 | ||
4633a7c4 LW |
1882 | Returns the current priority for a process, a process group, or a user. |
1883 | (See L<getpriority(2)>.) Will raise a fatal exception if used on a | |
f86cebdf | 1884 | machine that doesn't implement getpriority(2). |
a0d0e21e LW |
1885 | |
1886 | =item getpwnam NAME | |
1887 | ||
1888 | =item getgrnam NAME | |
1889 | ||
1890 | =item gethostbyname NAME | |
1891 | ||
1892 | =item getnetbyname NAME | |
1893 | ||
1894 | =item getprotobyname NAME | |
1895 | ||
1896 | =item getpwuid UID | |
1897 | ||
1898 | =item getgrgid GID | |
1899 | ||
1900 | =item getservbyname NAME,PROTO | |
1901 | ||
1902 | =item gethostbyaddr ADDR,ADDRTYPE | |
1903 | ||
1904 | =item getnetbyaddr ADDR,ADDRTYPE | |
1905 | ||
1906 | =item getprotobynumber NUMBER | |
1907 | ||
1908 | =item getservbyport PORT,PROTO | |
1909 | ||
1910 | =item getpwent | |
1911 | ||
1912 | =item getgrent | |
1913 | ||
1914 | =item gethostent | |
1915 | ||
1916 | =item getnetent | |
1917 | ||
1918 | =item getprotoent | |
1919 | ||
1920 | =item getservent | |
1921 | ||
1922 | =item setpwent | |
1923 | ||
1924 | =item setgrent | |
1925 | ||
1926 | =item sethostent STAYOPEN | |
1927 | ||
1928 | =item setnetent STAYOPEN | |
1929 | ||
1930 | =item setprotoent STAYOPEN | |
1931 | ||
1932 | =item setservent STAYOPEN | |
1933 | ||
1934 | =item endpwent | |
1935 | ||
1936 | =item endgrent | |
1937 | ||
1938 | =item endhostent | |
1939 | ||
1940 | =item endnetent | |
1941 | ||
1942 | =item endprotoent | |
1943 | ||
1944 | =item endservent | |
1945 | ||
1946 | These routines perform the same functions as their counterparts in the | |
5a964f20 | 1947 | system library. In list context, the return values from the |
a0d0e21e LW |
1948 | various get routines are as follows: |
1949 | ||
1950 | ($name,$passwd,$uid,$gid, | |
6ee623d5 | 1951 | $quota,$comment,$gcos,$dir,$shell,$expire) = getpw* |
a0d0e21e LW |
1952 | ($name,$passwd,$gid,$members) = getgr* |
1953 | ($name,$aliases,$addrtype,$length,@addrs) = gethost* | |
1954 | ($name,$aliases,$addrtype,$net) = getnet* | |
1955 | ($name,$aliases,$proto) = getproto* | |
1956 | ($name,$aliases,$port,$proto) = getserv* | |
1957 | ||
1958 | (If the entry doesn't exist you get a null list.) | |
1959 | ||
4602f195 JH |
1960 | The exact meaning of the $gcos field varies but it usually contains |
1961 | the real name of the user (as opposed to the login name) and other | |
1962 | information pertaining to the user. Beware, however, that in many | |
1963 | system users are able to change this information and therefore it | |
106325ad | 1964 | cannot be trusted and therefore the $gcos is tainted (see |
2959b6e3 JH |
1965 | L<perlsec>). The $passwd and $shell, user's encrypted password and |
1966 | login shell, are also tainted, because of the same reason. | |
4602f195 | 1967 | |
5a964f20 | 1968 | In scalar context, you get the name, unless the function was a |
a0d0e21e LW |
1969 | lookup by name, in which case you get the other thing, whatever it is. |
1970 | (If the entry doesn't exist you get the undefined value.) For example: | |
1971 | ||
5a964f20 TC |
1972 | $uid = getpwnam($name); |
1973 | $name = getpwuid($num); | |
1974 | $name = getpwent(); | |
1975 | $gid = getgrnam($name); | |
08a33e13 | 1976 | $name = getgrgid($num); |
5a964f20 TC |
1977 | $name = getgrent(); |
1978 | #etc. | |
a0d0e21e | 1979 | |
4602f195 JH |
1980 | In I<getpw*()> the fields $quota, $comment, and $expire are special |
1981 | cases in the sense that in many systems they are unsupported. If the | |
1982 | $quota is unsupported, it is an empty scalar. If it is supported, it | |
1983 | usually encodes the disk quota. If the $comment field is unsupported, | |
1984 | it is an empty scalar. If it is supported it usually encodes some | |
1985 | administrative comment about the user. In some systems the $quota | |
1986 | field may be $change or $age, fields that have to do with password | |
1987 | aging. In some systems the $comment field may be $class. The $expire | |
1988 | field, if present, encodes the expiration period of the account or the | |
1989 | password. For the availability and the exact meaning of these fields | |
1990 | in your system, please consult your getpwnam(3) documentation and your | |
1991 | F<pwd.h> file. You can also find out from within Perl what your | |
1992 | $quota and $comment fields mean and whether you have the $expire field | |
1993 | by using the C<Config> module and the values C<d_pwquota>, C<d_pwage>, | |
1994 | C<d_pwchange>, C<d_pwcomment>, and C<d_pwexpire>. Shadow password | |
1995 | files are only supported if your vendor has implemented them in the | |
1996 | intuitive fashion that calling the regular C library routines gets the | |
5d3a0a3b GS |
1997 | shadow versions if you're running under privilege or if there exists |
1998 | the shadow(3) functions as found in System V ( this includes Solaris | |
1999 | and Linux.) Those systems which implement a proprietary shadow password | |
2000 | facility are unlikely to be supported. | |
6ee623d5 | 2001 | |
19799a22 | 2002 | The $members value returned by I<getgr*()> is a space separated list of |
a0d0e21e LW |
2003 | the login names of the members of the group. |
2004 | ||
2005 | For the I<gethost*()> functions, if the C<h_errno> variable is supported in | |
2006 | C, it will be returned to you via C<$?> if the function call fails. The | |
7660c0ab | 2007 | C<@addrs> value returned by a successful call is a list of the raw |
a0d0e21e LW |
2008 | addresses returned by the corresponding system library call. In the |
2009 | Internet domain, each address is four bytes long and you can unpack it | |
2010 | by saying something like: | |
2011 | ||
2012 | ($a,$b,$c,$d) = unpack('C4',$addr[0]); | |
2013 | ||
2b5ab1e7 TC |
2014 | The Socket library makes this slightly easier: |
2015 | ||
2016 | use Socket; | |
2017 | $iaddr = inet_aton("127.1"); # or whatever address | |
2018 | $name = gethostbyaddr($iaddr, AF_INET); | |
2019 | ||
2020 | # or going the other way | |
19799a22 | 2021 | $straddr = inet_ntoa($iaddr); |
2b5ab1e7 | 2022 | |
19799a22 GS |
2023 | If you get tired of remembering which element of the return list |
2024 | contains which return value, by-name interfaces are provided | |
2025 | in standard modules: C<File::stat>, C<Net::hostent>, C<Net::netent>, | |
2026 | C<Net::protoent>, C<Net::servent>, C<Time::gmtime>, C<Time::localtime>, | |
2027 | and C<User::grent>. These override the normal built-ins, supplying | |
2028 | versions that return objects with the appropriate names | |
2029 | for each field. For example: | |
5a964f20 TC |
2030 | |
2031 | use File::stat; | |
2032 | use User::pwent; | |
2033 | $is_his = (stat($filename)->uid == pwent($whoever)->uid); | |
2034 | ||
b76cc8ba NIS |
2035 | Even though it looks like they're the same method calls (uid), |
2036 | they aren't, because a C<File::stat> object is different from | |
19799a22 | 2037 | a C<User::pwent> object. |
5a964f20 | 2038 | |
a0d0e21e LW |
2039 | =item getsockname SOCKET |
2040 | ||
19799a22 GS |
2041 | Returns the packed sockaddr address of this end of the SOCKET connection, |
2042 | in case you don't know the address because you have several different | |
2043 | IPs that the connection might have come in on. | |
a0d0e21e | 2044 | |
4633a7c4 LW |
2045 | use Socket; |
2046 | $mysockaddr = getsockname(SOCK); | |
19799a22 | 2047 | ($port, $myaddr) = sockaddr_in($mysockaddr); |
b76cc8ba | 2048 | printf "Connect to %s [%s]\n", |
19799a22 GS |
2049 | scalar gethostbyaddr($myaddr, AF_INET), |
2050 | inet_ntoa($myaddr); | |
a0d0e21e LW |
2051 | |
2052 | =item getsockopt SOCKET,LEVEL,OPTNAME | |
2053 | ||
5a964f20 | 2054 | Returns the socket option requested, or undef if there is an error. |
a0d0e21e LW |
2055 | |
2056 | =item glob EXPR | |
2057 | ||
0a753a76 | 2058 | =item glob |
2059 | ||
d9a9d457 JL |
2060 | In list context, returns a (possibly empty) list of filename expansions on |
2061 | the value of EXPR such as the standard Unix shell F</bin/csh> would do. In | |
2062 | scalar context, glob iterates through such filename expansions, returning | |
2063 | undef when the list is exhausted. This is the internal function | |
2064 | implementing the C<< <*.c> >> operator, but you can use it directly. If | |
2065 | EXPR is omitted, C<$_> is used. The C<< <*.c> >> operator is discussed in | |
2066 | more detail in L<perlop/"I/O Operators">. | |
a0d0e21e | 2067 | |
3a4b19e4 GS |
2068 | Beginning with v5.6.0, this operator is implemented using the standard |
2069 | C<File::Glob> extension. See L<File::Glob> for details. | |
2070 | ||
a0d0e21e LW |
2071 | =item gmtime EXPR |
2072 | ||
d1be9408 | 2073 | Converts a time as returned by the time function to an 8-element list |
54310121 | 2074 | with the time localized for the standard Greenwich time zone. |
4633a7c4 | 2075 | Typically used as follows: |
a0d0e21e | 2076 | |
b76cc8ba | 2077 | # 0 1 2 3 4 5 6 7 |
48a26b3a | 2078 | ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday) = |
a0d0e21e LW |
2079 | gmtime(time); |
2080 | ||
48a26b3a GS |
2081 | All list elements are numeric, and come straight out of the C `struct |
2082 | tm'. $sec, $min, and $hour are the seconds, minutes, and hours of the | |
2083 | specified time. $mday is the day of the month, and $mon is the month | |
2084 | itself, in the range C<0..11> with 0 indicating January and 11 | |
2085 | indicating December. $year is the number of years since 1900. That | |
2086 | is, $year is C<123> in year 2023. $wday is the day of the week, with | |
2087 | 0 indicating Sunday and 3 indicating Wednesday. $yday is the day of | |
b76cc8ba | 2088 | the year, in the range C<0..364> (or C<0..365> in leap years.) |
48a26b3a GS |
2089 | |
2090 | Note that the $year element is I<not> simply the last two digits of | |
2091 | the year. If you assume it is, then you create non-Y2K-compliant | |
2092 | programs--and you wouldn't want to do that, would you? | |
2f9daede | 2093 | |
abd75f24 GS |
2094 | The proper way to get a complete 4-digit year is simply: |
2095 | ||
2096 | $year += 1900; | |
2097 | ||
2098 | And to get the last two digits of the year (e.g., '01' in 2001) do: | |
2099 | ||
2100 | $year = sprintf("%02d", $year % 100); | |
2101 | ||
48a26b3a | 2102 | If EXPR is omitted, C<gmtime()> uses the current time (C<gmtime(time)>). |
a0d0e21e | 2103 | |
48a26b3a | 2104 | In scalar context, C<gmtime()> returns the ctime(3) value: |
0a753a76 | 2105 | |
2106 | $now_string = gmtime; # e.g., "Thu Oct 13 04:54:34 1994" | |
2107 | ||
19799a22 | 2108 | Also see the C<timegm> function provided by the C<Time::Local> module, |
f86cebdf | 2109 | and the strftime(3) function available via the POSIX module. |
7660c0ab | 2110 | |
2b5ab1e7 TC |
2111 | This scalar value is B<not> locale dependent (see L<perllocale>), but |
2112 | is instead a Perl builtin. Also see the C<Time::Local> module, and the | |
2113 | strftime(3) and mktime(3) functions available via the POSIX module. To | |
7660c0ab A |
2114 | get somewhat similar but locale dependent date strings, set up your |
2115 | locale environment variables appropriately (please see L<perllocale>) | |
2116 | and try for example: | |
2117 | ||
2118 | use POSIX qw(strftime); | |
2b5ab1e7 | 2119 | $now_string = strftime "%a %b %e %H:%M:%S %Y", gmtime; |
7660c0ab | 2120 | |
2b5ab1e7 TC |
2121 | Note that the C<%a> and C<%b> escapes, which represent the short forms |
2122 | of the day of the week and the month of the year, may not necessarily | |
2123 | be three characters wide in all locales. | |
0a753a76 | 2124 | |
a0d0e21e LW |
2125 | =item goto LABEL |
2126 | ||
748a9306 LW |
2127 | =item goto EXPR |
2128 | ||
a0d0e21e LW |
2129 | =item goto &NAME |
2130 | ||
7660c0ab | 2131 | The C<goto-LABEL> form finds the statement labeled with LABEL and resumes |
a0d0e21e | 2132 | execution there. It may not be used to go into any construct that |
7660c0ab | 2133 | requires initialization, such as a subroutine or a C<foreach> loop. It |
0a753a76 | 2134 | also can't be used to go into a construct that is optimized away, |
19799a22 | 2135 | or to get out of a block or subroutine given to C<sort>. |
0a753a76 | 2136 | It can be used to go almost anywhere else within the dynamic scope, |
a0d0e21e | 2137 | including out of subroutines, but it's usually better to use some other |
19799a22 | 2138 | construct such as C<last> or C<die>. The author of Perl has never felt the |
7660c0ab | 2139 | need to use this form of C<goto> (in Perl, that is--C is another matter). |
1b6921cb BT |
2140 | (The difference being that C does not offer named loops combined with |
2141 | loop control. Perl does, and this replaces most structured uses of C<goto> | |
2142 | in other languages.) | |
a0d0e21e | 2143 | |
7660c0ab A |
2144 | The C<goto-EXPR> form expects a label name, whose scope will be resolved |
2145 | dynamically. This allows for computed C<goto>s per FORTRAN, but isn't | |
748a9306 LW |
2146 | necessarily recommended if you're optimizing for maintainability: |
2147 | ||
2148 | goto ("FOO", "BAR", "GLARCH")[$i]; | |
2149 | ||
1b6921cb BT |
2150 | The C<goto-&NAME> form is quite different from the other forms of |
2151 | C<goto>. In fact, it isn't a goto in the normal sense at all, and | |
2152 | doesn't have the stigma associated with other gotos. Instead, it | |
2153 | exits the current subroutine (losing any changes set by local()) and | |
2154 | immediately calls in its place the named subroutine using the current | |
2155 | value of @_. This is used by C<AUTOLOAD> subroutines that wish to | |
2156 | load another subroutine and then pretend that the other subroutine had | |
2157 | been called in the first place (except that any modifications to C<@_> | |
6cb9131c GS |
2158 | in the current subroutine are propagated to the other subroutine.) |
2159 | After the C<goto>, not even C<caller> will be able to tell that this | |
2160 | routine was called first. | |
2161 | ||
2162 | NAME needn't be the name of a subroutine; it can be a scalar variable | |
2163 | containing a code reference, or a block which evaluates to a code | |
2164 | reference. | |
a0d0e21e LW |
2165 | |
2166 | =item grep BLOCK LIST | |
2167 | ||
2168 | =item grep EXPR,LIST | |
2169 | ||
2b5ab1e7 TC |
2170 | This is similar in spirit to, but not the same as, grep(1) and its |
2171 | relatives. In particular, it is not limited to using regular expressions. | |
2f9daede | 2172 | |
a0d0e21e | 2173 | Evaluates the BLOCK or EXPR for each element of LIST (locally setting |
7660c0ab | 2174 | C<$_> to each element) and returns the list value consisting of those |
19799a22 GS |
2175 | elements for which the expression evaluated to true. In scalar |
2176 | context, returns the number of times the expression was true. | |
a0d0e21e LW |
2177 | |
2178 | @foo = grep(!/^#/, @bar); # weed out comments | |
2179 | ||
2180 | or equivalently, | |
2181 | ||
2182 | @foo = grep {!/^#/} @bar; # weed out comments | |
2183 | ||
be3174d2 GS |
2184 | Note that C<$_> is an alias to the list value, so it can be used to |
2185 | modify the elements of the LIST. While this is useful and supported, | |
2186 | it can cause bizarre results if the elements of LIST are not variables. | |
2b5ab1e7 TC |
2187 | Similarly, grep returns aliases into the original list, much as a for |
2188 | loop's index variable aliases the list elements. That is, modifying an | |
19799a22 GS |
2189 | element of a list returned by grep (for example, in a C<foreach>, C<map> |
2190 | or another C<grep>) actually modifies the element in the original list. | |
2b5ab1e7 | 2191 | This is usually something to be avoided when writing clear code. |
a0d0e21e | 2192 | |
19799a22 | 2193 | See also L</map> for a list composed of the results of the BLOCK or EXPR. |
38325410 | 2194 | |
a0d0e21e LW |
2195 | =item hex EXPR |
2196 | ||
54310121 | 2197 | =item hex |
bbce6d69 | 2198 | |
2b5ab1e7 TC |
2199 | Interprets EXPR as a hex string and returns the corresponding value. |
2200 | (To convert strings that might start with either 0, 0x, or 0b, see | |
2201 | L</oct>.) If EXPR is omitted, uses C<$_>. | |
2f9daede TP |
2202 | |
2203 | print hex '0xAf'; # prints '175' | |
2204 | print hex 'aF'; # same | |
a0d0e21e | 2205 | |
19799a22 | 2206 | Hex strings may only represent integers. Strings that would cause |
53305cf1 NC |
2207 | integer overflow trigger a warning. Leading whitespace is not stripped, |
2208 | unlike oct(). | |
19799a22 | 2209 | |
a0d0e21e LW |
2210 | =item import |
2211 | ||
19799a22 | 2212 | There is no builtin C<import> function. It is just an ordinary |
4633a7c4 | 2213 | method (subroutine) defined (or inherited) by modules that wish to export |
19799a22 | 2214 | names to another module. The C<use> function calls the C<import> method |
cea6626f | 2215 | for the package used. See also L</use>, L<perlmod>, and L<Exporter>. |
a0d0e21e LW |
2216 | |
2217 | =item index STR,SUBSTR,POSITION | |
2218 | ||
2219 | =item index STR,SUBSTR | |
2220 | ||
2b5ab1e7 TC |
2221 | The index function searches for one string within another, but without |
2222 | the wildcard-like behavior of a full regular-expression pattern match. | |
2223 | It returns the position of the first occurrence of SUBSTR in STR at | |
2224 | or after POSITION. If POSITION is omitted, starts searching from the | |
2225 | beginning of the string. The return value is based at C<0> (or whatever | |
2226 | you've set the C<$[> variable to--but don't do that). If the substring | |
2227 | is not found, returns one less than the base, ordinarily C<-1>. | |
a0d0e21e LW |
2228 | |
2229 | =item int EXPR | |
2230 | ||
54310121 | 2231 | =item int |
bbce6d69 | 2232 | |
7660c0ab | 2233 | Returns the integer portion of EXPR. If EXPR is omitted, uses C<$_>. |
2b5ab1e7 TC |
2234 | You should not use this function for rounding: one because it truncates |
2235 | towards C<0>, and two because machine representations of floating point | |
2236 | numbers can sometimes produce counterintuitive results. For example, | |
2237 | C<int(-6.725/0.025)> produces -268 rather than the correct -269; that's | |
2238 | because it's really more like -268.99999999999994315658 instead. Usually, | |
19799a22 | 2239 | the C<sprintf>, C<printf>, or the C<POSIX::floor> and C<POSIX::ceil> |
2b5ab1e7 | 2240 | functions will serve you better than will int(). |
a0d0e21e LW |
2241 | |
2242 | =item ioctl FILEHANDLE,FUNCTION,SCALAR | |
2243 | ||
2b5ab1e7 | 2244 | Implements the ioctl(2) function. You'll probably first have to say |
a0d0e21e | 2245 | |
4633a7c4 | 2246 | require "ioctl.ph"; # probably in /usr/local/lib/perl/ioctl.ph |
a0d0e21e | 2247 | |
2b5ab1e7 | 2248 | to get the correct function definitions. If F<ioctl.ph> doesn't |
a0d0e21e | 2249 | exist or doesn't have the correct definitions you'll have to roll your |
61eff3bc | 2250 | own, based on your C header files such as F<< <sys/ioctl.h> >>. |
5a964f20 | 2251 | (There is a Perl script called B<h2ph> that comes with the Perl kit that |
54310121 | 2252 | may help you in this, but it's nontrivial.) SCALAR will be read and/or |
4633a7c4 | 2253 | written depending on the FUNCTION--a pointer to the string value of SCALAR |
19799a22 | 2254 | will be passed as the third argument of the actual C<ioctl> call. (If SCALAR |
4633a7c4 LW |
2255 | has no string value but does have a numeric value, that value will be |
2256 | passed rather than a pointer to the string value. To guarantee this to be | |
19799a22 GS |
2257 | true, add a C<0> to the scalar before using it.) The C<pack> and C<unpack> |
2258 | functions may be needed to manipulate the values of structures used by | |
b76cc8ba | 2259 | C<ioctl>. |
a0d0e21e | 2260 | |
19799a22 | 2261 | The return value of C<ioctl> (and C<fcntl>) is as follows: |
a0d0e21e LW |
2262 | |
2263 | if OS returns: then Perl returns: | |
2264 | -1 undefined value | |
2265 | 0 string "0 but true" | |
2266 | anything else that number | |
2267 | ||
19799a22 | 2268 | Thus Perl returns true on success and false on failure, yet you can |
a0d0e21e LW |
2269 | still easily determine the actual value returned by the operating |
2270 | system: | |
2271 | ||
2b5ab1e7 | 2272 | $retval = ioctl(...) || -1; |
a0d0e21e LW |
2273 | printf "System returned %d\n", $retval; |
2274 | ||
c2611fb3 | 2275 | The special string "C<0> but true" is exempt from B<-w> complaints |
5a964f20 TC |
2276 | about improper numeric conversions. |
2277 | ||
19799a22 GS |
2278 | Here's an example of setting a filehandle named C<REMOTE> to be |
2279 | non-blocking at the system level. You'll have to negotiate C<$|> | |
2280 | on your own, though. | |
2281 | ||
2282 | use Fcntl qw(F_GETFL F_SETFL O_NONBLOCK); | |
2283 | ||
2284 | $flags = fcntl(REMOTE, F_GETFL, 0) | |
2285 | or die "Can't get flags for the socket: $!\n"; | |
2286 | ||
2287 | $flags = fcntl(REMOTE, F_SETFL, $flags | O_NONBLOCK) | |
2288 | or die "Can't set flags for the socket: $!\n"; | |
2289 | ||
a0d0e21e LW |
2290 | =item join EXPR,LIST |
2291 | ||
2b5ab1e7 TC |
2292 | Joins the separate strings of LIST into a single string with fields |
2293 | separated by the value of EXPR, and returns that new string. Example: | |
a0d0e21e | 2294 | |
2b5ab1e7 | 2295 | $rec = join(':', $login,$passwd,$uid,$gid,$gcos,$home,$shell); |
a0d0e21e | 2296 | |
eb6e2d6f GS |
2297 | Beware that unlike C<split>, C<join> doesn't take a pattern as its |
2298 | first argument. Compare L</split>. | |
a0d0e21e | 2299 | |
aa689395 | 2300 | =item keys HASH |
2301 | ||
19799a22 | 2302 | Returns a list consisting of all the keys of the named hash. (In |
1d2dff63 | 2303 | scalar context, returns the number of keys.) The keys are returned in |
ab192400 GS |
2304 | an apparently random order. The actual random order is subject to |
2305 | change in future versions of perl, but it is guaranteed to be the same | |
19799a22 | 2306 | order as either the C<values> or C<each> function produces (given |
ab192400 GS |
2307 | that the hash has not been modified). As a side effect, it resets |
2308 | HASH's iterator. | |
a0d0e21e | 2309 | |
aa689395 | 2310 | Here is yet another way to print your environment: |
a0d0e21e LW |
2311 | |
2312 | @keys = keys %ENV; | |
2313 | @values = values %ENV; | |
b76cc8ba | 2314 | while (@keys) { |
a0d0e21e LW |
2315 | print pop(@keys), '=', pop(@values), "\n"; |
2316 | } | |
2317 | ||
2318 | or how about sorted by key: | |
2319 | ||
2320 | foreach $key (sort(keys %ENV)) { | |
2321 | print $key, '=', $ENV{$key}, "\n"; | |
2322 | } | |
2323 | ||
8ea1e5d4 GS |
2324 | The returned values are copies of the original keys in the hash, so |
2325 | modifying them will not affect the original hash. Compare L</values>. | |
2326 | ||
19799a22 | 2327 | To sort a hash by value, you'll need to use a C<sort> function. |
aa689395 | 2328 | Here's a descending numeric sort of a hash by its values: |
4633a7c4 | 2329 | |
5a964f20 | 2330 | foreach $key (sort { $hash{$b} <=> $hash{$a} } keys %hash) { |
4633a7c4 LW |
2331 | printf "%4d %s\n", $hash{$key}, $key; |
2332 | } | |
2333 | ||
19799a22 | 2334 | As an lvalue C<keys> allows you to increase the number of hash buckets |
aa689395 | 2335 | allocated for the given hash. This can gain you a measure of efficiency if |
2336 | you know the hash is going to get big. (This is similar to pre-extending | |
2337 | an array by assigning a larger number to $#array.) If you say | |
55497cff | 2338 | |
2339 | keys %hash = 200; | |
2340 | ||
ab192400 GS |
2341 | then C<%hash> will have at least 200 buckets allocated for it--256 of them, |
2342 | in fact, since it rounds up to the next power of two. These | |
55497cff | 2343 | buckets will be retained even if you do C<%hash = ()>, use C<undef |
2344 | %hash> if you want to free the storage while C<%hash> is still in scope. | |
2345 | You can't shrink the number of buckets allocated for the hash using | |
19799a22 | 2346 | C<keys> in this way (but you needn't worry about doing this by accident, |
55497cff | 2347 | as trying has no effect). |
2348 | ||
19799a22 | 2349 | See also C<each>, C<values> and C<sort>. |
ab192400 | 2350 | |
b350dd2f | 2351 | =item kill SIGNAL, LIST |
a0d0e21e | 2352 | |
b350dd2f | 2353 | Sends a signal to a list of processes. Returns the number of |
517db077 GS |
2354 | processes successfully signaled (which is not necessarily the |
2355 | same as the number actually killed). | |
a0d0e21e LW |
2356 | |
2357 | $cnt = kill 1, $child1, $child2; | |
2358 | kill 9, @goners; | |
2359 | ||
b350dd2f GS |
2360 | If SIGNAL is zero, no signal is sent to the process. This is a |
2361 | useful way to check that the process is alive and hasn't changed | |
2362 | its UID. See L<perlport> for notes on the portability of this | |
2363 | construct. | |
2364 | ||
2365 | Unlike in the shell, if SIGNAL is negative, it kills | |
4633a7c4 LW |
2366 | process groups instead of processes. (On System V, a negative I<PROCESS> |
2367 | number will also kill process groups, but that's not portable.) That | |
2368 | means you usually want to use positive not negative signals. You may also | |
da0045b7 | 2369 | use a signal name in quotes. See L<perlipc/"Signals"> for details. |
a0d0e21e LW |
2370 | |
2371 | =item last LABEL | |
2372 | ||
2373 | =item last | |
2374 | ||
2375 | The C<last> command is like the C<break> statement in C (as used in | |
2376 | loops); it immediately exits the loop in question. If the LABEL is | |
2377 | omitted, the command refers to the innermost enclosing loop. The | |
2378 | C<continue> block, if any, is not executed: | |
2379 | ||
4633a7c4 LW |
2380 | LINE: while (<STDIN>) { |
2381 | last LINE if /^$/; # exit when done with header | |
5a964f20 | 2382 | #... |
a0d0e21e LW |
2383 | } |
2384 | ||
4968c1e4 | 2385 | C<last> cannot be used to exit a block which returns a value such as |
2b5ab1e7 TC |
2386 | C<eval {}>, C<sub {}> or C<do {}>, and should not be used to exit |
2387 | a grep() or map() operation. | |
4968c1e4 | 2388 | |
6c1372ed GS |
2389 | Note that a block by itself is semantically identical to a loop |
2390 | that executes once. Thus C<last> can be used to effect an early | |
2391 | exit out of such a block. | |
2392 | ||
98293880 JH |
2393 | See also L</continue> for an illustration of how C<last>, C<next>, and |
2394 | C<redo> work. | |
1d2dff63 | 2395 | |
a0d0e21e LW |
2396 | =item lc EXPR |
2397 | ||
54310121 | 2398 | =item lc |
bbce6d69 | 2399 | |
d1be9408 | 2400 | Returns a lowercased version of EXPR. This is the internal function |
ad0029c4 JH |
2401 | implementing the C<\L> escape in double-quoted strings. Respects |
2402 | current LC_CTYPE locale if C<use locale> in force. See L<perllocale> | |
983ffd37 | 2403 | and L<perlunicode> for more details about locale and Unicode support. |
a0d0e21e | 2404 | |
7660c0ab | 2405 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 2406 | |
a0d0e21e LW |
2407 | =item lcfirst EXPR |
2408 | ||
54310121 | 2409 | =item lcfirst |
bbce6d69 | 2410 | |
ad0029c4 JH |
2411 | Returns the value of EXPR with the first character lowercased. This |
2412 | is the internal function implementing the C<\l> escape in | |
2413 | double-quoted strings. Respects current LC_CTYPE locale if C<use | |
983ffd37 JH |
2414 | locale> in force. See L<perllocale> and L<perlunicode> for more |
2415 | details about locale and Unicode support. | |
a0d0e21e | 2416 | |
7660c0ab | 2417 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 2418 | |
a0d0e21e LW |
2419 | =item length EXPR |
2420 | ||
54310121 | 2421 | =item length |
bbce6d69 | 2422 | |
a0ed51b3 | 2423 | Returns the length in characters of the value of EXPR. If EXPR is |
b76cc8ba | 2424 | omitted, returns length of C<$_>. Note that this cannot be used on |
2b5ab1e7 TC |
2425 | an entire array or hash to find out how many elements these have. |
2426 | For that, use C<scalar @array> and C<scalar keys %hash> respectively. | |
a0d0e21e LW |
2427 | |
2428 | =item link OLDFILE,NEWFILE | |
2429 | ||
19799a22 | 2430 | Creates a new filename linked to the old filename. Returns true for |
b76cc8ba | 2431 | success, false otherwise. |
a0d0e21e LW |
2432 | |
2433 | =item listen SOCKET,QUEUESIZE | |
2434 | ||
19799a22 | 2435 | Does the same thing that the listen system call does. Returns true if |
b76cc8ba | 2436 | it succeeded, false otherwise. See the example in |
cea6626f | 2437 | L<perlipc/"Sockets: Client/Server Communication">. |
a0d0e21e LW |
2438 | |
2439 | =item local EXPR | |
2440 | ||
19799a22 | 2441 | You really probably want to be using C<my> instead, because C<local> isn't |
b76cc8ba | 2442 | what most people think of as "local". See |
13a2d996 | 2443 | L<perlsub/"Private Variables via my()"> for details. |
2b5ab1e7 | 2444 | |
5a964f20 TC |
2445 | A local modifies the listed variables to be local to the enclosing |
2446 | block, file, or eval. If more than one value is listed, the list must | |
2447 | be placed in parentheses. See L<perlsub/"Temporary Values via local()"> | |
2448 | for details, including issues with tied arrays and hashes. | |
a0d0e21e | 2449 | |
a0d0e21e LW |
2450 | =item localtime EXPR |
2451 | ||
19799a22 | 2452 | Converts a time as returned by the time function to a 9-element list |
5f05dabc | 2453 | with the time analyzed for the local time zone. Typically used as |
a0d0e21e LW |
2454 | follows: |
2455 | ||
54310121 | 2456 | # 0 1 2 3 4 5 6 7 8 |
a0d0e21e LW |
2457 | ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = |
2458 | localtime(time); | |
2459 | ||
48a26b3a GS |
2460 | All list elements are numeric, and come straight out of the C `struct |
2461 | tm'. $sec, $min, and $hour are the seconds, minutes, and hours of the | |
2462 | specified time. $mday is the day of the month, and $mon is the month | |
2463 | itself, in the range C<0..11> with 0 indicating January and 11 | |
2464 | indicating December. $year is the number of years since 1900. That | |
2465 | is, $year is C<123> in year 2023. $wday is the day of the week, with | |
2466 | 0 indicating Sunday and 3 indicating Wednesday. $yday is the day of | |
874b1813 | 2467 | the year, in the range C<0..364> (or C<0..365> in leap years.) $isdst |
48a26b3a GS |
2468 | is true if the specified time occurs during daylight savings time, |
2469 | false otherwise. | |
2470 | ||
2471 | Note that the $year element is I<not> simply the last two digits of | |
2472 | the year. If you assume it is, then you create non-Y2K-compliant | |
2473 | programs--and you wouldn't want to do that, would you? | |
54310121 | 2474 | |
abd75f24 GS |
2475 | The proper way to get a complete 4-digit year is simply: |
2476 | ||
2477 | $year += 1900; | |
2478 | ||
2479 | And to get the last two digits of the year (e.g., '01' in 2001) do: | |
2480 | ||
2481 | $year = sprintf("%02d", $year % 100); | |
2482 | ||
48a26b3a | 2483 | If EXPR is omitted, C<localtime()> uses the current time (C<localtime(time)>). |
a0d0e21e | 2484 | |
48a26b3a | 2485 | In scalar context, C<localtime()> returns the ctime(3) value: |
a0d0e21e | 2486 | |
5f05dabc | 2487 | $now_string = localtime; # e.g., "Thu Oct 13 04:54:34 1994" |
a0d0e21e | 2488 | |
a3cb178b | 2489 | This scalar value is B<not> locale dependent, see L<perllocale>, but |
68f8bed4 JH |
2490 | instead a Perl builtin. Also see the C<Time::Local> module |
2491 | (to convert the second, minutes, hours, ... back to seconds since the | |
2492 | stroke of midnight the 1st of January 1970, the value returned by | |
ca6e1c26 | 2493 | time()), and the strftime(3) and mktime(3) functions available via the |
68f8bed4 JH |
2494 | POSIX module. To get somewhat similar but locale dependent date |
2495 | strings, set up your locale environment variables appropriately | |
2496 | (please see L<perllocale>) and try for example: | |
a3cb178b | 2497 | |
5a964f20 | 2498 | use POSIX qw(strftime); |
2b5ab1e7 | 2499 | $now_string = strftime "%a %b %e %H:%M:%S %Y", localtime; |
a3cb178b GS |
2500 | |
2501 | Note that the C<%a> and C<%b>, the short forms of the day of the week | |
2502 | and the month of the year, may not necessarily be three characters wide. | |
a0d0e21e | 2503 | |
07698885 | 2504 | =item lock THING |
19799a22 | 2505 | |
01e6739c | 2506 | This function places an advisory lock on a shared variable, or referenced |
03730085 | 2507 | object contained in I<THING> until the lock goes out of scope. |
a6d5524e | 2508 | |
f3a23afb | 2509 | lock() is a "weak keyword" : this means that if you've defined a function |
67408cae | 2510 | by this name (before any calls to it), that function will be called |
03730085 AB |
2511 | instead. (However, if you've said C<use threads>, lock() is always a |
2512 | keyword.) See L<threads>. | |
19799a22 | 2513 | |
a0d0e21e LW |
2514 | =item log EXPR |
2515 | ||
54310121 | 2516 | =item log |
bbce6d69 | 2517 | |
2b5ab1e7 TC |
2518 | Returns the natural logarithm (base I<e>) of EXPR. If EXPR is omitted, |
2519 | returns log of C<$_>. To get the log of another base, use basic algebra: | |
19799a22 | 2520 | The base-N log of a number is equal to the natural log of that number |
2b5ab1e7 TC |
2521 | divided by the natural log of N. For example: |
2522 | ||
2523 | sub log10 { | |
2524 | my $n = shift; | |
2525 | return log($n)/log(10); | |
b76cc8ba | 2526 | } |
2b5ab1e7 TC |
2527 | |
2528 | See also L</exp> for the inverse operation. | |
a0d0e21e | 2529 | |
a0d0e21e LW |
2530 | =item lstat EXPR |
2531 | ||
54310121 | 2532 | =item lstat |
bbce6d69 | 2533 | |
19799a22 | 2534 | Does the same thing as the C<stat> function (including setting the |
5a964f20 TC |
2535 | special C<_> filehandle) but stats a symbolic link instead of the file |
2536 | the symbolic link points to. If symbolic links are unimplemented on | |
19799a22 | 2537 | your system, a normal C<stat> is done. |
a0d0e21e | 2538 | |
7660c0ab | 2539 | If EXPR is omitted, stats C<$_>. |
bbce6d69 | 2540 | |
a0d0e21e LW |
2541 | =item m// |
2542 | ||
2543 | The match operator. See L<perlop>. | |
2544 | ||
2545 | =item map BLOCK LIST | |
2546 | ||
2547 | =item map EXPR,LIST | |
2548 | ||
19799a22 GS |
2549 | Evaluates the BLOCK or EXPR for each element of LIST (locally setting |
2550 | C<$_> to each element) and returns the list value composed of the | |
2551 | results of each such evaluation. In scalar context, returns the | |
2552 | total number of elements so generated. Evaluates BLOCK or EXPR in | |
2553 | list context, so each element of LIST may produce zero, one, or | |
2554 | more elements in the returned value. | |
dd99ebda | 2555 | |
a0d0e21e LW |
2556 | @chars = map(chr, @nums); |
2557 | ||
2558 | translates a list of numbers to the corresponding characters. And | |
2559 | ||
4633a7c4 | 2560 | %hash = map { getkey($_) => $_ } @array; |
a0d0e21e LW |
2561 | |
2562 | is just a funny way to write | |
2563 | ||
2564 | %hash = (); | |
2565 | foreach $_ (@array) { | |
4633a7c4 | 2566 | $hash{getkey($_)} = $_; |
a0d0e21e LW |
2567 | } |
2568 | ||
be3174d2 GS |
2569 | Note that C<$_> is an alias to the list value, so it can be used to |
2570 | modify the elements of the LIST. While this is useful and supported, | |
2571 | it can cause bizarre results if the elements of LIST are not variables. | |
2b5ab1e7 TC |
2572 | Using a regular C<foreach> loop for this purpose would be clearer in |
2573 | most cases. See also L</grep> for an array composed of those items of | |
2574 | the original list for which the BLOCK or EXPR evaluates to true. | |
fb73857a | 2575 | |
205fdb4d NC |
2576 | C<{> starts both hash references and blocks, so C<map { ...> could be either |
2577 | the start of map BLOCK LIST or map EXPR, LIST. Because perl doesn't look | |
2578 | ahead for the closing C<}> it has to take a guess at which its dealing with | |
2579 | based what it finds just after the C<{>. Usually it gets it right, but if it | |
2580 | doesn't it won't realize something is wrong until it gets to the C<}> and | |
2581 | encounters the missing (or unexpected) comma. The syntax error will be | |
2582 | reported close to the C<}> but you'll need to change something near the C<{> | |
2583 | such as using a unary C<+> to give perl some help: | |
2584 | ||
2585 | %hash = map { "\L$_", 1 } @array # perl guesses EXPR. wrong | |
2586 | %hash = map { +"\L$_", 1 } @array # perl guesses BLOCK. right | |
2587 | %hash = map { ("\L$_", 1) } @array # this also works | |
2588 | %hash = map { lc($_), 1 } @array # as does this. | |
2589 | %hash = map +( lc($_), 1 ), @array # this is EXPR and works! | |
cea6626f | 2590 | |
205fdb4d NC |
2591 | %hash = map ( lc($_), 1 ), @array # evaluates to (1, @array) |
2592 | ||
2593 | or to force an anon hash constructor use C<+{> | |
2594 | ||
2595 | @hashes = map +{ lc($_), 1 }, @array # EXPR, so needs , at end | |
2596 | ||
2597 | and you get list of anonymous hashes each with only 1 entry. | |
2598 | ||
19799a22 | 2599 | =item mkdir FILENAME,MASK |
a0d0e21e | 2600 | |
5a211162 GS |
2601 | =item mkdir FILENAME |
2602 | ||
0591cd52 | 2603 | Creates the directory specified by FILENAME, with permissions |
19799a22 GS |
2604 | specified by MASK (as modified by C<umask>). If it succeeds it |
2605 | returns true, otherwise it returns false and sets C<$!> (errno). | |
5a211162 | 2606 | If omitted, MASK defaults to 0777. |
0591cd52 | 2607 | |
19799a22 | 2608 | In general, it is better to create directories with permissive MASK, |
0591cd52 | 2609 | and let the user modify that with their C<umask>, than it is to supply |
19799a22 | 2610 | a restrictive MASK and give the user no way to be more permissive. |
0591cd52 NT |
2611 | The exceptions to this rule are when the file or directory should be |
2612 | kept private (mail files, for instance). The perlfunc(1) entry on | |
19799a22 | 2613 | C<umask> discusses the choice of MASK in more detail. |
a0d0e21e | 2614 | |
cc1852e8 JH |
2615 | Note that according to the POSIX 1003.1-1996 the FILENAME may have any |
2616 | number of trailing slashes. Some operating and filesystems do not get | |
2617 | this right, so Perl automatically removes all trailing slashes to keep | |
2618 | everyone happy. | |
2619 | ||
a0d0e21e LW |
2620 | =item msgctl ID,CMD,ARG |
2621 | ||
f86cebdf | 2622 | Calls the System V IPC function msgctl(2). You'll probably have to say |
0ade1984 JH |
2623 | |
2624 | use IPC::SysV; | |
2625 | ||
7660c0ab A |
2626 | first to get the correct constant definitions. If CMD is C<IPC_STAT>, |
2627 | then ARG must be a variable which will hold the returned C<msqid_ds> | |
951ba7fe GS |
2628 | structure. Returns like C<ioctl>: the undefined value for error, |
2629 | C<"0 but true"> for zero, or the actual return value otherwise. See also | |
4755096e | 2630 | L<perlipc/"SysV IPC">, C<IPC::SysV>, and C<IPC::Semaphore> documentation. |
a0d0e21e LW |
2631 | |
2632 | =item msgget KEY,FLAGS | |
2633 | ||
f86cebdf | 2634 | Calls the System V IPC function msgget(2). Returns the message queue |
4755096e GS |
2635 | id, or the undefined value if there is an error. See also |
2636 | L<perlipc/"SysV IPC"> and C<IPC::SysV> and C<IPC::Msg> documentation. | |
a0d0e21e | 2637 | |
a0d0e21e LW |
2638 | =item msgrcv ID,VAR,SIZE,TYPE,FLAGS |
2639 | ||
2640 | Calls the System V IPC function msgrcv to receive a message from | |
2641 | message queue ID into variable VAR with a maximum message size of | |
41d6edb2 JH |
2642 | SIZE. Note that when a message is received, the message type as a |
2643 | native long integer will be the first thing in VAR, followed by the | |
2644 | actual message. This packing may be opened with C<unpack("l! a*")>. | |
2645 | Taints the variable. Returns true if successful, or false if there is | |
4755096e GS |
2646 | an error. See also L<perlipc/"SysV IPC">, C<IPC::SysV>, and |
2647 | C<IPC::SysV::Msg> documentation. | |
41d6edb2 JH |
2648 | |
2649 | =item msgsnd ID,MSG,FLAGS | |
2650 | ||
2651 | Calls the System V IPC function msgsnd to send the message MSG to the | |
2652 | message queue ID. MSG must begin with the native long integer message | |
2653 | type, and be followed by the length of the actual message, and finally | |
2654 | the message itself. This kind of packing can be achieved with | |
2655 | C<pack("l! a*", $type, $message)>. Returns true if successful, | |
2656 | or false if there is an error. See also C<IPC::SysV> | |
2657 | and C<IPC::SysV::Msg> documentation. | |
a0d0e21e LW |
2658 | |
2659 | =item my EXPR | |
2660 | ||
307ea6df JH |
2661 | =item my TYPE EXPR |
2662 | ||
1d2de774 | 2663 | =item my EXPR : ATTRS |
09bef843 | 2664 | |
1d2de774 | 2665 | =item my TYPE EXPR : ATTRS |
307ea6df | 2666 | |
19799a22 | 2667 | A C<my> declares the listed variables to be local (lexically) to the |
1d2de774 JH |
2668 | enclosing block, file, or C<eval>. If more than one value is listed, |
2669 | the list must be placed in parentheses. | |
307ea6df | 2670 | |
1d2de774 JH |
2671 | The exact semantics and interface of TYPE and ATTRS are still |
2672 | evolving. TYPE is currently bound to the use of C<fields> pragma, | |
307ea6df JH |
2673 | and attributes are handled using the C<attributes> pragma, or starting |
2674 | from Perl 5.8.0 also via the C<Attribute::Handlers> module. See | |
2675 | L<perlsub/"Private Variables via my()"> for details, and L<fields>, | |
2676 | L<attributes>, and L<Attribute::Handlers>. | |
4633a7c4 | 2677 | |
a0d0e21e LW |
2678 | =item next LABEL |
2679 | ||
2680 | =item next | |
2681 | ||
2682 | The C<next> command is like the C<continue> statement in C; it starts | |
2683 | the next iteration of the loop: | |
2684 | ||
4633a7c4 LW |
2685 | LINE: while (<STDIN>) { |
2686 | next LINE if /^#/; # discard comments | |
5a964f20 | 2687 | #... |
a0d0e21e LW |
2688 | } |
2689 | ||
2690 | Note that if there were a C<continue> block on the above, it would get | |
2691 | executed even on discarded lines. If the LABEL is omitted, the command | |
2692 | refers to the innermost enclosing loop. | |
2693 | ||
4968c1e4 | 2694 | C<next> cannot be used to exit a block which returns a value such as |
2b5ab1e7 TC |
2695 | C<eval {}>, C<sub {}> or C<do {}>, and should not be used to exit |
2696 | a grep() or map() operation. | |
4968c1e4 | 2697 | |
6c1372ed GS |
2698 | Note that a block by itself is semantically identical to a loop |
2699 | that executes once. Thus C<next> will exit such a block early. | |
2700 | ||
98293880 JH |
2701 | See also L</continue> for an illustration of how C<last>, C<next>, and |
2702 | C<redo> work. | |
1d2dff63 | 2703 | |
4a66ea5a RGS |
2704 | =item no Module VERSION LIST |
2705 | ||
2706 | =item no Module VERSION | |
2707 | ||
a0d0e21e LW |
2708 | =item no Module LIST |
2709 | ||
4a66ea5a RGS |
2710 | =item no Module |
2711 | ||
7660c0ab | 2712 | See the L</use> function, which C<no> is the opposite of. |
a0d0e21e LW |
2713 | |
2714 | =item oct EXPR | |
2715 | ||
54310121 | 2716 | =item oct |
bbce6d69 | 2717 | |
4633a7c4 | 2718 | Interprets EXPR as an octal string and returns the corresponding |
4f19785b WSI |
2719 | value. (If EXPR happens to start off with C<0x>, interprets it as a |
2720 | hex string. If EXPR starts off with C<0b>, it is interpreted as a | |
53305cf1 NC |
2721 | binary string. Leading whitespace is ignored in all three cases.) |
2722 | The following will handle decimal, binary, octal, and hex in the standard | |
2723 | Perl or C notation: | |
a0d0e21e LW |
2724 | |
2725 | $val = oct($val) if $val =~ /^0/; | |
2726 | ||
19799a22 GS |
2727 | If EXPR is omitted, uses C<$_>. To go the other way (produce a number |
2728 | in octal), use sprintf() or printf(): | |
2729 | ||
2730 | $perms = (stat("filename"))[2] & 07777; | |
2731 | $oct_perms = sprintf "%lo", $perms; | |
2732 | ||
2733 | The oct() function is commonly used when a string such as C<644> needs | |
2734 | to be converted into a file mode, for example. (Although perl will | |
2735 | automatically convert strings into numbers as needed, this automatic | |
2736 | conversion assumes base 10.) | |
a0d0e21e LW |
2737 | |
2738 | =item open FILEHANDLE,EXPR | |
2739 | ||
68bd7414 NIS |
2740 | =item open FILEHANDLE,MODE,EXPR |
2741 | ||
2742 | =item open FILEHANDLE,MODE,EXPR,LIST | |
2743 | ||
ba964c95 T |
2744 | =item open FILEHANDLE,MODE,REFERENCE |
2745 | ||
a0d0e21e LW |
2746 | =item open FILEHANDLE |
2747 | ||
2748 | Opens the file whose filename is given by EXPR, and associates it with | |
ed53a2bb JH |
2749 | FILEHANDLE. |
2750 | ||
2751 | (The following is a comprehensive reference to open(): for a gentler | |
2752 | introduction you may consider L<perlopentut>.) | |
2753 | ||
2754 | If FILEHANDLE is an undefined lexical (C<my>) variable the variable is | |
2755 | assigned a reference to a new anonymous filehandle, otherwise if | |
2756 | FILEHANDLE is an expression, its value is used as the name of the real | |
2757 | filehandle wanted. (This is considered a symbolic reference, so C<use | |
2758 | strict 'refs'> should I<not> be in effect.) | |
2759 | ||
2760 | If EXPR is omitted, the scalar variable of the same name as the | |
2761 | FILEHANDLE contains the filename. (Note that lexical variables--those | |
2762 | declared with C<my>--will not work for this purpose; so if you're | |
67408cae | 2763 | using C<my>, specify EXPR in your call to open.) |
ed53a2bb JH |
2764 | |
2765 | If three or more arguments are specified then the mode of opening and | |
2766 | the file name are separate. If MODE is C<< '<' >> or nothing, the file | |
2767 | is opened for input. If MODE is C<< '>' >>, the file is truncated and | |
2768 | opened for output, being created if necessary. If MODE is C<<< '>>' >>>, | |
b76cc8ba | 2769 | the file is opened for appending, again being created if necessary. |
5a964f20 | 2770 | |
ed53a2bb JH |
2771 | You can put a C<'+'> in front of the C<< '>' >> or C<< '<' >> to |
2772 | indicate that you want both read and write access to the file; thus | |
2773 | C<< '+<' >> is almost always preferred for read/write updates--the C<< | |
2774 | '+>' >> mode would clobber the file first. You can't usually use | |
2775 | either read-write mode for updating textfiles, since they have | |
2776 | variable length records. See the B<-i> switch in L<perlrun> for a | |
2777 | better approach. The file is created with permissions of C<0666> | |
2778 | modified by the process' C<umask> value. | |
2779 | ||
2780 | These various prefixes correspond to the fopen(3) modes of C<'r'>, | |
2781 | C<'r+'>, C<'w'>, C<'w+'>, C<'a'>, and C<'a+'>. | |
5f05dabc | 2782 | |
6170680b IZ |
2783 | In the 2-arguments (and 1-argument) form of the call the mode and |
2784 | filename should be concatenated (in this order), possibly separated by | |
68bd7414 NIS |
2785 | spaces. It is possible to omit the mode in these forms if the mode is |
2786 | C<< '<' >>. | |
6170680b | 2787 | |
7660c0ab | 2788 | If the filename begins with C<'|'>, the filename is interpreted as a |
5a964f20 | 2789 | command to which output is to be piped, and if the filename ends with a |
f244e06d GS |
2790 | C<'|'>, the filename is interpreted as a command which pipes output to |
2791 | us. See L<perlipc/"Using open() for IPC"> | |
19799a22 | 2792 | for more examples of this. (You are not allowed to C<open> to a command |
5a964f20 | 2793 | that pipes both in I<and> out, but see L<IPC::Open2>, L<IPC::Open3>, |
4a4eefd0 GS |
2794 | and L<perlipc/"Bidirectional Communication with Another Process"> |
2795 | for alternatives.) | |
cb1a09d0 | 2796 | |
ed53a2bb JH |
2797 | For three or more arguments if MODE is C<'|-'>, the filename is |
2798 | interpreted as a command to which output is to be piped, and if MODE | |
2799 | is C<'-|'>, the filename is interpreted as a command which pipes | |
2800 | output to us. In the 2-arguments (and 1-argument) form one should | |
2801 | replace dash (C<'-'>) with the command. | |
2802 | See L<perlipc/"Using open() for IPC"> for more examples of this. | |
2803 | (You are not allowed to C<open> to a command that pipes both in I<and> | |
2804 | out, but see L<IPC::Open2>, L<IPC::Open3>, and | |
2805 | L<perlipc/"Bidirectional Communication"> for alternatives.) | |
2806 | ||
2807 | In the three-or-more argument form of pipe opens, if LIST is specified | |
2808 | (extra arguments after the command name) then LIST becomes arguments | |
2809 | to the command invoked if the platform supports it. The meaning of | |
2810 | C<open> with more than three arguments for non-pipe modes is not yet | |
2811 | specified. Experimental "layers" may give extra LIST arguments | |
2812 | meaning. | |
6170680b IZ |
2813 | |
2814 | In the 2-arguments (and 1-argument) form opening C<'-'> opens STDIN | |
b76cc8ba | 2815 | and opening C<< '>-' >> opens STDOUT. |
6170680b | 2816 | |
fae2c0fb RGS |
2817 | You may use the three-argument form of open to specify IO "layers" |
2818 | (sometimes also referred to as "disciplines") to be applied to the handle | |
2819 | that affect how the input and output are processed (see L<open> and | |
2820 | L<PerlIO> for more details). For example | |
7207e29d | 2821 | |
9124316e JH |
2822 | open(FH, "<:utf8", "file") |
2823 | ||
2824 | will open the UTF-8 encoded file containing Unicode characters, | |
fae2c0fb RGS |
2825 | see L<perluniintro>. (Note that if layers are specified in the |
2826 | three-arg form then default layers set by the C<open> pragma are | |
01e6739c | 2827 | ignored.) |
ed53a2bb JH |
2828 | |
2829 | Open returns nonzero upon success, the undefined value otherwise. If | |
2830 | the C<open> involved a pipe, the return value happens to be the pid of | |
2831 | the subprocess. | |
cb1a09d0 | 2832 | |
ed53a2bb JH |
2833 | If you're running Perl on a system that distinguishes between text |
2834 | files and binary files, then you should check out L</binmode> for tips | |
2835 | for dealing with this. The key distinction between systems that need | |
2836 | C<binmode> and those that don't is their text file formats. Systems | |
8939ba94 | 2837 | like Unix, Mac OS, and Plan 9, which delimit lines with a single |
ed53a2bb JH |
2838 | character, and which encode that character in C as C<"\n">, do not |
2839 | need C<binmode>. The rest need it. | |
cb1a09d0 | 2840 | |
fb73857a | 2841 | When opening a file, it's usually a bad idea to continue normal execution |
19799a22 GS |
2842 | if the request failed, so C<open> is frequently used in connection with |
2843 | C<die>. Even if C<die> won't do what you want (say, in a CGI script, | |
fb73857a | 2844 | where you want to make a nicely formatted error message (but there are |
5a964f20 | 2845 | modules that can help with that problem)) you should always check |
19799a22 | 2846 | the return value from opening a file. The infrequent exception is when |
fb73857a | 2847 | working with an unopened filehandle is actually what you want to do. |
2848 | ||
ed53a2bb JH |
2849 | As a special case the 3 arg form with a read/write mode and the third |
2850 | argument being C<undef>: | |
b76cc8ba NIS |
2851 | |
2852 | open(TMP, "+>", undef) or die ... | |
2853 | ||
2854 | opens a filehandle to an anonymous temporary file. | |
2855 | ||
ba964c95 T |
2856 | File handles can be opened to "in memory" files held in Perl scalars via: |
2857 | ||
b996200f SB |
2858 | open($fh, '>', \$variable) || .. |
2859 | ||
2860 | Though if you try to re-open C<STDOUT> or C<STDERR> as an "in memory" | |
2861 | file, you have to close it first: | |
2862 | ||
2863 | close STDOUT; | |
2864 | open STDOUT, '>', \$variable or die "Can't open STDOUT: $!"; | |
ba964c95 | 2865 | |
cb1a09d0 | 2866 | Examples: |
a0d0e21e LW |
2867 | |
2868 | $ARTICLE = 100; | |
2869 | open ARTICLE or die "Can't find article $ARTICLE: $!\n"; | |
2870 | while (<ARTICLE>) {... | |
2871 | ||
6170680b | 2872 | open(LOG, '>>/usr/spool/news/twitlog'); # (log is reserved) |
fb73857a | 2873 | # if the open fails, output is discarded |
a0d0e21e | 2874 | |
6170680b | 2875 | open(DBASE, '+<', 'dbase.mine') # open for update |
fb73857a | 2876 | or die "Can't open 'dbase.mine' for update: $!"; |
cb1a09d0 | 2877 | |
6170680b IZ |
2878 | open(DBASE, '+<dbase.mine') # ditto |
2879 | or die "Can't open 'dbase.mine' for update: $!"; | |
2880 | ||
2881 | open(ARTICLE, '-|', "caesar <$article") # decrypt article | |
fb73857a | 2882 | or die "Can't start caesar: $!"; |
a0d0e21e | 2883 | |
6170680b IZ |
2884 | open(ARTICLE, "caesar <$article |") # ditto |
2885 | or die "Can't start caesar: $!"; | |
2886 | ||
2887 | open(EXTRACT, "|sort >/tmp/Tmp$$") # $$ is our process id | |
fb73857a | 2888 | or die "Can't start sort: $!"; |
a0d0e21e | 2889 | |
ba964c95 T |
2890 | # in memory files |
2891 | open(MEMORY,'>', \$var) | |
2892 | or die "Can't open memory file: $!"; | |
2893 | print MEMORY "foo!\n"; # output will end up in $var | |
2894 | ||
a0d0e21e LW |
2895 | # process argument list of files along with any includes |
2896 | ||
2897 | foreach $file (@ARGV) { | |
2898 | process($file, 'fh00'); | |
2899 | } | |
2900 | ||
2901 | sub process { | |
5a964f20 | 2902 | my($filename, $input) = @_; |
a0d0e21e LW |
2903 | $input++; # this is a string increment |
2904 | unless (open($input, $filename)) { | |
2905 | print STDERR "Can't open $filename: $!\n"; | |
2906 | return; | |
2907 | } | |
2908 | ||
5a964f20 | 2909 | local $_; |
a0d0e21e LW |
2910 | while (<$input>) { # note use of indirection |
2911 | if (/^#include "(.*)"/) { | |
2912 | process($1, $input); | |
2913 | next; | |
2914 | } | |
5a964f20 | 2915 | #... # whatever |
a0d0e21e LW |
2916 | } |
2917 | } | |
2918 | ||
2919 | You may also, in the Bourne shell tradition, specify an EXPR beginning | |
61eff3bc | 2920 | with C<< '>&' >>, in which case the rest of the string is interpreted as the |
5a964f20 | 2921 | name of a filehandle (or file descriptor, if numeric) to be |
61eff3bc JH |
2922 | duped and opened. You may use C<&> after C<< > >>, C<<< >> >>>, |
2923 | C<< < >>, C<< +> >>, C<<< +>> >>>, and C<< +< >>. The | |
a0d0e21e | 2924 | mode you specify should match the mode of the original filehandle. |
184e9718 | 2925 | (Duping a filehandle does not take into account any existing contents of |
9124316e | 2926 | IO buffers.) If you use the 3 arg form then you can pass either a number, |
b76cc8ba | 2927 | the name of a filehandle or the normal "reference to a glob". |
6170680b | 2928 | |
eae1b76b SB |
2929 | Here is a script that saves, redirects, and restores C<STDOUT> and |
2930 | C<STDERR> using various methods: | |
a0d0e21e LW |
2931 | |
2932 | #!/usr/bin/perl | |
eae1b76b SB |
2933 | open my $oldout, ">&STDOUT" or die "Can't dup STDOUT: $!"; |
2934 | open OLDERR, ">&", \*STDERR or die "Can't dup STDERR: $!"; | |
818c4caa | 2935 | |
eae1b76b SB |
2936 | open STDOUT, '>', "foo.out" or die "Can't redirect STDOUT: $!"; |
2937 | open STDERR, ">&STDOUT" or die "Can't dup STDOUT: $!"; | |
a0d0e21e | 2938 | |
eae1b76b SB |
2939 | select STDERR; $| = 1; # make unbuffered |
2940 | select STDOUT; $| = 1; # make unbuffered | |
a0d0e21e LW |
2941 | |
2942 | print STDOUT "stdout 1\n"; # this works for | |
2943 | print STDERR "stderr 1\n"; # subprocesses too | |
2944 | ||
eae1b76b SB |
2945 | close STDOUT; |
2946 | close STDERR; | |
a0d0e21e | 2947 | |
eae1b76b SB |
2948 | open STDOUT, ">&", $oldout or die "Can't dup \$oldout: $!"; |
2949 | open STDERR, ">&OLDERR" or die "Can't dup OLDERR: $!"; | |
a0d0e21e LW |
2950 | |
2951 | print STDOUT "stdout 2\n"; | |
2952 | print STDERR "stderr 2\n"; | |
2953 | ||
df632fdf JH |
2954 | If you specify C<< '<&=N' >>, where C<N> is a number, then Perl will |
2955 | do an equivalent of C's C<fdopen> of that file descriptor; this is | |
2956 | more parsimonious of file descriptors. For example: | |
a0d0e21e LW |
2957 | |
2958 | open(FILEHANDLE, "<&=$fd") | |
df632fdf | 2959 | |
b76cc8ba | 2960 | or |
df632fdf | 2961 | |
b76cc8ba | 2962 | open(FILEHANDLE, "<&=", $fd) |
a0d0e21e | 2963 | |
df632fdf JH |
2964 | Note that if Perl is using the standard C libraries' fdopen() then on |
2965 | many UNIX systems, fdopen() is known to fail when file descriptors | |
4af147f6 | 2966 | exceed a certain value, typically 255. If you need more file |
b76cc8ba | 2967 | descriptors than that, consider rebuilding Perl to use the C<PerlIO>. |
4af147f6 | 2968 | |
df632fdf JH |
2969 | You can see whether Perl has been compiled with PerlIO or not by |
2970 | running C<perl -V> and looking for C<useperlio=> line. If C<useperlio> | |
2971 | is C<define>, you have PerlIO, otherwise you don't. | |
2972 | ||
6170680b IZ |
2973 | If you open a pipe on the command C<'-'>, i.e., either C<'|-'> or C<'-|'> |
2974 | with 2-arguments (or 1-argument) form of open(), then | |
a0d0e21e | 2975 | there is an implicit fork done, and the return value of open is the pid |
7660c0ab | 2976 | of the child within the parent process, and C<0> within the child |
184e9718 | 2977 | process. (Use C<defined($pid)> to determine whether the open was successful.) |
a0d0e21e LW |
2978 | The filehandle behaves normally for the parent, but i/o to that |
2979 | filehandle is piped from/to the STDOUT/STDIN of the child process. | |
2980 | In the child process the filehandle isn't opened--i/o happens from/to | |
2981 | the new STDOUT or STDIN. Typically this is used like the normal | |
2982 | piped open when you want to exercise more control over just how the | |
2983 | pipe command gets executed, such as when you are running setuid, and | |
54310121 | 2984 | don't want to have to scan shell commands for metacharacters. |
6170680b | 2985 | The following triples are more or less equivalent: |
a0d0e21e LW |
2986 | |
2987 | open(FOO, "|tr '[a-z]' '[A-Z]'"); | |
6170680b IZ |
2988 | open(FOO, '|-', "tr '[a-z]' '[A-Z]'"); |
2989 | open(FOO, '|-') || exec 'tr', '[a-z]', '[A-Z]'; | |
b76cc8ba | 2990 | open(FOO, '|-', "tr", '[a-z]', '[A-Z]'); |
a0d0e21e LW |
2991 | |
2992 | open(FOO, "cat -n '$file'|"); | |
6170680b IZ |
2993 | open(FOO, '-|', "cat -n '$file'"); |
2994 | open(FOO, '-|') || exec 'cat', '-n', $file; | |
b76cc8ba NIS |
2995 | open(FOO, '-|', "cat", '-n', $file); |
2996 | ||
2997 | The last example in each block shows the pipe as "list form", which is | |
64da03b2 JH |
2998 | not yet supported on all platforms. A good rule of thumb is that if |
2999 | your platform has true C<fork()> (in other words, if your platform is | |
3000 | UNIX) you can use the list form. | |
a0d0e21e | 3001 | |
4633a7c4 LW |
3002 | See L<perlipc/"Safe Pipe Opens"> for more examples of this. |
3003 | ||
0f897271 GS |
3004 | Beginning with v5.6.0, Perl will attempt to flush all files opened for |
3005 | output before any operation that may do a fork, but this may not be | |
3006 | supported on some platforms (see L<perlport>). To be safe, you may need | |
3007 | to set C<$|> ($AUTOFLUSH in English) or call the C<autoflush()> method | |
3008 | of C<IO::Handle> on any open handles. | |
3009 | ||
ed53a2bb JH |
3010 | On systems that support a close-on-exec flag on files, the flag will |
3011 | be set for the newly opened file descriptor as determined by the value | |
3012 | of $^F. See L<perlvar/$^F>. | |
a0d0e21e | 3013 | |
0dccf244 CS |
3014 | Closing any piped filehandle causes the parent process to wait for the |
3015 | child to finish, and returns the status value in C<$?>. | |
3016 | ||
ed53a2bb JH |
3017 | The filename passed to 2-argument (or 1-argument) form of open() will |
3018 | have leading and trailing whitespace deleted, and the normal | |
3019 | redirection characters honored. This property, known as "magic open", | |
5a964f20 | 3020 | can often be used to good effect. A user could specify a filename of |
7660c0ab | 3021 | F<"rsh cat file |">, or you could change certain filenames as needed: |
5a964f20 TC |
3022 | |
3023 | $filename =~ s/(.*\.gz)\s*$/gzip -dc < $1|/; | |
3024 | open(FH, $filename) or die "Can't open $filename: $!"; | |
3025 | ||
6170680b IZ |
3026 | Use 3-argument form to open a file with arbitrary weird characters in it, |
3027 | ||
3028 | open(FOO, '<', $file); | |
3029 | ||
3030 | otherwise it's necessary to protect any leading and trailing whitespace: | |
5a964f20 TC |
3031 | |
3032 | $file =~ s#^(\s)#./$1#; | |
3033 | open(FOO, "< $file\0"); | |
3034 | ||
a31a806a | 3035 | (this may not work on some bizarre filesystems). One should |
106325ad | 3036 | conscientiously choose between the I<magic> and 3-arguments form |
6170680b IZ |
3037 | of open(): |
3038 | ||
3039 | open IN, $ARGV[0]; | |
3040 | ||
3041 | will allow the user to specify an argument of the form C<"rsh cat file |">, | |
3042 | but will not work on a filename which happens to have a trailing space, while | |
3043 | ||
3044 | open IN, '<', $ARGV[0]; | |
3045 | ||
3046 | will have exactly the opposite restrictions. | |
3047 | ||
19799a22 | 3048 | If you want a "real" C C<open> (see L<open(2)> on your system), then you |
6170680b IZ |
3049 | should use the C<sysopen> function, which involves no such magic (but |
3050 | may use subtly different filemodes than Perl open(), which is mapped | |
3051 | to C fopen()). This is | |
5a964f20 TC |
3052 | another way to protect your filenames from interpretation. For example: |
3053 | ||
3054 | use IO::Handle; | |
3055 | sysopen(HANDLE, $path, O_RDWR|O_CREAT|O_EXCL) | |
3056 | or die "sysopen $path: $!"; | |
3057 | $oldfh = select(HANDLE); $| = 1; select($oldfh); | |
38762f02 | 3058 | print HANDLE "stuff $$\n"; |
5a964f20 TC |
3059 | seek(HANDLE, 0, 0); |
3060 | print "File contains: ", <HANDLE>; | |
3061 | ||
7660c0ab A |
3062 | Using the constructor from the C<IO::Handle> package (or one of its |
3063 | subclasses, such as C<IO::File> or C<IO::Socket>), you can generate anonymous | |
5a964f20 TC |
3064 | filehandles that have the scope of whatever variables hold references to |
3065 | them, and automatically close whenever and however you leave that scope: | |
c07a80fd | 3066 | |
5f05dabc | 3067 | use IO::File; |
5a964f20 | 3068 | #... |
c07a80fd | 3069 | sub read_myfile_munged { |
3070 | my $ALL = shift; | |
5f05dabc | 3071 | my $handle = new IO::File; |
c07a80fd | 3072 | open($handle, "myfile") or die "myfile: $!"; |
3073 | $first = <$handle> | |
3074 | or return (); # Automatically closed here. | |
3075 | mung $first or die "mung failed"; # Or here. | |
3076 | return $first, <$handle> if $ALL; # Or here. | |
3077 | $first; # Or here. | |
3078 | } | |
3079 | ||
b687b08b | 3080 | See L</seek> for some details about mixing reading and writing. |
a0d0e21e LW |
3081 | |
3082 | =item opendir DIRHANDLE,EXPR | |
3083 | ||
19799a22 GS |
3084 | Opens a directory named EXPR for processing by C<readdir>, C<telldir>, |
3085 | C<seekdir>, C<rewinddir>, and C<closedir>. Returns true if successful. | |
a0d0e21e LW |
3086 | DIRHANDLEs have their own namespace separate from FILEHANDLEs. |
3087 | ||
3088 | =item ord EXPR | |
3089 | ||
54310121 | 3090 | =item ord |
bbce6d69 | 3091 | |
121910a4 JH |
3092 | Returns the numeric (the native 8-bit encoding, like ASCII or EBCDIC, |
3093 | or Unicode) value of the first character of EXPR. If EXPR is omitted, | |
3094 | uses C<$_>. | |
3095 | ||
3096 | For the reverse, see L</chr>. | |
3097 | See L<perlunicode> and L<encoding> for more about Unicode. | |
a0d0e21e | 3098 | |
77ca0c92 LW |
3099 | =item our EXPR |
3100 | ||
307ea6df JH |
3101 | =item our EXPR TYPE |
3102 | ||
1d2de774 | 3103 | =item our EXPR : ATTRS |
9969eac4 | 3104 | |
1d2de774 | 3105 | =item our TYPE EXPR : ATTRS |
307ea6df | 3106 | |
77ca0c92 LW |
3107 | An C<our> declares the listed variables to be valid globals within |
3108 | the enclosing block, file, or C<eval>. That is, it has the same | |
3109 | scoping rules as a "my" declaration, but does not create a local | |
3110 | variable. If more than one value is listed, the list must be placed | |
3111 | in parentheses. The C<our> declaration has no semantic effect unless | |
3112 | "use strict vars" is in effect, in which case it lets you use the | |
3113 | declared global variable without qualifying it with a package name. | |
3114 | (But only within the lexical scope of the C<our> declaration. In this | |
3115 | it differs from "use vars", which is package scoped.) | |
3116 | ||
f472eb5c GS |
3117 | An C<our> declaration declares a global variable that will be visible |
3118 | across its entire lexical scope, even across package boundaries. The | |
3119 | package in which the variable is entered is determined at the point | |
3120 | of the declaration, not at the point of use. This means the following | |
3121 | behavior holds: | |
3122 | ||
3123 | package Foo; | |
3124 | our $bar; # declares $Foo::bar for rest of lexical scope | |
3125 | $bar = 20; | |
3126 | ||
3127 | package Bar; | |
3128 | print $bar; # prints 20 | |
3129 | ||
3130 | Multiple C<our> declarations in the same lexical scope are allowed | |
3131 | if they are in different packages. If they happened to be in the same | |
3132 | package, Perl will emit warnings if you have asked for them. | |
3133 | ||
3134 | use warnings; | |
3135 | package Foo; | |
3136 | our $bar; # declares $Foo::bar for rest of lexical scope | |
3137 | $bar = 20; | |
3138 | ||
3139 | package Bar; | |
3140 | our $bar = 30; # declares $Bar::bar for rest of lexical scope | |
3141 | print $bar; # prints 30 | |
3142 | ||
3143 | our $bar; # emits warning | |
3144 | ||
9969eac4 | 3145 | An C<our> declaration may also have a list of attributes associated |
307ea6df JH |
3146 | with it. |
3147 | ||
1d2de774 JH |
3148 | The exact semantics and interface of TYPE and ATTRS are still |
3149 | evolving. TYPE is currently bound to the use of C<fields> pragma, | |
307ea6df JH |
3150 | and attributes are handled using the C<attributes> pragma, or starting |
3151 | from Perl 5.8.0 also via the C<Attribute::Handlers> module. See | |
3152 | L<perlsub/"Private Variables via my()"> for details, and L<fields>, | |
3153 | L<attributes>, and L<Attribute::Handlers>. | |
3154 | ||
3155 | The only currently recognized C<our()> attribute is C<unique> which | |
3156 | indicates that a single copy of the global is to be used by all | |
3157 | interpreters should the program happen to be running in a | |
3158 | multi-interpreter environment. (The default behaviour would be for | |
3159 | each interpreter to have its own copy of the global.) Examples: | |
9969eac4 | 3160 | |
51d2bbcc JH |
3161 | our @EXPORT : unique = qw(foo); |
3162 | our %EXPORT_TAGS : unique = (bar => [qw(aa bb cc)]); | |
3163 | our $VERSION : unique = "1.00"; | |
9969eac4 | 3164 | |
96fa8c42 | 3165 | Note that this attribute also has the effect of making the global |
72e53bfb JH |
3166 | readonly when the first new interpreter is cloned (for example, |
3167 | when the first new thread is created). | |
96fa8c42 | 3168 | |
9969eac4 BS |
3169 | Multi-interpreter environments can come to being either through the |
3170 | fork() emulation on Windows platforms, or by embedding perl in a | |
51d2bbcc | 3171 | multi-threaded application. The C<unique> attribute does nothing in |
9969eac4 BS |
3172 | all other environments. |
3173 | ||
a0d0e21e LW |
3174 | =item pack TEMPLATE,LIST |
3175 | ||
2b6c5635 GS |
3176 | Takes a LIST of values and converts it into a string using the rules |
3177 | given by the TEMPLATE. The resulting string is the concatenation of | |
3178 | the converted values. Typically, each converted value looks | |
3179 | like its machine-level representation. For example, on 32-bit machines | |
3180 | a converted integer may be represented by a sequence of 4 bytes. | |
3181 | ||
18529408 IZ |
3182 | The TEMPLATE is a sequence of characters that give the order and type |
3183 | of values, as follows: | |
a0d0e21e | 3184 | |
5a929a98 | 3185 | a A string with arbitrary binary data, will be null padded. |
121910a4 JH |
3186 | A A text (ASCII) string, will be space padded. |
3187 | Z A null terminated (ASCIZ) string, will be null padded. | |
5a929a98 | 3188 | |
2b6c5635 GS |
3189 | b A bit string (ascending bit order inside each byte, like vec()). |
3190 | B A bit string (descending bit order inside each byte). | |
a0d0e21e LW |
3191 | h A hex string (low nybble first). |
3192 | H A hex string (high nybble first). | |
3193 | ||
3194 | c A signed char value. | |
a0ed51b3 | 3195 | C An unsigned char value. Only does bytes. See U for Unicode. |
96e4d5b1 | 3196 | |
a0d0e21e LW |
3197 | s A signed short value. |
3198 | S An unsigned short value. | |
96e4d5b1 | 3199 | (This 'short' is _exactly_ 16 bits, which may differ from |
851646ae JH |
3200 | what a local C compiler calls 'short'. If you want |
3201 | native-length shorts, use the '!' suffix.) | |
96e4d5b1 | 3202 | |
a0d0e21e LW |
3203 | i A signed integer value. |
3204 | I An unsigned integer value. | |
19799a22 | 3205 | (This 'integer' is _at_least_ 32 bits wide. Its exact |
f86cebdf GS |
3206 | size depends on what a local C compiler calls 'int', |
3207 | and may even be larger than the 'long' described in | |
3208 | the next item.) | |
96e4d5b1 | 3209 | |
a0d0e21e LW |
3210 | l A signed long value. |
3211 | L An unsigned long value. | |
96e4d5b1 | 3212 | (This 'long' is _exactly_ 32 bits, which may differ from |
851646ae JH |
3213 | what a local C compiler calls 'long'. If you want |
3214 | native-length longs, use the '!' suffix.) | |
a0d0e21e | 3215 | |
5d11dd56 MG |
3216 | n An unsigned short in "network" (big-endian) order. |
3217 | N An unsigned long in "network" (big-endian) order. | |
3218 | v An unsigned short in "VAX" (little-endian) order. | |
3219 | V An unsigned long in "VAX" (little-endian) order. | |
96e4d5b1 | 3220 | (These 'shorts' and 'longs' are _exactly_ 16 bits and |
3221 | _exactly_ 32 bits, respectively.) | |
a0d0e21e | 3222 | |
dae0da7a JH |
3223 | q A signed quad (64-bit) value. |
3224 | Q An unsigned quad value. | |
851646ae JH |
3225 | (Quads are available only if your system supports 64-bit |
3226 | integer values _and_ if Perl has been compiled to support those. | |
dae0da7a JH |
3227 | Causes a fatal error otherwise.) |
3228 | ||
92d41999 JH |
3229 | j A signed integer value (a Perl internal integer, IV). |
3230 | J An unsigned integer value (a Perl internal unsigned integer, UV). | |
3231 | ||
a0d0e21e LW |
3232 | f A single-precision float in the native format. |
3233 | d A double-precision float in the native format. | |
3234 | ||
92d41999 JH |
3235 | F A floating point value in the native native format |
3236 | (a Perl internal floating point value, NV). | |
3237 | D A long double-precision float in the native format. | |
3238 | (Long doubles are available only if your system supports long | |
3239 | double values _and_ if Perl has been compiled to support those. | |
3240 | Causes a fatal error otherwise.) | |
3241 | ||
a0d0e21e LW |
3242 | p A pointer to a null-terminated string. |
3243 | P A pointer to a structure (fixed-length string). | |
3244 | ||
3245 | u A uuencoded string. | |
ad0029c4 JH |
3246 | U A Unicode character number. Encodes to UTF-8 internally |
3247 | (or UTF-EBCDIC in EBCDIC platforms). | |
a0d0e21e | 3248 | |
96e4d5b1 | 3249 | w A BER compressed integer. Its bytes represent an unsigned |
f86cebdf GS |
3250 | integer in base 128, most significant digit first, with as |
3251 | few digits as possible. Bit eight (the high bit) is set | |
3252 | on each byte except the last. | |
def98dd4 | 3253 | |
a0d0e21e LW |
3254 | x A null byte. |
3255 | X Back up a byte. | |
3256 | @ Null fill to absolute position. | |
206947d2 | 3257 | ( Start of a ()-group. |
a0d0e21e | 3258 | |
5a929a98 VU |
3259 | The following rules apply: |
3260 | ||
3261 | =over 8 | |
3262 | ||
3263 | =item * | |
3264 | ||
5a964f20 | 3265 | Each letter may optionally be followed by a number giving a repeat |
951ba7fe | 3266 | count. With all types except C<a>, C<A>, C<Z>, C<b>, C<B>, C<h>, |
206947d2 IZ |
3267 | C<H>, C<@>, C<x>, C<X> and C<P> the pack function will gobble up that |
3268 | many values from the LIST. A C<*> for the repeat count means to use | |
3269 | however many items are left, except for C<@>, C<x>, C<X>, where it is | |
3270 | equivalent to C<0>, and C<u>, where it is equivalent to 1 (or 45, what | |
3271 | is the same). A numeric repeat count may optionally be enclosed in | |
3272 | brackets, as in C<pack 'C[80]', @arr>. | |
3273 | ||
3274 | One can replace the numeric repeat count by a template enclosed in brackets; | |
3275 | then the packed length of this template in bytes is used as a count. | |
62f95557 IZ |
3276 | For example, C<x[L]> skips a long (it skips the number of bytes in a long); |
3277 | the template C<$t X[$t] $t> unpack()s twice what $t unpacks. | |
3278 | If the template in brackets contains alignment commands (such as C<x![d]>), | |
3279 | its packed length is calculated as if the start of the template has the maximal | |
3280 | possible alignment. | |
2b6c5635 | 3281 | |
951ba7fe | 3282 | When used with C<Z>, C<*> results in the addition of a trailing null |
2b6c5635 GS |
3283 | byte (so the packed result will be one longer than the byte C<length> |
3284 | of the item). | |
3285 | ||
951ba7fe | 3286 | The repeat count for C<u> is interpreted as the maximal number of bytes |
2b6c5635 | 3287 | to encode per line of output, with 0 and 1 replaced by 45. |
5a929a98 VU |
3288 | |
3289 | =item * | |
3290 | ||
951ba7fe | 3291 | The C<a>, C<A>, and C<Z> types gobble just one value, but pack it as a |
5a929a98 | 3292 | string of length count, padding with nulls or spaces as necessary. When |
951ba7fe GS |
3293 | unpacking, C<A> strips trailing spaces and nulls, C<Z> strips everything |
3294 | after the first null, and C<a> returns data verbatim. When packing, | |
3295 | C<a>, and C<Z> are equivalent. | |
2b6c5635 GS |
3296 | |
3297 | If the value-to-pack is too long, it is truncated. If too long and an | |
951ba7fe GS |
3298 | explicit count is provided, C<Z> packs only C<$count-1> bytes, followed |
3299 | by a null byte. Thus C<Z> always packs a trailing null byte under | |
2b6c5635 | 3300 | all circumstances. |
5a929a98 VU |
3301 | |
3302 | =item * | |
3303 | ||
951ba7fe | 3304 | Likewise, the C<b> and C<B> fields pack a string that many bits long. |
c73032f5 IZ |
3305 | Each byte of the input field of pack() generates 1 bit of the result. |
3306 | Each result bit is based on the least-significant bit of the corresponding | |
3307 | input byte, i.e., on C<ord($byte)%2>. In particular, bytes C<"0"> and | |
3308 | C<"1"> generate bits 0 and 1, as do bytes C<"\0"> and C<"\1">. | |
3309 | ||
3310 | Starting from the beginning of the input string of pack(), each 8-tuple | |
951ba7fe | 3311 | of bytes is converted to 1 byte of output. With format C<b> |
c73032f5 | 3312 | the first byte of the 8-tuple determines the least-significant bit of a |
951ba7fe | 3313 | byte, and with format C<B> it determines the most-significant bit of |
c73032f5 IZ |
3314 | a byte. |
3315 | ||
3316 | If the length of the input string is not exactly divisible by 8, the | |
3317 | remainder is packed as if the input string were padded by null bytes | |
3318 | at the end. Similarly, during unpack()ing the "extra" bits are ignored. | |
3319 | ||
3320 | If the input string of pack() is longer than needed, extra bytes are ignored. | |
2b6c5635 GS |
3321 | A C<*> for the repeat count of pack() means to use all the bytes of |
3322 | the input field. On unpack()ing the bits are converted to a string | |
3323 | of C<"0">s and C<"1">s. | |
5a929a98 VU |
3324 | |
3325 | =item * | |
3326 | ||
951ba7fe | 3327 | The C<h> and C<H> fields pack a string that many nybbles (4-bit groups, |
851646ae | 3328 | representable as hexadecimal digits, 0-9a-f) long. |
5a929a98 | 3329 | |
c73032f5 IZ |
3330 | Each byte of the input field of pack() generates 4 bits of the result. |
3331 | For non-alphabetical bytes the result is based on the 4 least-significant | |
3332 | bits of the input byte, i.e., on C<ord($byte)%16>. In particular, | |
3333 | bytes C<"0"> and C<"1"> generate nybbles 0 and 1, as do bytes | |
3334 | C<"\0"> and C<"\1">. For bytes C<"a".."f"> and C<"A".."F"> the result | |
3335 | is compatible with the usual hexadecimal digits, so that C<"a"> and | |
3336 | C<"A"> both generate the nybble C<0xa==10>. The result for bytes | |
3337 | C<"g".."z"> and C<"G".."Z"> is not well-defined. | |
3338 | ||
3339 | Starting from the beginning of the input string of pack(), each pair | |
951ba7fe | 3340 | of bytes is converted to 1 byte of output. With format C<h> the |
c73032f5 | 3341 | first byte of the pair determines the least-significant nybble of the |
951ba7fe | 3342 | output byte, and with format C<H> it determines the most-significant |
c73032f5 IZ |
3343 | nybble. |
3344 | ||
3345 | If the length of the input string is not even, it behaves as if padded | |
3346 | by a null byte at the end. Similarly, during unpack()ing the "extra" | |
3347 | nybbles are ignored. | |
3348 | ||
3349 | If the input string of pack() is longer than needed, extra bytes are ignored. | |
3350 | A C<*> for the repeat count of pack() means to use all the bytes of | |
3351 | the input field. On unpack()ing the bits are converted to a string | |
3352 | of hexadecimal digits. | |
3353 | ||
5a929a98 VU |
3354 | =item * |
3355 | ||
951ba7fe | 3356 | The C<p> type packs a pointer to a null-terminated string. You are |
5a929a98 VU |
3357 | responsible for ensuring the string is not a temporary value (which can |
3358 | potentially get deallocated before you get around to using the packed result). | |
951ba7fe GS |
3359 | The C<P> type packs a pointer to a structure of the size indicated by the |
3360 | length. A NULL pointer is created if the corresponding value for C<p> or | |
3361 | C<P> is C<undef>, similarly for unpack(). | |
5a929a98 VU |
3362 | |
3363 | =item * | |
3364 | ||
951ba7fe GS |
3365 | The C</> template character allows packing and unpacking of strings where |
3366 | the packed structure contains a byte count followed by the string itself. | |
17f4a12d | 3367 | You write I<length-item>C</>I<string-item>. |
43192e07 | 3368 | |
92d41999 JH |
3369 | The I<length-item> can be any C<pack> template letter, and describes |
3370 | how the length value is packed. The ones likely to be of most use are | |
3371 | integer-packing ones like C<n> (for Java strings), C<w> (for ASN.1 or | |
3372 | SNMP) and C<N> (for Sun XDR). | |
43192e07 IP |
3373 | |
3374 | The I<string-item> must, at present, be C<"A*">, C<"a*"> or C<"Z*">. | |
3375 | For C<unpack> the length of the string is obtained from the I<length-item>, | |
3376 | but if you put in the '*' it will be ignored. | |
3377 | ||
17f4a12d IZ |
3378 | unpack 'C/a', "\04Gurusamy"; gives 'Guru' |
3379 | unpack 'a3/A* A*', '007 Bond J '; gives (' Bond','J') | |
3380 | pack 'n/a* w/a*','hello,','world'; gives "\000\006hello,\005world" | |
43192e07 IP |
3381 | |
3382 | The I<length-item> is not returned explicitly from C<unpack>. | |
3383 | ||
951ba7fe GS |
3384 | Adding a count to the I<length-item> letter is unlikely to do anything |
3385 | useful, unless that letter is C<A>, C<a> or C<Z>. Packing with a | |
3386 | I<length-item> of C<a> or C<Z> may introduce C<"\000"> characters, | |
43192e07 IP |
3387 | which Perl does not regard as legal in numeric strings. |
3388 | ||
3389 | =item * | |
3390 | ||
951ba7fe GS |
3391 | The integer types C<s>, C<S>, C<l>, and C<L> may be |
3392 | immediately followed by a C<!> suffix to signify native shorts or | |
3393 | longs--as you can see from above for example a bare C<l> does mean | |
851646ae JH |
3394 | exactly 32 bits, the native C<long> (as seen by the local C compiler) |
3395 | may be larger. This is an issue mainly in 64-bit platforms. You can | |
951ba7fe | 3396 | see whether using C<!> makes any difference by |
726ea183 | 3397 | |
4d0c1c44 GS |
3398 | print length(pack("s")), " ", length(pack("s!")), "\n"; |
3399 | print length(pack("l")), " ", length(pack("l!")), "\n"; | |
ef54e1a4 | 3400 | |
951ba7fe GS |
3401 | C<i!> and C<I!> also work but only because of completeness; |
3402 | they are identical to C<i> and C<I>. | |
ef54e1a4 | 3403 | |
19799a22 GS |
3404 | The actual sizes (in bytes) of native shorts, ints, longs, and long |
3405 | longs on the platform where Perl was built are also available via | |
3406 | L<Config>: | |
3407 | ||
3408 | use Config; | |
3409 | print $Config{shortsize}, "\n"; | |
3410 | print $Config{intsize}, "\n"; | |
3411 | print $Config{longsize}, "\n"; | |
3412 | print $Config{longlongsize}, "\n"; | |
ef54e1a4 | 3413 | |
5074e145 | 3414 | (The C<$Config{longlongsize}> will be undefine if your system does |
b76cc8ba | 3415 | not support long longs.) |
851646ae | 3416 | |
ef54e1a4 JH |
3417 | =item * |
3418 | ||
92d41999 | 3419 | The integer formats C<s>, C<S>, C<i>, C<I>, C<l>, C<L>, C<j>, and C<J> |
ef54e1a4 JH |
3420 | are inherently non-portable between processors and operating systems |
3421 | because they obey the native byteorder and endianness. For example a | |
82e239e7 | 3422 | 4-byte integer 0x12345678 (305419896 decimal) would be ordered natively |
ef54e1a4 | 3423 | (arranged in and handled by the CPU registers) into bytes as |
61eff3bc | 3424 | |
b35e152f JJ |
3425 | 0x12 0x34 0x56 0x78 # big-endian |
3426 | 0x78 0x56 0x34 0x12 # little-endian | |
61eff3bc | 3427 | |
b84d4f81 JH |
3428 | Basically, the Intel and VAX CPUs are little-endian, while everybody |
3429 | else, for example Motorola m68k/88k, PPC, Sparc, HP PA, Power, and | |
3430 | Cray are big-endian. Alpha and MIPS can be either: Digital/Compaq | |
82e239e7 JH |
3431 | used/uses them in little-endian mode; SGI/Cray uses them in big-endian |
3432 | mode. | |
719a3cf5 | 3433 | |
19799a22 | 3434 | The names `big-endian' and `little-endian' are comic references to |
ef54e1a4 JH |
3435 | the classic "Gulliver's Travels" (via the paper "On Holy Wars and a |
3436 | Plea for Peace" by Danny Cohen, USC/ISI IEN 137, April 1, 1980) and | |
19799a22 | 3437 | the egg-eating habits of the Lilliputians. |
61eff3bc | 3438 | |
140cb37e | 3439 | Some systems may have even weirder byte orders such as |
61eff3bc | 3440 | |
ef54e1a4 JH |
3441 | 0x56 0x78 0x12 0x34 |
3442 | 0x34 0x12 0x78 0x56 | |
61eff3bc | 3443 | |
ef54e1a4 JH |
3444 | You can see your system's preference with |
3445 | ||
3446 | print join(" ", map { sprintf "%#02x", $_ } | |
3447 | unpack("C*",pack("L",0x12345678))), "\n"; | |
3448 | ||
d99ad34e | 3449 | The byteorder on the platform where Perl was built is also available |
726ea183 | 3450 | via L<Config>: |
ef54e1a4 JH |
3451 | |
3452 | use Config; | |
3453 | print $Config{byteorder}, "\n"; | |
3454 | ||
d99ad34e JH |
3455 | Byteorders C<'1234'> and C<'12345678'> are little-endian, C<'4321'> |
3456 | and C<'87654321'> are big-endian. | |
719a3cf5 | 3457 | |
951ba7fe | 3458 | If you want portable packed integers use the formats C<n>, C<N>, |
82e239e7 | 3459 | C<v>, and C<V>, their byte endianness and size are known. |
851646ae | 3460 | See also L<perlport>. |
ef54e1a4 JH |
3461 | |
3462 | =item * | |
3463 | ||
5a929a98 VU |
3464 | Real numbers (floats and doubles) are in the native machine format only; |
3465 | due to the multiplicity of floating formats around, and the lack of a | |
3466 | standard "network" representation, no facility for interchange has been | |
3467 | made. This means that packed floating point data written on one machine | |
3468 | may not be readable on another - even if both use IEEE floating point | |
3469 | arithmetic (as the endian-ness of the memory representation is not part | |
851646ae | 3470 | of the IEEE spec). See also L<perlport>. |
5a929a98 VU |
3471 | |
3472 | Note that Perl uses doubles internally for all numeric calculation, and | |
3473 | converting from double into float and thence back to double again will | |
3474 | lose precision (i.e., C<unpack("f", pack("f", $foo)>) will not in general | |
19799a22 | 3475 | equal $foo). |
5a929a98 | 3476 | |
851646ae JH |
3477 | =item * |
3478 | ||
036b4402 GS |
3479 | If the pattern begins with a C<U>, the resulting string will be treated |
3480 | as Unicode-encoded. You can force UTF8 encoding on in a string with an | |
3481 | initial C<U0>, and the bytes that follow will be interpreted as Unicode | |
3482 | characters. If you don't want this to happen, you can begin your pattern | |
3483 | with C<C0> (or anything else) to force Perl not to UTF8 encode your | |
3484 | string, and then follow this with a C<U*> somewhere in your pattern. | |
3485 | ||
3486 | =item * | |
3487 | ||
851646ae | 3488 | You must yourself do any alignment or padding by inserting for example |
9ccd05c0 JH |
3489 | enough C<'x'>es while packing. There is no way to pack() and unpack() |
3490 | could know where the bytes are going to or coming from. Therefore | |
3491 | C<pack> (and C<unpack>) handle their output and input as flat | |
3492 | sequences of bytes. | |
851646ae | 3493 | |
17f4a12d IZ |
3494 | =item * |
3495 | ||
18529408 IZ |
3496 | A ()-group is a sub-TEMPLATE enclosed in parentheses. A group may |
3497 | take a repeat count, both as postfix, and via the C</> template | |
3498 | character. | |
3499 | ||
3500 | =item * | |
3501 | ||
62f95557 IZ |
3502 | C<x> and C<X> accept C<!> modifier. In this case they act as |
3503 | alignment commands: they jump forward/back to the closest position | |
3504 | aligned at a multiple of C<count> bytes. For example, to pack() or | |
3505 | unpack() C's C<struct {char c; double d; char cc[2]}> one may need to | |
3506 | use the template C<C x![d] d C[2]>; this assumes that doubles must be | |
3507 | aligned on the double's size. | |
666f95b9 | 3508 | |
62f95557 IZ |
3509 | For alignment commands C<count> of 0 is equivalent to C<count> of 1; |
3510 | both result in no-ops. | |
666f95b9 | 3511 | |
62f95557 IZ |
3512 | =item * |
3513 | ||
17f4a12d IZ |
3514 | A comment in a TEMPLATE starts with C<#> and goes to the end of line. |
3515 | ||
2b6c5635 GS |
3516 | =item * |
3517 | ||
3518 | If TEMPLATE requires more arguments to pack() than actually given, pack() | |
3519 | assumes additional C<""> arguments. If TEMPLATE requires less arguments | |
3520 | to pack() than actually given, extra arguments are ignored. | |
3521 | ||
5a929a98 | 3522 | =back |
a0d0e21e LW |
3523 | |
3524 | Examples: | |
3525 | ||
a0ed51b3 | 3526 | $foo = pack("CCCC",65,66,67,68); |
a0d0e21e | 3527 | # foo eq "ABCD" |
a0ed51b3 | 3528 | $foo = pack("C4",65,66,67,68); |
a0d0e21e | 3529 | # same thing |
a0ed51b3 LW |
3530 | $foo = pack("U4",0x24b6,0x24b7,0x24b8,0x24b9); |
3531 | # same thing with Unicode circled letters | |
a0d0e21e LW |
3532 | |
3533 | $foo = pack("ccxxcc",65,66,67,68); | |
3534 | # foo eq "AB\0\0CD" | |
3535 | ||
9ccd05c0 JH |
3536 | # note: the above examples featuring "C" and "c" are true |
3537 | # only on ASCII and ASCII-derived systems such as ISO Latin 1 | |
3538 | # and UTF-8. In EBCDIC the first example would be | |
3539 | # $foo = pack("CCCC",193,194,195,196); | |
3540 | ||
a0d0e21e LW |
3541 | $foo = pack("s2",1,2); |
3542 | # "\1\0\2\0" on little-endian | |
3543 | # "\0\1\0\2" on big-endian | |
3544 | ||
3545 | $foo = pack("a4","abcd","x","y","z"); | |
3546 | # "abcd" | |
3547 | ||
3548 | $foo = pack("aaaa","abcd","x","y","z"); | |
3549 | # "axyz" | |
3550 | ||
3551 | $foo = pack("a14","abcdefg"); | |
3552 | # "abcdefg\0\0\0\0\0\0\0" | |
3553 | ||
3554 | $foo = pack("i9pl", gmtime); | |
3555 | # a real struct tm (on my system anyway) | |
3556 | ||
5a929a98 VU |
3557 | $utmp_template = "Z8 Z8 Z16 L"; |
3558 | $utmp = pack($utmp_template, @utmp1); | |
3559 | # a struct utmp (BSDish) | |
3560 | ||
3561 | @utmp2 = unpack($utmp_template, $utmp); | |
3562 | # "@utmp1" eq "@utmp2" | |
3563 | ||
a0d0e21e LW |
3564 | sub bintodec { |
3565 | unpack("N", pack("B32", substr("0" x 32 . shift, -32))); | |
3566 | } | |
3567 | ||
851646ae JH |
3568 | $foo = pack('sx2l', 12, 34); |
3569 | # short 12, two zero bytes padding, long 34 | |
3570 | $bar = pack('s@4l', 12, 34); | |
3571 | # short 12, zero fill to position 4, long 34 | |
3572 | # $foo eq $bar | |
3573 | ||
5a929a98 | 3574 | The same template may generally also be used in unpack(). |
a0d0e21e | 3575 | |
cb1a09d0 AD |
3576 | =item package NAMESPACE |
3577 | ||
b76cc8ba | 3578 | =item package |
d6217f1e | 3579 | |
cb1a09d0 | 3580 | Declares the compilation unit as being in the given namespace. The scope |
2b5ab1e7 | 3581 | of the package declaration is from the declaration itself through the end |
19799a22 | 3582 | of the enclosing block, file, or eval (the same as the C<my> operator). |
2b5ab1e7 TC |
3583 | All further unqualified dynamic identifiers will be in this namespace. |
3584 | A package statement affects only dynamic variables--including those | |
19799a22 GS |
3585 | you've used C<local> on--but I<not> lexical variables, which are created |
3586 | with C<my>. Typically it would be the first declaration in a file to | |
2b5ab1e7 TC |
3587 | be included by the C<require> or C<use> operator. You can switch into a |
3588 | package in more than one place; it merely influences which symbol table | |
3589 | is used by the compiler for the rest of that block. You can refer to | |
3590 | variables and filehandles in other packages by prefixing the identifier | |
3591 | with the package name and a double colon: C<$Package::Variable>. | |
3592 | If the package name is null, the C<main> package as assumed. That is, | |
3593 | C<$::sail> is equivalent to C<$main::sail> (as well as to C<$main'sail>, | |
3594 | still seen in older code). | |
cb1a09d0 | 3595 | |
5a964f20 | 3596 | If NAMESPACE is omitted, then there is no current package, and all |
f2c0fa37 RH |
3597 | identifiers must be fully qualified or lexicals. However, you are |
3598 | strongly advised not to make use of this feature. Its use can cause | |
3599 | unexpected behaviour, even crashing some versions of Perl. It is | |
3600 | deprecated, and will be removed from a future release. | |
5a964f20 | 3601 | |
cb1a09d0 AD |
3602 | See L<perlmod/"Packages"> for more information about packages, modules, |
3603 | and classes. See L<perlsub> for other scoping issues. | |
3604 | ||
a0d0e21e LW |
3605 | =item pipe READHANDLE,WRITEHANDLE |
3606 | ||
3607 | Opens a pair of connected pipes like the corresponding system call. | |
3608 | Note that if you set up a loop of piped processes, deadlock can occur | |
3609 | unless you are very careful. In addition, note that Perl's pipes use | |
9124316e | 3610 | IO buffering, so you may need to set C<$|> to flush your WRITEHANDLE |
a0d0e21e LW |
3611 | after each command, depending on the application. |
3612 | ||
7e1af8bc | 3613 | See L<IPC::Open2>, L<IPC::Open3>, and L<perlipc/"Bidirectional Communication"> |
4633a7c4 LW |
3614 | for examples of such things. |
3615 | ||
4771b018 GS |
3616 | On systems that support a close-on-exec flag on files, the flag will be set |
3617 | for the newly opened file descriptors as determined by the value of $^F. | |
3618 | See L<perlvar/$^F>. | |
3619 | ||
a0d0e21e LW |
3620 | =item pop ARRAY |
3621 | ||
54310121 | 3622 | =item pop |
28757baa | 3623 | |
a0d0e21e | 3624 | Pops and returns the last value of the array, shortening the array by |
19799a22 | 3625 | one element. Has an effect similar to |
a0d0e21e | 3626 | |
19799a22 | 3627 | $ARRAY[$#ARRAY--] |
a0d0e21e | 3628 | |
19799a22 GS |
3629 | If there are no elements in the array, returns the undefined value |
3630 | (although this may happen at other times as well). If ARRAY is | |
3631 | omitted, pops the C<@ARGV> array in the main program, and the C<@_> | |
3632 | array in subroutines, just like C<shift>. | |
a0d0e21e LW |
3633 | |
3634 | =item pos SCALAR | |
3635 | ||
54310121 | 3636 | =item pos |
bbce6d69 | 3637 | |
4633a7c4 | 3638 | Returns the offset of where the last C<m//g> search left off for the variable |
d6217f1e | 3639 | in question (C<$_> is used when the variable is not specified). May be |
44a8e56a | 3640 | modified to change that offset. Such modification will also influence |
3641 | the C<\G> zero-width assertion in regular expressions. See L<perlre> and | |
3642 | L<perlop>. | |
a0d0e21e LW |
3643 | |
3644 | =item print FILEHANDLE LIST | |
3645 | ||
3646 | =item print LIST | |
3647 | ||
3648 | =item print | |
3649 | ||
19799a22 GS |
3650 | Prints a string or a list of strings. Returns true if successful. |
3651 | FILEHANDLE may be a scalar variable name, in which case the variable | |
3652 | contains the name of or a reference to the filehandle, thus introducing | |
3653 | one level of indirection. (NOTE: If FILEHANDLE is a variable and | |
3654 | the next token is a term, it may be misinterpreted as an operator | |
2b5ab1e7 | 3655 | unless you interpose a C<+> or put parentheses around the arguments.) |
19799a22 GS |
3656 | If FILEHANDLE is omitted, prints by default to standard output (or |
3657 | to the last selected output channel--see L</select>). If LIST is | |
3658 | also omitted, prints C<$_> to the currently selected output channel. | |
3659 | To set the default output channel to something other than STDOUT | |
3660 | use the select operation. The current value of C<$,> (if any) is | |
3661 | printed between each LIST item. The current value of C<$\> (if | |
3662 | any) is printed after the entire LIST has been printed. Because | |
3663 | print takes a LIST, anything in the LIST is evaluated in list | |
3664 | context, and any subroutine that you call will have one or more of | |
3665 | its expressions evaluated in list context. Also be careful not to | |
3666 | follow the print keyword with a left parenthesis unless you want | |
3667 | the corresponding right parenthesis to terminate the arguments to | |
3668 | the print--interpose a C<+> or put parentheses around all the | |
3669 | arguments. | |
a0d0e21e | 3670 | |
4633a7c4 | 3671 | Note that if you're storing FILEHANDLES in an array or other expression, |
da0045b7 | 3672 | you will have to use a block returning its value instead: |
4633a7c4 LW |
3673 | |
3674 | print { $files[$i] } "stuff\n"; | |
3675 | print { $OK ? STDOUT : STDERR } "stuff\n"; | |
3676 | ||
5f05dabc | 3677 | =item printf FILEHANDLE FORMAT, LIST |
a0d0e21e | 3678 | |
5f05dabc | 3679 | =item printf FORMAT, LIST |
a0d0e21e | 3680 | |
7660c0ab | 3681 | Equivalent to C<print FILEHANDLE sprintf(FORMAT, LIST)>, except that C<$\> |
a3cb178b | 3682 | (the output record separator) is not appended. The first argument |
f39758bf GJ |
3683 | of the list will be interpreted as the C<printf> format. See C<sprintf> |
3684 | for an explanation of the format argument. If C<use locale> is in effect, | |
3685 | the character used for the decimal point in formatted real numbers is | |
3686 | affected by the LC_NUMERIC locale. See L<perllocale>. | |
a0d0e21e | 3687 | |
19799a22 GS |
3688 | Don't fall into the trap of using a C<printf> when a simple |
3689 | C<print> would do. The C<print> is more efficient and less | |
28757baa | 3690 | error prone. |
3691 | ||
da0045b7 | 3692 | =item prototype FUNCTION |
3693 | ||
3694 | Returns the prototype of a function as a string (or C<undef> if the | |
5f05dabc | 3695 | function has no prototype). FUNCTION is a reference to, or the name of, |
3696 | the function whose prototype you want to retrieve. | |
da0045b7 | 3697 | |
2b5ab1e7 TC |
3698 | If FUNCTION is a string starting with C<CORE::>, the rest is taken as a |
3699 | name for Perl builtin. If the builtin is not I<overridable> (such as | |
ab4f32c2 | 3700 | C<qw//>) or its arguments cannot be expressed by a prototype (such as |
19799a22 | 3701 | C<system>) returns C<undef> because the builtin does not really behave |
2b5ab1e7 TC |
3702 | like a Perl function. Otherwise, the string describing the equivalent |
3703 | prototype is returned. | |
b6c543e3 | 3704 | |
a0d0e21e LW |
3705 | =item push ARRAY,LIST |
3706 | ||
3707 | Treats ARRAY as a stack, and pushes the values of LIST | |
3708 | onto the end of ARRAY. The length of ARRAY increases by the length of | |
3709 | LIST. Has the same effect as | |
3710 | ||
3711 | for $value (LIST) { | |
3712 | $ARRAY[++$#ARRAY] = $value; | |
3713 | } | |
3714 | ||
3715 | but is more efficient. Returns the new number of elements in the array. | |
3716 | ||
3717 | =item q/STRING/ | |
3718 | ||
3719 | =item qq/STRING/ | |
3720 | ||
8782bef2 GB |
3721 | =item qr/STRING/ |
3722 | ||
945c54fd | 3723 | =item qx/STRING/ |
a0d0e21e LW |
3724 | |
3725 | =item qw/STRING/ | |
3726 | ||
4b6a7270 | 3727 | Generalized quotes. See L<perlop/"Regexp Quote-Like Operators">. |
a0d0e21e LW |
3728 | |
3729 | =item quotemeta EXPR | |
3730 | ||
54310121 | 3731 | =item quotemeta |
bbce6d69 | 3732 | |
36bbe248 | 3733 | Returns the value of EXPR with all non-"word" |
a034a98d DD |
3734 | characters backslashed. (That is, all characters not matching |
3735 | C</[A-Za-z_0-9]/> will be preceded by a backslash in the | |
3736 | returned string, regardless of any locale settings.) | |
3737 | This is the internal function implementing | |
7660c0ab | 3738 | the C<\Q> escape in double-quoted strings. |
a0d0e21e | 3739 | |
7660c0ab | 3740 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 3741 | |
a0d0e21e LW |
3742 | =item rand EXPR |
3743 | ||
3744 | =item rand | |
3745 | ||
7660c0ab | 3746 | Returns a random fractional number greater than or equal to C<0> and less |
3e3baf6d | 3747 | than the value of EXPR. (EXPR should be positive.) If EXPR is |
351f3254 NC |
3748 | omitted, the value C<1> is used. Currently EXPR with the value C<0> is |
3749 | also special-cased as C<1> - this has not been documented before perl 5.8.0 | |
3750 | and is subject to change in future versions of perl. Automatically calls | |
3751 | C<srand> unless C<srand> has already been called. See also C<srand>. | |
a0d0e21e | 3752 | |
6063ba18 WM |
3753 | Apply C<int()> to the value returned by C<rand()> if you want random |
3754 | integers instead of random fractional numbers. For example, | |
3755 | ||
3756 | int(rand(10)) | |
3757 | ||
3758 | returns a random integer between C<0> and C<9>, inclusive. | |
3759 | ||
2f9daede | 3760 | (Note: If your rand function consistently returns numbers that are too |
a0d0e21e | 3761 | large or too small, then your version of Perl was probably compiled |
2f9daede | 3762 | with the wrong number of RANDBITS.) |
a0d0e21e LW |
3763 | |
3764 | =item read FILEHANDLE,SCALAR,LENGTH,OFFSET | |
3765 | ||
3766 | =item read FILEHANDLE,SCALAR,LENGTH | |
3767 | ||
9124316e JH |
3768 | Attempts to read LENGTH I<characters> of data into variable SCALAR |
3769 | from the specified FILEHANDLE. Returns the number of characters | |
3770 | actually read, C<0> at end of file, or undef if there was an error. | |
3771 | SCALAR will be grown or shrunk to the length actually read. If SCALAR | |
3772 | needs growing, the new bytes will be zero bytes. An OFFSET may be | |
3773 | specified to place the read data into some other place in SCALAR than | |
3774 | the beginning. The call is actually implemented in terms of either | |
3775 | Perl's or system's fread() call. To get a true read(2) system call, | |
3776 | see C<sysread>. | |
3777 | ||
3778 | Note the I<characters>: depending on the status of the filehandle, | |
3779 | either (8-bit) bytes or characters are read. By default all | |
3780 | filehandles operate on bytes, but for example if the filehandle has | |
fae2c0fb | 3781 | been opened with the C<:utf8> I/O layer (see L</open>, and the C<open> |
9124316e | 3782 | pragma, L<open>), the I/O will operate on characters, not bytes. |
a0d0e21e LW |
3783 | |
3784 | =item readdir DIRHANDLE | |
3785 | ||
19799a22 | 3786 | Returns the next directory entry for a directory opened by C<opendir>. |
5a964f20 | 3787 | If used in list context, returns all the rest of the entries in the |
a0d0e21e | 3788 | directory. If there are no more entries, returns an undefined value in |
5a964f20 | 3789 | scalar context or a null list in list context. |
a0d0e21e | 3790 | |
19799a22 | 3791 | If you're planning to filetest the return values out of a C<readdir>, you'd |
5f05dabc | 3792 | better prepend the directory in question. Otherwise, because we didn't |
19799a22 | 3793 | C<chdir> there, it would have been testing the wrong file. |
cb1a09d0 AD |
3794 | |
3795 | opendir(DIR, $some_dir) || die "can't opendir $some_dir: $!"; | |
3796 | @dots = grep { /^\./ && -f "$some_dir/$_" } readdir(DIR); | |
3797 | closedir DIR; | |
3798 | ||
84902520 TB |
3799 | =item readline EXPR |
3800 | ||
d4679214 JH |
3801 | Reads from the filehandle whose typeglob is contained in EXPR. In scalar |
3802 | context, each call reads and returns the next line, until end-of-file is | |
3803 | reached, whereupon the subsequent call returns undef. In list context, | |
3804 | reads until end-of-file is reached and returns a list of lines. Note that | |
3805 | the notion of "line" used here is however you may have defined it | |
3806 | with C<$/> or C<$INPUT_RECORD_SEPARATOR>). See L<perlvar/"$/">. | |
fbad3eb5 | 3807 | |
2b5ab1e7 | 3808 | When C<$/> is set to C<undef>, when readline() is in scalar |
449bc448 GS |
3809 | context (i.e. file slurp mode), and when an empty file is read, it |
3810 | returns C<''> the first time, followed by C<undef> subsequently. | |
fbad3eb5 | 3811 | |
61eff3bc JH |
3812 | This is the internal function implementing the C<< <EXPR> >> |
3813 | operator, but you can use it directly. The C<< <EXPR> >> | |
84902520 TB |
3814 | operator is discussed in more detail in L<perlop/"I/O Operators">. |
3815 | ||
5a964f20 TC |
3816 | $line = <STDIN>; |
3817 | $line = readline(*STDIN); # same thing | |
3818 | ||
a0d0e21e LW |
3819 | =item readlink EXPR |
3820 | ||
54310121 | 3821 | =item readlink |
bbce6d69 | 3822 | |
a0d0e21e LW |
3823 | Returns the value of a symbolic link, if symbolic links are |
3824 | implemented. If not, gives a fatal error. If there is some system | |
184e9718 | 3825 | error, returns the undefined value and sets C<$!> (errno). If EXPR is |
7660c0ab | 3826 | omitted, uses C<$_>. |
a0d0e21e | 3827 | |
84902520 TB |
3828 | =item readpipe EXPR |
3829 | ||
5a964f20 | 3830 | EXPR is executed as a system command. |
84902520 TB |
3831 | The collected standard output of the command is returned. |
3832 | In scalar context, it comes back as a single (potentially | |
3833 | multi-line) string. In list context, returns a list of lines | |
7660c0ab | 3834 | (however you've defined lines with C<$/> or C<$INPUT_RECORD_SEPARATOR>). |
84902520 TB |
3835 | This is the internal function implementing the C<qx/EXPR/> |
3836 | operator, but you can use it directly. The C<qx/EXPR/> | |
3837 | operator is discussed in more detail in L<perlop/"I/O Operators">. | |
3838 | ||
399388f4 | 3839 | =item recv SOCKET,SCALAR,LENGTH,FLAGS |
a0d0e21e | 3840 | |
9124316e JH |
3841 | Receives a message on a socket. Attempts to receive LENGTH characters |
3842 | of data into variable SCALAR from the specified SOCKET filehandle. | |
3843 | SCALAR will be grown or shrunk to the length actually read. Takes the | |
3844 | same flags as the system call of the same name. Returns the address | |
3845 | of the sender if SOCKET's protocol supports this; returns an empty | |
3846 | string otherwise. If there's an error, returns the undefined value. | |
3847 | This call is actually implemented in terms of recvfrom(2) system call. | |
3848 | See L<perlipc/"UDP: Message Passing"> for examples. | |
3849 | ||
3850 | Note the I<characters>: depending on the status of the socket, either | |
3851 | (8-bit) bytes or characters are received. By default all sockets | |
3852 | operate on bytes, but for example if the socket has been changed using | |
fae2c0fb | 3853 | binmode() to operate with the C<:utf8> I/O layer (see the C<open> |
9124316e | 3854 | pragma, L<open>), the I/O will operate on characters, not bytes. |
a0d0e21e LW |
3855 | |
3856 | =item redo LABEL | |
3857 | ||
3858 | =item redo | |
3859 | ||
3860 | The C<redo> command restarts the loop block without evaluating the | |
98293880 | 3861 | conditional again. The C<continue> block, if any, is not executed. If |
a0d0e21e LW |
3862 | the LABEL is omitted, the command refers to the innermost enclosing |
3863 | loop. This command is normally used by programs that want to lie to | |
3864 | themselves about what was just input: | |
3865 | ||
3866 | # a simpleminded Pascal comment stripper | |
3867 | # (warning: assumes no { or } in strings) | |
4633a7c4 | 3868 | LINE: while (<STDIN>) { |
a0d0e21e LW |
3869 | while (s|({.*}.*){.*}|$1 |) {} |
3870 | s|{.*}| |; | |
3871 | if (s|{.*| |) { | |
3872 | $front = $_; | |
3873 | while (<STDIN>) { | |
3874 | if (/}/) { # end of comment? | |
5a964f20 | 3875 | s|^|$front\{|; |
4633a7c4 | 3876 | redo LINE; |
a0d0e21e LW |
3877 | } |
3878 | } | |
3879 | } | |
3880 | print; | |
3881 | } | |
3882 | ||
4968c1e4 | 3883 | C<redo> cannot be used to retry a block which returns a value such as |
2b5ab1e7 TC |
3884 | C<eval {}>, C<sub {}> or C<do {}>, and should not be used to exit |
3885 | a grep() or map() operation. | |
4968c1e4 | 3886 | |
6c1372ed GS |
3887 | Note that a block by itself is semantically identical to a loop |
3888 | that executes once. Thus C<redo> inside such a block will effectively | |
3889 | turn it into a looping construct. | |
3890 | ||
98293880 | 3891 | See also L</continue> for an illustration of how C<last>, C<next>, and |
1d2dff63 GS |
3892 | C<redo> work. |
3893 | ||
a0d0e21e LW |
3894 | =item ref EXPR |
3895 | ||
54310121 | 3896 | =item ref |
bbce6d69 | 3897 | |
19799a22 | 3898 | Returns a true value if EXPR is a reference, false otherwise. If EXPR |
7660c0ab | 3899 | is not specified, C<$_> will be used. The value returned depends on the |
bbce6d69 | 3900 | type of thing the reference is a reference to. |
a0d0e21e LW |
3901 | Builtin types include: |
3902 | ||
a0d0e21e LW |
3903 | SCALAR |
3904 | ARRAY | |
3905 | HASH | |
3906 | CODE | |
19799a22 | 3907 | REF |
a0d0e21e | 3908 | GLOB |
19799a22 | 3909 | LVALUE |
a0d0e21e | 3910 | |
54310121 | 3911 | If the referenced object has been blessed into a package, then that package |
19799a22 | 3912 | name is returned instead. You can think of C<ref> as a C<typeof> operator. |
a0d0e21e LW |
3913 | |
3914 | if (ref($r) eq "HASH") { | |
aa689395 | 3915 | print "r is a reference to a hash.\n"; |
54310121 | 3916 | } |
2b5ab1e7 | 3917 | unless (ref($r)) { |
a0d0e21e | 3918 | print "r is not a reference at all.\n"; |
54310121 | 3919 | } |
2b5ab1e7 TC |
3920 | if (UNIVERSAL::isa($r, "HASH")) { # for subclassing |
3921 | print "r is a reference to something that isa hash.\n"; | |
b76cc8ba | 3922 | } |
a0d0e21e LW |
3923 | |
3924 | See also L<perlref>. | |
3925 | ||
3926 | =item rename OLDNAME,NEWNAME | |
3927 | ||
19799a22 GS |
3928 | Changes the name of a file; an existing file NEWNAME will be |
3929 | clobbered. Returns true for success, false otherwise. | |
3930 | ||
2b5ab1e7 TC |
3931 | Behavior of this function varies wildly depending on your system |
3932 | implementation. For example, it will usually not work across file system | |
3933 | boundaries, even though the system I<mv> command sometimes compensates | |
3934 | for this. Other restrictions include whether it works on directories, | |
3935 | open files, or pre-existing files. Check L<perlport> and either the | |
3936 | rename(2) manpage or equivalent system documentation for details. | |
a0d0e21e | 3937 | |
16070b82 GS |
3938 | =item require VERSION |
3939 | ||
a0d0e21e LW |
3940 | =item require EXPR |
3941 | ||
3942 | =item require | |
3943 | ||
3b825e41 RK |
3944 | Demands a version of Perl specified by VERSION, or demands some semantics |
3945 | specified by EXPR or by C<$_> if EXPR is not supplied. | |
44dcb63b | 3946 | |
3b825e41 RK |
3947 | VERSION may be either a numeric argument such as 5.006, which will be |
3948 | compared to C<$]>, or a literal of the form v5.6.1, which will be compared | |
3949 | to C<$^V> (aka $PERL_VERSION). A fatal error is produced at run time if | |
3950 | VERSION is greater than the version of the current Perl interpreter. | |
3951 | Compare with L</use>, which can do a similar check at compile time. | |
3952 | ||
3953 | Specifying VERSION as a literal of the form v5.6.1 should generally be | |
3954 | avoided, because it leads to misleading error messages under earlier | |
3955 | versions of Perl which do not support this syntax. The equivalent numeric | |
3956 | version should be used instead. | |
44dcb63b | 3957 | |
dd629d5b GS |
3958 | require v5.6.1; # run time version check |
3959 | require 5.6.1; # ditto | |
3b825e41 | 3960 | require 5.006_001; # ditto; preferred for backwards compatibility |
a0d0e21e LW |
3961 | |
3962 | Otherwise, demands that a library file be included if it hasn't already | |
3963 | been included. The file is included via the do-FILE mechanism, which is | |
19799a22 | 3964 | essentially just a variety of C<eval>. Has semantics similar to the following |
a0d0e21e LW |
3965 | subroutine: |
3966 | ||
3967 | sub require { | |
5a964f20 | 3968 | my($filename) = @_; |
a0d0e21e | 3969 | return 1 if $INC{$filename}; |
5a964f20 | 3970 | my($realfilename,$result); |
a0d0e21e LW |
3971 | ITER: { |
3972 | foreach $prefix (@INC) { | |
3973 | $realfilename = "$prefix/$filename"; | |
3974 | if (-f $realfilename) { | |
f784dfa3 | 3975 | $INC{$filename} = $realfilename; |
a0d0e21e LW |
3976 | $result = do $realfilename; |
3977 | last ITER; | |
3978 | } | |
3979 | } | |
3980 | die "Can't find $filename in \@INC"; | |
3981 | } | |
f784dfa3 | 3982 | delete $INC{$filename} if $@ || !$result; |
a0d0e21e LW |
3983 | die $@ if $@; |
3984 | die "$filename did not return true value" unless $result; | |
5a964f20 | 3985 | return $result; |
a0d0e21e LW |
3986 | } |
3987 | ||
3988 | Note that the file will not be included twice under the same specified | |
19799a22 | 3989 | name. The file must return true as the last statement to indicate |
a0d0e21e | 3990 | successful execution of any initialization code, so it's customary to |
19799a22 GS |
3991 | end such a file with C<1;> unless you're sure it'll return true |
3992 | otherwise. But it's better just to put the C<1;>, in case you add more | |
a0d0e21e LW |
3993 | statements. |
3994 | ||
54310121 | 3995 | If EXPR is a bareword, the require assumes a "F<.pm>" extension and |
da0045b7 | 3996 | replaces "F<::>" with "F</>" in the filename for you, |
54310121 | 3997 | to make it easy to load standard modules. This form of loading of |
a0d0e21e LW |
3998 | modules does not risk altering your namespace. |
3999 | ||
ee580363 GS |
4000 | In other words, if you try this: |
4001 | ||
b76cc8ba | 4002 | require Foo::Bar; # a splendid bareword |
ee580363 | 4003 | |
b76cc8ba | 4004 | The require function will actually look for the "F<Foo/Bar.pm>" file in the |
7660c0ab | 4005 | directories specified in the C<@INC> array. |
ee580363 | 4006 | |
5a964f20 | 4007 | But if you try this: |
ee580363 GS |
4008 | |
4009 | $class = 'Foo::Bar'; | |
f86cebdf | 4010 | require $class; # $class is not a bareword |
5a964f20 | 4011 | #or |
f86cebdf | 4012 | require "Foo::Bar"; # not a bareword because of the "" |
ee580363 | 4013 | |
b76cc8ba | 4014 | The require function will look for the "F<Foo::Bar>" file in the @INC array and |
19799a22 | 4015 | will complain about not finding "F<Foo::Bar>" there. In this case you can do: |
ee580363 GS |
4016 | |
4017 | eval "require $class"; | |
4018 | ||
d54b56d5 RGS |
4019 | You can also insert hooks into the import facility, by putting directly |
4020 | Perl code into the @INC array. There are three forms of hooks: subroutine | |
4021 | references, array references and blessed objects. | |
4022 | ||
4023 | Subroutine references are the simplest case. When the inclusion system | |
4024 | walks through @INC and encounters a subroutine, this subroutine gets | |
4025 | called with two parameters, the first being a reference to itself, and the | |
4026 | second the name of the file to be included (e.g. "F<Foo/Bar.pm>"). The | |
4027 | subroutine should return C<undef> or a filehandle, from which the file to | |
4028 | include will be read. If C<undef> is returned, C<require> will look at | |
4029 | the remaining elements of @INC. | |
4030 | ||
4031 | If the hook is an array reference, its first element must be a subroutine | |
4032 | reference. This subroutine is called as above, but the first parameter is | |
4033 | the array reference. This enables to pass indirectly some arguments to | |
4034 | the subroutine. | |
4035 | ||
4036 | In other words, you can write: | |
4037 | ||
4038 | push @INC, \&my_sub; | |
4039 | sub my_sub { | |
4040 | my ($coderef, $filename) = @_; # $coderef is \&my_sub | |
4041 | ... | |
4042 | } | |
4043 | ||
4044 | or: | |
4045 | ||
4046 | push @INC, [ \&my_sub, $x, $y, ... ]; | |
4047 | sub my_sub { | |
4048 | my ($arrayref, $filename) = @_; | |
4049 | # Retrieve $x, $y, ... | |
4050 | my @parameters = @$arrayref[1..$#$arrayref]; | |
4051 | ... | |
4052 | } | |
4053 | ||
4054 | If the hook is an object, it must provide an INC method, that will be | |
4055 | called as above, the first parameter being the object itself. (Note that | |
4056 | you must fully qualify the sub's name, as it is always forced into package | |
4057 | C<main>.) Here is a typical code layout: | |
4058 | ||
4059 | # In Foo.pm | |
4060 | package Foo; | |
4061 | sub new { ... } | |
4062 | sub Foo::INC { | |
4063 | my ($self, $filename) = @_; | |
4064 | ... | |
4065 | } | |
4066 | ||
4067 | # In the main program | |
4068 | push @INC, new Foo(...); | |
4069 | ||
9ae8cd5b RGS |
4070 | Note that these hooks are also permitted to set the %INC entry |
4071 | corresponding to the files they have loaded. See L<perlvar/%INC>. | |
4072 | ||
ee580363 | 4073 | For a yet-more-powerful import facility, see L</use> and L<perlmod>. |
a0d0e21e LW |
4074 | |
4075 | =item reset EXPR | |
4076 | ||
4077 | =item reset | |
4078 | ||
4079 | Generally used in a C<continue> block at the end of a loop to clear | |
7660c0ab | 4080 | variables and reset C<??> searches so that they work again. The |
a0d0e21e LW |
4081 | expression is interpreted as a list of single characters (hyphens |
4082 | allowed for ranges). All variables and arrays beginning with one of | |
4083 | those letters are reset to their pristine state. If the expression is | |
7660c0ab | 4084 | omitted, one-match searches (C<?pattern?>) are reset to match again. Resets |
5f05dabc | 4085 | only variables or searches in the current package. Always returns |
a0d0e21e LW |
4086 | 1. Examples: |
4087 | ||
4088 | reset 'X'; # reset all X variables | |
4089 | reset 'a-z'; # reset lower case variables | |
2b5ab1e7 | 4090 | reset; # just reset ?one-time? searches |
a0d0e21e | 4091 | |
7660c0ab | 4092 | Resetting C<"A-Z"> is not recommended because you'll wipe out your |
2b5ab1e7 TC |
4093 | C<@ARGV> and C<@INC> arrays and your C<%ENV> hash. Resets only package |
4094 | variables--lexical variables are unaffected, but they clean themselves | |
4095 | up on scope exit anyway, so you'll probably want to use them instead. | |
4096 | See L</my>. | |
a0d0e21e | 4097 | |
54310121 | 4098 | =item return EXPR |
4099 | ||
4100 | =item return | |
4101 | ||
b76cc8ba | 4102 | Returns from a subroutine, C<eval>, or C<do FILE> with the value |
5a964f20 | 4103 | given in EXPR. Evaluation of EXPR may be in list, scalar, or void |
54310121 | 4104 | context, depending on how the return value will be used, and the context |
19799a22 | 4105 | may vary from one execution to the next (see C<wantarray>). If no EXPR |
2b5ab1e7 TC |
4106 | is given, returns an empty list in list context, the undefined value in |
4107 | scalar context, and (of course) nothing at all in a void context. | |
a0d0e21e | 4108 | |
d1be9408 | 4109 | (Note that in the absence of an explicit C<return>, a subroutine, eval, |
2b5ab1e7 TC |
4110 | or do FILE will automatically return the value of the last expression |
4111 | evaluated.) | |
a0d0e21e LW |
4112 | |
4113 | =item reverse LIST | |
4114 | ||
5a964f20 TC |
4115 | In list context, returns a list value consisting of the elements |
4116 | of LIST in the opposite order. In scalar context, concatenates the | |
2b5ab1e7 | 4117 | elements of LIST and returns a string value with all characters |
a0ed51b3 | 4118 | in the opposite order. |
4633a7c4 | 4119 | |
2f9daede | 4120 | print reverse <>; # line tac, last line first |
4633a7c4 | 4121 | |
2f9daede | 4122 | undef $/; # for efficiency of <> |
a0ed51b3 | 4123 | print scalar reverse <>; # character tac, last line tsrif |
2f9daede TP |
4124 | |
4125 | This operator is also handy for inverting a hash, although there are some | |
4126 | caveats. If a value is duplicated in the original hash, only one of those | |
4127 | can be represented as a key in the inverted hash. Also, this has to | |
4128 | unwind one hash and build a whole new one, which may take some time | |
2b5ab1e7 | 4129 | on a large hash, such as from a DBM file. |
2f9daede TP |
4130 | |
4131 | %by_name = reverse %by_address; # Invert the hash | |
a0d0e21e LW |
4132 | |
4133 | =item rewinddir DIRHANDLE | |
4134 | ||
4135 | Sets the current position to the beginning of the directory for the | |
19799a22 | 4136 | C<readdir> routine on DIRHANDLE. |
a0d0e21e LW |
4137 | |
4138 | =item rindex STR,SUBSTR,POSITION | |
4139 | ||
4140 | =item rindex STR,SUBSTR | |
4141 | ||
2b5ab1e7 | 4142 | Works just like index() except that it returns the position of the LAST |
a0d0e21e LW |
4143 | occurrence of SUBSTR in STR. If POSITION is specified, returns the |
4144 | last occurrence at or before that position. | |
4145 | ||
4146 | =item rmdir FILENAME | |
4147 | ||
54310121 | 4148 | =item rmdir |
bbce6d69 | 4149 | |
5a964f20 | 4150 | Deletes the directory specified by FILENAME if that directory is empty. If it |
19799a22 | 4151 | succeeds it returns true, otherwise it returns false and sets C<$!> (errno). If |
7660c0ab | 4152 | FILENAME is omitted, uses C<$_>. |
a0d0e21e LW |
4153 | |
4154 | =item s/// | |
4155 | ||
4156 | The substitution operator. See L<perlop>. | |
4157 | ||
4158 | =item scalar EXPR | |
4159 | ||
5a964f20 | 4160 | Forces EXPR to be interpreted in scalar context and returns the value |
54310121 | 4161 | of EXPR. |
cb1a09d0 AD |
4162 | |
4163 | @counts = ( scalar @a, scalar @b, scalar @c ); | |
4164 | ||
54310121 | 4165 | There is no equivalent operator to force an expression to |
2b5ab1e7 | 4166 | be interpolated in list context because in practice, this is never |
cb1a09d0 AD |
4167 | needed. If you really wanted to do so, however, you could use |
4168 | the construction C<@{[ (some expression) ]}>, but usually a simple | |
4169 | C<(some expression)> suffices. | |
a0d0e21e | 4170 | |
19799a22 | 4171 | Because C<scalar> is unary operator, if you accidentally use for EXPR a |
2b5ab1e7 TC |
4172 | parenthesized list, this behaves as a scalar comma expression, evaluating |
4173 | all but the last element in void context and returning the final element | |
4174 | evaluated in scalar context. This is seldom what you want. | |
62c18ce2 GS |
4175 | |
4176 | The following single statement: | |
4177 | ||
4178 | print uc(scalar(&foo,$bar)),$baz; | |
4179 | ||
4180 | is the moral equivalent of these two: | |
4181 | ||
4182 | &foo; | |
4183 | print(uc($bar),$baz); | |
4184 | ||
4185 | See L<perlop> for more details on unary operators and the comma operator. | |
4186 | ||
a0d0e21e LW |
4187 | =item seek FILEHANDLE,POSITION,WHENCE |
4188 | ||
19799a22 | 4189 | Sets FILEHANDLE's position, just like the C<fseek> call of C<stdio>. |
8903cb82 | 4190 | FILEHANDLE may be an expression whose value gives the name of the |
9124316e JH |
4191 | filehandle. The values for WHENCE are C<0> to set the new position |
4192 | I<in bytes> to POSITION, C<1> to set it to the current position plus | |
4193 | POSITION, and C<2> to set it to EOF plus POSITION (typically | |
4194 | negative). For WHENCE you may use the constants C<SEEK_SET>, | |
4195 | C<SEEK_CUR>, and C<SEEK_END> (start of the file, current position, end | |
4196 | of the file) from the Fcntl module. Returns C<1> upon success, C<0> | |
4197 | otherwise. | |
4198 | ||
4199 | Note the I<in bytes>: even if the filehandle has been set to | |
4200 | operate on characters (for example by using the C<:utf8> open | |
fae2c0fb | 4201 | layer), tell() will return byte offsets, not character offsets |
9124316e | 4202 | (because implementing that would render seek() and tell() rather slow). |
8903cb82 | 4203 | |
19799a22 GS |
4204 | If you want to position file for C<sysread> or C<syswrite>, don't use |
4205 | C<seek>--buffering makes its effect on the file's system position | |
4206 | unpredictable and non-portable. Use C<sysseek> instead. | |
a0d0e21e | 4207 | |
2b5ab1e7 TC |
4208 | Due to the rules and rigors of ANSI C, on some systems you have to do a |
4209 | seek whenever you switch between reading and writing. Amongst other | |
4210 | things, this may have the effect of calling stdio's clearerr(3). | |
4211 | A WHENCE of C<1> (C<SEEK_CUR>) is useful for not moving the file position: | |
cb1a09d0 AD |
4212 | |
4213 | seek(TEST,0,1); | |
4214 | ||
4215 | This is also useful for applications emulating C<tail -f>. Once you hit | |
4216 | EOF on your read, and then sleep for a while, you might have to stick in a | |
19799a22 | 4217 | seek() to reset things. The C<seek> doesn't change the current position, |
8903cb82 | 4218 | but it I<does> clear the end-of-file condition on the handle, so that the |
61eff3bc | 4219 | next C<< <FILE> >> makes Perl try again to read something. We hope. |
cb1a09d0 | 4220 | |
9124316e JH |
4221 | If that doesn't work (some IO implementations are particularly |
4222 | cantankerous), then you may need something more like this: | |
cb1a09d0 AD |
4223 | |
4224 | for (;;) { | |
f86cebdf GS |
4225 | for ($curpos = tell(FILE); $_ = <FILE>; |
4226 | $curpos = tell(FILE)) { | |
cb1a09d0 AD |
4227 | # search for some stuff and put it into files |
4228 | } | |
4229 | sleep($for_a_while); | |
4230 | seek(FILE, $curpos, 0); | |
4231 | } | |
4232 | ||
a0d0e21e LW |
4233 | =item seekdir DIRHANDLE,POS |
4234 | ||
19799a22 GS |
4235 | Sets the current position for the C<readdir> routine on DIRHANDLE. POS |
4236 | must be a value returned by C<telldir>. Has the same caveats about | |
a0d0e21e LW |
4237 | possible directory compaction as the corresponding system library |
4238 | routine. | |
4239 | ||
4240 | =item select FILEHANDLE | |
4241 | ||
4242 | =item select | |
4243 | ||
4244 | Returns the currently selected filehandle. Sets the current default | |
4245 | filehandle for output, if FILEHANDLE is supplied. This has two | |
19799a22 | 4246 | effects: first, a C<write> or a C<print> without a filehandle will |
a0d0e21e LW |
4247 | default to this FILEHANDLE. Second, references to variables related to |
4248 | output will refer to this output channel. For example, if you have to | |
4249 | set the top of form format for more than one output channel, you might | |
4250 | do the following: | |
4251 | ||
4252 | select(REPORT1); | |
4253 | $^ = 'report1_top'; | |
4254 | select(REPORT2); | |
4255 | $^ = 'report2_top'; | |
4256 | ||
4257 | FILEHANDLE may be an expression whose value gives the name of the | |
4258 | actual filehandle. Thus: | |
4259 | ||
4260 | $oldfh = select(STDERR); $| = 1; select($oldfh); | |
4261 | ||
4633a7c4 LW |
4262 | Some programmers may prefer to think of filehandles as objects with |
4263 | methods, preferring to write the last example as: | |
a0d0e21e | 4264 | |
28757baa | 4265 | use IO::Handle; |
a0d0e21e LW |
4266 | STDERR->autoflush(1); |
4267 | ||
4268 | =item select RBITS,WBITS,EBITS,TIMEOUT | |
4269 | ||
f86cebdf | 4270 | This calls the select(2) system call with the bit masks specified, which |
19799a22 | 4271 | can be constructed using C<fileno> and C<vec>, along these lines: |
a0d0e21e LW |
4272 | |
4273 | $rin = $win = $ein = ''; | |
4274 | vec($rin,fileno(STDIN),1) = 1; | |
4275 | vec($win,fileno(STDOUT),1) = 1; | |
4276 | $ein = $rin | $win; | |
4277 | ||
4278 | If you want to select on many filehandles you might wish to write a | |
4279 | subroutine: | |
4280 | ||
4281 | sub fhbits { | |
5a964f20 TC |
4282 | my(@fhlist) = split(' ',$_[0]); |
4283 | my($bits); | |
a0d0e21e LW |
4284 | for (@fhlist) { |
4285 | vec($bits,fileno($_),1) = 1; | |
4286 | } | |
4287 | $bits; | |
4288 | } | |
4633a7c4 | 4289 | $rin = fhbits('STDIN TTY SOCK'); |
a0d0e21e LW |
4290 | |
4291 | The usual idiom is: | |
4292 | ||
4293 | ($nfound,$timeleft) = | |
4294 | select($rout=$rin, $wout=$win, $eout=$ein, $timeout); | |
4295 | ||
54310121 | 4296 | or to block until something becomes ready just do this |
a0d0e21e LW |
4297 | |
4298 | $nfound = select($rout=$rin, $wout=$win, $eout=$ein, undef); | |
4299 | ||
19799a22 GS |
4300 | Most systems do not bother to return anything useful in $timeleft, so |
4301 | calling select() in scalar context just returns $nfound. | |
c07a80fd | 4302 | |
5f05dabc | 4303 | Any of the bit masks can also be undef. The timeout, if specified, is |
a0d0e21e | 4304 | in seconds, which may be fractional. Note: not all implementations are |
be119125 | 4305 | capable of returning the $timeleft. If not, they always return |
19799a22 | 4306 | $timeleft equal to the supplied $timeout. |
a0d0e21e | 4307 | |
ff68c719 | 4308 | You can effect a sleep of 250 milliseconds this way: |
a0d0e21e LW |
4309 | |
4310 | select(undef, undef, undef, 0.25); | |
4311 | ||
b09fc1d8 JH |
4312 | Note that whether C<select> gets restarted after signals (say, SIGALRM) |
4313 | is implementation-dependent. | |
4314 | ||
19799a22 | 4315 | B<WARNING>: One should not attempt to mix buffered I/O (like C<read> |
61eff3bc | 4316 | or <FH>) with C<select>, except as permitted by POSIX, and even |
19799a22 | 4317 | then only on POSIX systems. You have to use C<sysread> instead. |
a0d0e21e LW |
4318 | |
4319 | =item semctl ID,SEMNUM,CMD,ARG | |
4320 | ||
19799a22 | 4321 | Calls the System V IPC function C<semctl>. You'll probably have to say |
0ade1984 JH |
4322 | |
4323 | use IPC::SysV; | |
4324 | ||
4325 | first to get the correct constant definitions. If CMD is IPC_STAT or | |
4326 | GETALL, then ARG must be a variable which will hold the returned | |
e4038a1f MS |
4327 | semid_ds structure or semaphore value array. Returns like C<ioctl>: |
4328 | the undefined value for error, "C<0 but true>" for zero, or the actual | |
4329 | return value otherwise. The ARG must consist of a vector of native | |
106325ad | 4330 | short integers, which may be created with C<pack("s!",(0)x$nsem)>. |
4755096e GS |
4331 | See also L<perlipc/"SysV IPC">, C<IPC::SysV>, C<IPC::Semaphore> |
4332 | documentation. | |
a0d0e21e LW |
4333 | |
4334 | =item semget KEY,NSEMS,FLAGS | |
4335 | ||
4336 | Calls the System V IPC function semget. Returns the semaphore id, or | |
4755096e GS |
4337 | the undefined value if there is an error. See also |
4338 | L<perlipc/"SysV IPC">, C<IPC::SysV>, C<IPC::SysV::Semaphore> | |
4339 | documentation. | |
a0d0e21e LW |
4340 | |
4341 | =item semop KEY,OPSTRING | |
4342 | ||
4343 | Calls the System V IPC function semop to perform semaphore operations | |
5354997a | 4344 | such as signalling and waiting. OPSTRING must be a packed array of |
a0d0e21e | 4345 | semop structures. Each semop structure can be generated with |
f878ba33 | 4346 | C<pack("s!3", $semnum, $semop, $semflag)>. The number of semaphore |
19799a22 GS |
4347 | operations is implied by the length of OPSTRING. Returns true if |
4348 | successful, or false if there is an error. As an example, the | |
4349 | following code waits on semaphore $semnum of semaphore id $semid: | |
a0d0e21e | 4350 | |
f878ba33 | 4351 | $semop = pack("s!3", $semnum, -1, 0); |
a0d0e21e LW |
4352 | die "Semaphore trouble: $!\n" unless semop($semid, $semop); |
4353 | ||
4755096e GS |
4354 | To signal the semaphore, replace C<-1> with C<1>. See also |
4355 | L<perlipc/"SysV IPC">, C<IPC::SysV>, and C<IPC::SysV::Semaphore> | |
4356 | documentation. | |
a0d0e21e LW |
4357 | |
4358 | =item send SOCKET,MSG,FLAGS,TO | |
4359 | ||
4360 | =item send SOCKET,MSG,FLAGS | |
4361 | ||
fe854a6f | 4362 | Sends a message on a socket. Attempts to send the scalar MSG to the |
9124316e JH |
4363 | SOCKET filehandle. Takes the same flags as the system call of the |
4364 | same name. On unconnected sockets you must specify a destination to | |
4365 | send TO, in which case it does a C C<sendto>. Returns the number of | |
4366 | characters sent, or the undefined value if there is an error. The C | |
4367 | system call sendmsg(2) is currently unimplemented. See | |
4368 | L<perlipc/"UDP: Message Passing"> for examples. | |
4369 | ||
4370 | Note the I<characters>: depending on the status of the socket, either | |
4371 | (8-bit) bytes or characters are sent. By default all sockets operate | |
4372 | on bytes, but for example if the socket has been changed using | |
fae2c0fb | 4373 | binmode() to operate with the C<:utf8> I/O layer (see L</open>, or |
9124316e JH |
4374 | the C<open> pragma, L<open>), the I/O will operate on characters, not |
4375 | bytes. | |
a0d0e21e LW |
4376 | |
4377 | =item setpgrp PID,PGRP | |
4378 | ||
7660c0ab | 4379 | Sets the current process group for the specified PID, C<0> for the current |
a0d0e21e | 4380 | process. Will produce a fatal error if used on a machine that doesn't |
81777298 GS |
4381 | implement POSIX setpgid(2) or BSD setpgrp(2). If the arguments are omitted, |
4382 | it defaults to C<0,0>. Note that the BSD 4.2 version of C<setpgrp> does not | |
4383 | accept any arguments, so only C<setpgrp(0,0)> is portable. See also | |
4384 | C<POSIX::setsid()>. | |
a0d0e21e LW |
4385 | |
4386 | =item setpriority WHICH,WHO,PRIORITY | |
4387 | ||
4388 | Sets the current priority for a process, a process group, or a user. | |
f86cebdf GS |
4389 | (See setpriority(2).) Will produce a fatal error if used on a machine |
4390 | that doesn't implement setpriority(2). | |
a0d0e21e LW |
4391 | |
4392 | =item setsockopt SOCKET,LEVEL,OPTNAME,OPTVAL | |
4393 | ||
4394 | Sets the socket option requested. Returns undefined if there is an | |
7660c0ab | 4395 | error. OPTVAL may be specified as C<undef> if you don't want to pass an |
a0d0e21e LW |
4396 | argument. |
4397 | ||
4398 | =item shift ARRAY | |
4399 | ||
4400 | =item shift | |
4401 | ||
4402 | Shifts the first value of the array off and returns it, shortening the | |
4403 | array by 1 and moving everything down. If there are no elements in the | |
4404 | array, returns the undefined value. If ARRAY is omitted, shifts the | |
7660c0ab A |
4405 | C<@_> array within the lexical scope of subroutines and formats, and the |
4406 | C<@ARGV> array at file scopes or within the lexical scopes established by | |
7d30b5c4 | 4407 | the C<eval ''>, C<BEGIN {}>, C<INIT {}>, C<CHECK {}>, and C<END {}> |
4f25aa18 GS |
4408 | constructs. |
4409 | ||
a1b2c429 | 4410 | See also C<unshift>, C<push>, and C<pop>. C<shift> and C<unshift> do the |
19799a22 | 4411 | same thing to the left end of an array that C<pop> and C<push> do to the |
977336f5 | 4412 | right end. |
a0d0e21e LW |
4413 | |
4414 | =item shmctl ID,CMD,ARG | |
4415 | ||
0ade1984 JH |
4416 | Calls the System V IPC function shmctl. You'll probably have to say |
4417 | ||
4418 | use IPC::SysV; | |
4419 | ||
7660c0ab A |
4420 | first to get the correct constant definitions. If CMD is C<IPC_STAT>, |
4421 | then ARG must be a variable which will hold the returned C<shmid_ds> | |
4422 | structure. Returns like ioctl: the undefined value for error, "C<0> but | |
0ade1984 | 4423 | true" for zero, or the actual return value otherwise. |
4755096e | 4424 | See also L<perlipc/"SysV IPC"> and C<IPC::SysV> documentation. |
a0d0e21e LW |
4425 | |
4426 | =item shmget KEY,SIZE,FLAGS | |
4427 | ||
4428 | Calls the System V IPC function shmget. Returns the shared memory | |
4429 | segment id, or the undefined value if there is an error. | |
4755096e | 4430 | See also L<perlipc/"SysV IPC"> and C<IPC::SysV> documentation. |
a0d0e21e LW |
4431 | |
4432 | =item shmread ID,VAR,POS,SIZE | |
4433 | ||
4434 | =item shmwrite ID,STRING,POS,SIZE | |
4435 | ||
4436 | Reads or writes the System V shared memory segment ID starting at | |
4437 | position POS for size SIZE by attaching to it, copying in/out, and | |
5a964f20 | 4438 | detaching from it. When reading, VAR must be a variable that will |
a0d0e21e LW |
4439 | hold the data read. When writing, if STRING is too long, only SIZE |
4440 | bytes are used; if STRING is too short, nulls are written to fill out | |
19799a22 | 4441 | SIZE bytes. Return true if successful, or false if there is an error. |
4755096e GS |
4442 | shmread() taints the variable. See also L<perlipc/"SysV IPC">, |
4443 | C<IPC::SysV> documentation, and the C<IPC::Shareable> module from CPAN. | |
a0d0e21e LW |
4444 | |
4445 | =item shutdown SOCKET,HOW | |
4446 | ||
4447 | Shuts down a socket connection in the manner indicated by HOW, which | |
4448 | has the same interpretation as in the system call of the same name. | |
4449 | ||
f86cebdf GS |
4450 | shutdown(SOCKET, 0); # I/we have stopped reading data |
4451 | shutdown(SOCKET, 1); # I/we have stopped writing data | |
4452 | shutdown(SOCKET, 2); # I/we have stopped using this socket | |
5a964f20 TC |
4453 | |
4454 | This is useful with sockets when you want to tell the other | |
4455 | side you're done writing but not done reading, or vice versa. | |
b76cc8ba | 4456 | It's also a more insistent form of close because it also |
19799a22 | 4457 | disables the file descriptor in any forked copies in other |
5a964f20 TC |
4458 | processes. |
4459 | ||
a0d0e21e LW |
4460 | =item sin EXPR |
4461 | ||
54310121 | 4462 | =item sin |
bbce6d69 | 4463 | |
a0d0e21e | 4464 | Returns the sine of EXPR (expressed in radians). If EXPR is omitted, |
7660c0ab | 4465 | returns sine of C<$_>. |
a0d0e21e | 4466 | |
ca6e1c26 | 4467 | For the inverse sine operation, you may use the C<Math::Trig::asin> |
28757baa | 4468 | function, or use this relation: |
4469 | ||
4470 | sub asin { atan2($_[0], sqrt(1 - $_[0] * $_[0])) } | |
4471 | ||
a0d0e21e LW |
4472 | =item sleep EXPR |
4473 | ||
4474 | =item sleep | |
4475 | ||
4476 | Causes the script to sleep for EXPR seconds, or forever if no EXPR. | |
7660c0ab | 4477 | May be interrupted if the process receives a signal such as C<SIGALRM>. |
1d3434b8 | 4478 | Returns the number of seconds actually slept. You probably cannot |
19799a22 GS |
4479 | mix C<alarm> and C<sleep> calls, because C<sleep> is often implemented |
4480 | using C<alarm>. | |
a0d0e21e LW |
4481 | |
4482 | On some older systems, it may sleep up to a full second less than what | |
4483 | you requested, depending on how it counts seconds. Most modern systems | |
5a964f20 TC |
4484 | always sleep the full amount. They may appear to sleep longer than that, |
4485 | however, because your process might not be scheduled right away in a | |
4486 | busy multitasking system. | |
a0d0e21e | 4487 | |
cb1a09d0 | 4488 | For delays of finer granularity than one second, you may use Perl's |
68f8bed4 | 4489 | C<syscall> interface to access setitimer(2) if your system supports |
83df6a1d JH |
4490 | it, or else see L</select> above. The Time::HiRes module (from CPAN, |
4491 | and starting from Perl 5.8 part of the standard distribution) may also | |
4492 | help. | |
cb1a09d0 | 4493 | |
b6e2112e | 4494 | See also the POSIX module's C<pause> function. |
5f05dabc | 4495 | |
a0d0e21e LW |
4496 | =item socket SOCKET,DOMAIN,TYPE,PROTOCOL |
4497 | ||
4498 | Opens a socket of the specified kind and attaches it to filehandle | |
19799a22 GS |
4499 | SOCKET. DOMAIN, TYPE, and PROTOCOL are specified the same as for |
4500 | the system call of the same name. You should C<use Socket> first | |
4501 | to get the proper definitions imported. See the examples in | |
4502 | L<perlipc/"Sockets: Client/Server Communication">. | |
a0d0e21e | 4503 | |
8d2a6795 GS |
4504 | On systems that support a close-on-exec flag on files, the flag will |
4505 | be set for the newly opened file descriptor, as determined by the | |
4506 | value of $^F. See L<perlvar/$^F>. | |
4507 | ||
a0d0e21e LW |
4508 | =item socketpair SOCKET1,SOCKET2,DOMAIN,TYPE,PROTOCOL |
4509 | ||
4510 | Creates an unnamed pair of sockets in the specified domain, of the | |
5f05dabc | 4511 | specified type. DOMAIN, TYPE, and PROTOCOL are specified the same as |
a0d0e21e | 4512 | for the system call of the same name. If unimplemented, yields a fatal |
19799a22 | 4513 | error. Returns true if successful. |
a0d0e21e | 4514 | |
8d2a6795 GS |
4515 | On systems that support a close-on-exec flag on files, the flag will |
4516 | be set for the newly opened file descriptors, as determined by the value | |
4517 | of $^F. See L<perlvar/$^F>. | |
4518 | ||
19799a22 | 4519 | Some systems defined C<pipe> in terms of C<socketpair>, in which a call |
5a964f20 TC |
4520 | to C<pipe(Rdr, Wtr)> is essentially: |
4521 | ||
4522 | use Socket; | |
4523 | socketpair(Rdr, Wtr, AF_UNIX, SOCK_STREAM, PF_UNSPEC); | |
4524 | shutdown(Rdr, 1); # no more writing for reader | |
4525 | shutdown(Wtr, 0); # no more reading for writer | |
4526 | ||
02fc2eee NC |
4527 | See L<perlipc> for an example of socketpair use. Perl 5.8 and later will |
4528 | emulate socketpair using IP sockets to localhost if your system implements | |
4529 | sockets but not socketpair. | |
5a964f20 | 4530 | |
a0d0e21e LW |
4531 | =item sort SUBNAME LIST |
4532 | ||
4533 | =item sort BLOCK LIST | |
4534 | ||
4535 | =item sort LIST | |
4536 | ||
41d39f30 | 4537 | In list context, this sorts the LIST and returns the sorted list value. |
9fdc1d08 | 4538 | In scalar context, the behaviour of C<sort()> is undefined. |
41d39f30 A |
4539 | |
4540 | If SUBNAME or BLOCK is omitted, C<sort>s in standard string comparison | |
4541 | order. If SUBNAME is specified, it gives the name of a subroutine | |
4542 | that returns an integer less than, equal to, or greater than C<0>, | |
4543 | depending on how the elements of the list are to be ordered. (The C<< | |
4544 | <=> >> and C<cmp> operators are extremely useful in such routines.) | |
4545 | SUBNAME may be a scalar variable name (unsubscripted), in which case | |
4546 | the value provides the name of (or a reference to) the actual | |
4547 | subroutine to use. In place of a SUBNAME, you can provide a BLOCK as | |
4548 | an anonymous, in-line sort subroutine. | |
a0d0e21e | 4549 | |
43481408 | 4550 | If the subroutine's prototype is C<($$)>, the elements to be compared |
f9a36357 GS |
4551 | are passed by reference in C<@_>, as for a normal subroutine. This is |
4552 | slower than unprototyped subroutines, where the elements to be | |
4553 | compared are passed into the subroutine | |
43481408 GS |
4554 | as the package global variables $a and $b (see example below). Note that |
4555 | in the latter case, it is usually counter-productive to declare $a and | |
4556 | $b as lexicals. | |
4557 | ||
4558 | In either case, the subroutine may not be recursive. The values to be | |
4559 | compared are always passed by reference, so don't modify them. | |
a0d0e21e | 4560 | |
0a753a76 | 4561 | You also cannot exit out of the sort block or subroutine using any of the |
19799a22 | 4562 | loop control operators described in L<perlsyn> or with C<goto>. |
0a753a76 | 4563 | |
a034a98d DD |
4564 | When C<use locale> is in effect, C<sort LIST> sorts LIST according to the |
4565 | current collation locale. See L<perllocale>. | |
4566 | ||
58c7fc7c JH |
4567 | Perl 5.6 and earlier used a quicksort algorithm to implement sort. |
4568 | That algorithm was not stable, and I<could> go quadratic. (A I<stable> sort | |
4569 | preserves the input order of elements that compare equal. Although | |
4570 | quicksort's run time is O(NlogN) when averaged over all arrays of | |
4571 | length N, the time can be O(N**2), I<quadratic> behavior, for some | |
4572 | inputs.) In 5.7, the quicksort implementation was replaced with | |
4573 | a stable mergesort algorithm whose worst case behavior is O(NlogN). | |
4574 | But benchmarks indicated that for some inputs, on some platforms, | |
4575 | the original quicksort was faster. 5.8 has a sort pragma for | |
4576 | limited control of the sort. Its rather blunt control of the | |
4577 | underlying algorithm may not persist into future perls, but the | |
4578 | ability to characterize the input or output in implementation | |
6a30edae | 4579 | independent ways quite probably will. See L<sort>. |
c16425f1 | 4580 | |
a0d0e21e LW |
4581 | Examples: |
4582 | ||
4583 | # sort lexically | |
4584 | @articles = sort @files; | |
4585 | ||
4586 | # same thing, but with explicit sort routine | |
4587 | @articles = sort {$a cmp $b} @files; | |
4588 | ||
cb1a09d0 | 4589 | # now case-insensitively |
54310121 | 4590 | @articles = sort {uc($a) cmp uc($b)} @files; |
cb1a09d0 | 4591 | |
a0d0e21e LW |
4592 | # same thing in reversed order |
4593 | @articles = sort {$b cmp $a} @files; | |
4594 | ||
4595 | # sort numerically ascending | |
4596 | @articles = sort {$a <=> $b} @files; | |
4597 | ||
4598 | # sort numerically descending | |
4599 | @articles = sort {$b <=> $a} @files; | |
4600 | ||
19799a22 GS |
4601 | # this sorts the %age hash by value instead of key |
4602 | # using an in-line function | |
4603 | @eldest = sort { $age{$b} <=> $age{$a} } keys %age; | |
4604 | ||
a0d0e21e LW |
4605 | # sort using explicit subroutine name |
4606 | sub byage { | |
2f9daede | 4607 | $age{$a} <=> $age{$b}; # presuming numeric |
a0d0e21e LW |
4608 | } |
4609 | @sortedclass = sort byage @class; | |
4610 | ||
19799a22 GS |
4611 | sub backwards { $b cmp $a } |
4612 | @harry = qw(dog cat x Cain Abel); | |
4613 | @george = qw(gone chased yz Punished Axed); | |
a0d0e21e LW |
4614 | print sort @harry; |
4615 | # prints AbelCaincatdogx | |
4616 | print sort backwards @harry; | |
4617 | # prints xdogcatCainAbel | |
4618 | print sort @george, 'to', @harry; | |
4619 | # prints AbelAxedCainPunishedcatchaseddoggonetoxyz | |
4620 | ||
54310121 | 4621 | # inefficiently sort by descending numeric compare using |
4622 | # the first integer after the first = sign, or the | |
cb1a09d0 AD |
4623 | # whole record case-insensitively otherwise |
4624 | ||
4625 | @new = sort { | |
4626 | ($b =~ /=(\d+)/)[0] <=> ($a =~ /=(\d+)/)[0] | |
4627 | || | |
4628 | uc($a) cmp uc($b) | |
4629 | } @old; | |
4630 | ||
4631 | # same thing, but much more efficiently; | |
4632 | # we'll build auxiliary indices instead | |
4633 | # for speed | |
4634 | @nums = @caps = (); | |
54310121 | 4635 | for (@old) { |
cb1a09d0 AD |
4636 | push @nums, /=(\d+)/; |
4637 | push @caps, uc($_); | |
54310121 | 4638 | } |
cb1a09d0 AD |
4639 | |
4640 | @new = @old[ sort { | |
4641 | $nums[$b] <=> $nums[$a] | |
4642 | || | |
4643 | $caps[$a] cmp $caps[$b] | |
4644 | } 0..$#old | |
4645 | ]; | |
4646 | ||
19799a22 | 4647 | # same thing, but without any temps |
cb1a09d0 | 4648 | @new = map { $_->[0] } |
19799a22 GS |
4649 | sort { $b->[1] <=> $a->[1] |
4650 | || | |
4651 | $a->[2] cmp $b->[2] | |
4652 | } map { [$_, /=(\d+)/, uc($_)] } @old; | |
61eff3bc | 4653 | |
43481408 GS |
4654 | # using a prototype allows you to use any comparison subroutine |
4655 | # as a sort subroutine (including other package's subroutines) | |
4656 | package other; | |
4657 | sub backwards ($$) { $_[1] cmp $_[0]; } # $a and $b are not set here | |
4658 | ||
4659 | package main; | |
4660 | @new = sort other::backwards @old; | |
cb1a09d0 | 4661 | |
58c7fc7c JH |
4662 | # guarantee stability, regardless of algorithm |
4663 | use sort 'stable'; | |
4664 | @new = sort { substr($a, 3, 5) cmp substr($b, 3, 5) } @old; | |
4665 | ||
268e9d79 JL |
4666 | # force use of mergesort (not portable outside Perl 5.8) |
4667 | use sort '_mergesort'; # note discouraging _ | |
58c7fc7c | 4668 | @new = sort { substr($a, 3, 5) cmp substr($b, 3, 5) } @old; |
58c7fc7c | 4669 | |
19799a22 GS |
4670 | If you're using strict, you I<must not> declare $a |
4671 | and $b as lexicals. They are package globals. That means | |
47223a36 | 4672 | if you're in the C<main> package and type |
13a2d996 | 4673 | |
47223a36 | 4674 | @articles = sort {$b <=> $a} @files; |
13a2d996 | 4675 | |
47223a36 JH |
4676 | then C<$a> and C<$b> are C<$main::a> and C<$main::b> (or C<$::a> and C<$::b>), |
4677 | but if you're in the C<FooPack> package, it's the same as typing | |
cb1a09d0 AD |
4678 | |
4679 | @articles = sort {$FooPack::b <=> $FooPack::a} @files; | |
4680 | ||
55497cff | 4681 | The comparison function is required to behave. If it returns |
7660c0ab A |
4682 | inconsistent results (sometimes saying C<$x[1]> is less than C<$x[2]> and |
4683 | sometimes saying the opposite, for example) the results are not | |
4684 | well-defined. | |
55497cff | 4685 | |
a0d0e21e LW |
4686 | =item splice ARRAY,OFFSET,LENGTH,LIST |
4687 | ||
4688 | =item splice ARRAY,OFFSET,LENGTH | |
4689 | ||
4690 | =item splice ARRAY,OFFSET | |
4691 | ||
453f9044 GS |
4692 | =item splice ARRAY |
4693 | ||
a0d0e21e | 4694 | Removes the elements designated by OFFSET and LENGTH from an array, and |
5a964f20 TC |
4695 | replaces them with the elements of LIST, if any. In list context, |
4696 | returns the elements removed from the array. In scalar context, | |
43051805 | 4697 | returns the last element removed, or C<undef> if no elements are |
48cdf507 | 4698 | removed. The array grows or shrinks as necessary. |
19799a22 | 4699 | If OFFSET is negative then it starts that far from the end of the array. |
48cdf507 | 4700 | If LENGTH is omitted, removes everything from OFFSET onward. |
d0920e03 MJD |
4701 | If LENGTH is negative, removes the elements from OFFSET onward |
4702 | except for -LENGTH elements at the end of the array. | |
8cbc2e3b JH |
4703 | If both OFFSET and LENGTH are omitted, removes everything. If OFFSET is |
4704 | past the end of the array, perl issues a warning, and splices at the | |
4705 | end of the array. | |
453f9044 | 4706 | |
48cdf507 | 4707 | The following equivalences hold (assuming C<$[ == 0>): |
a0d0e21e | 4708 | |
48cdf507 | 4709 | push(@a,$x,$y) splice(@a,@a,0,$x,$y) |
a0d0e21e LW |
4710 | pop(@a) splice(@a,-1) |
4711 | shift(@a) splice(@a,0,1) | |
4712 | unshift(@a,$x,$y) splice(@a,0,0,$x,$y) | |
5a964f20 | 4713 | $a[$x] = $y splice(@a,$x,1,$y) |
a0d0e21e LW |
4714 | |
4715 | Example, assuming array lengths are passed before arrays: | |
4716 | ||
4717 | sub aeq { # compare two list values | |
5a964f20 TC |
4718 | my(@a) = splice(@_,0,shift); |
4719 | my(@b) = splice(@_,0,shift); | |
a0d0e21e LW |
4720 | return 0 unless @a == @b; # same len? |
4721 | while (@a) { | |
4722 | return 0 if pop(@a) ne pop(@b); | |
4723 | } | |
4724 | return 1; | |
4725 | } | |
4726 | if (&aeq($len,@foo[1..$len],0+@bar,@bar)) { ... } | |
4727 | ||
4728 | =item split /PATTERN/,EXPR,LIMIT | |
4729 | ||
4730 | =item split /PATTERN/,EXPR | |
4731 | ||
4732 | =item split /PATTERN/ | |
4733 | ||
4734 | =item split | |
4735 | ||
19799a22 | 4736 | Splits a string into a list of strings and returns that list. By default, |
5a964f20 | 4737 | empty leading fields are preserved, and empty trailing ones are deleted. |
a0d0e21e | 4738 | |
46836f5c GS |
4739 | In scalar context, returns the number of fields found and splits into |
4740 | the C<@_> array. Use of split in scalar context is deprecated, however, | |
4741 | because it clobbers your subroutine arguments. | |
a0d0e21e | 4742 | |
7660c0ab | 4743 | If EXPR is omitted, splits the C<$_> string. If PATTERN is also omitted, |
4633a7c4 LW |
4744 | splits on whitespace (after skipping any leading whitespace). Anything |
4745 | matching PATTERN is taken to be a delimiter separating the fields. (Note | |
fb73857a | 4746 | that the delimiter may be longer than one character.) |
4747 | ||
836e0ee7 | 4748 | If LIMIT is specified and positive, it represents the maximum number |
e833de1e BS |
4749 | of fields the EXPR will be split into, though the actual number of |
4750 | fields returned depends on the number of times PATTERN matches within | |
4751 | EXPR. If LIMIT is unspecified or zero, trailing null fields are | |
4752 | stripped (which potential users of C<pop> would do well to remember). | |
4753 | If LIMIT is negative, it is treated as if an arbitrarily large LIMIT | |
4754 | had been specified. Note that splitting an EXPR that evaluates to the | |
4755 | empty string always returns the empty list, regardless of the LIMIT | |
4756 | specified. | |
a0d0e21e LW |
4757 | |
4758 | A pattern matching the null string (not to be confused with | |
748a9306 | 4759 | a null pattern C<//>, which is just one member of the set of patterns |
a0d0e21e LW |
4760 | matching a null string) will split the value of EXPR into separate |
4761 | characters at each point it matches that way. For example: | |
4762 | ||
4763 | print join(':', split(/ */, 'hi there')); | |
4764 | ||
4765 | produces the output 'h:i:t:h:e:r:e'. | |
4766 | ||
6de67870 JP |
4767 | Using the empty pattern C<//> specifically matches the null string, and is |
4768 | not be confused with the use of C<//> to mean "the last successful pattern | |
4769 | match". | |
4770 | ||
91542540 | 4771 | Empty leading (or trailing) fields are produced when there are positive width |
0156e0fd RB |
4772 | matches at the beginning (or end) of the string; a zero-width match at the |
4773 | beginning (or end) of the string does not produce an empty field. For | |
4774 | example: | |
4775 | ||
4776 | print join(':', split(/(?=\w)/, 'hi there!')); | |
4777 | ||
4778 | produces the output 'h:i :t:h:e:r:e!'. | |
4779 | ||
5f05dabc | 4780 | The LIMIT parameter can be used to split a line partially |
a0d0e21e LW |
4781 | |
4782 | ($login, $passwd, $remainder) = split(/:/, $_, 3); | |
4783 | ||
4784 | When assigning to a list, if LIMIT is omitted, Perl supplies a LIMIT | |
4785 | one larger than the number of variables in the list, to avoid | |
4786 | unnecessary work. For the list above LIMIT would have been 4 by | |
4787 | default. In time critical applications it behooves you not to split | |
4788 | into more fields than you really need. | |
4789 | ||
19799a22 | 4790 | If the PATTERN contains parentheses, additional list elements are |
a0d0e21e LW |
4791 | created from each matching substring in the delimiter. |
4792 | ||
da0045b7 | 4793 | split(/([,-])/, "1-10,20", 3); |
a0d0e21e LW |
4794 | |
4795 | produces the list value | |
4796 | ||
4797 | (1, '-', 10, ',', 20) | |
4798 | ||
19799a22 | 4799 | If you had the entire header of a normal Unix email message in $header, |
4633a7c4 LW |
4800 | you could split it up into fields and their values this way: |
4801 | ||
4802 | $header =~ s/\n\s+/ /g; # fix continuation lines | |
fb73857a | 4803 | %hdrs = (UNIX_FROM => split /^(\S*?):\s*/m, $header); |
4633a7c4 | 4804 | |
a0d0e21e LW |
4805 | The pattern C</PATTERN/> may be replaced with an expression to specify |
4806 | patterns that vary at runtime. (To do runtime compilation only once, | |
748a9306 LW |
4807 | use C</$variable/o>.) |
4808 | ||
4809 | As a special case, specifying a PATTERN of space (C<' '>) will split on | |
19799a22 | 4810 | white space just as C<split> with no arguments does. Thus, C<split(' ')> can |
748a9306 LW |
4811 | be used to emulate B<awk>'s default behavior, whereas C<split(/ /)> |
4812 | will give you as many null initial fields as there are leading spaces. | |
19799a22 GS |
4813 | A C<split> on C</\s+/> is like a C<split(' ')> except that any leading |
4814 | whitespace produces a null first field. A C<split> with no arguments | |
748a9306 | 4815 | really does a C<split(' ', $_)> internally. |
a0d0e21e | 4816 | |
cc50a203 | 4817 | A PATTERN of C</^/> is treated as if it were C</^/m>, since it isn't |
1ec94568 MG |
4818 | much use otherwise. |
4819 | ||
a0d0e21e LW |
4820 | Example: |
4821 | ||
5a964f20 TC |
4822 | open(PASSWD, '/etc/passwd'); |
4823 | while (<PASSWD>) { | |
5b3eff12 MS |
4824 | chomp; |
4825 | ($login, $passwd, $uid, $gid, | |
f86cebdf | 4826 | $gcos, $home, $shell) = split(/:/); |
5a964f20 | 4827 | #... |
a0d0e21e LW |
4828 | } |
4829 | ||
6de67870 JP |
4830 | As with regular pattern matching, any capturing parentheses that are not |
4831 | matched in a C<split()> will be set to C<undef> when returned: | |
4832 | ||
4833 | @fields = split /(A)|B/, "1A2B3"; | |
4834 | # @fields is (1, 'A', 2, undef, 3) | |
a0d0e21e | 4835 | |
5f05dabc | 4836 | =item sprintf FORMAT, LIST |
a0d0e21e | 4837 | |
6662521e GS |
4838 | Returns a string formatted by the usual C<printf> conventions of the C |
4839 | library function C<sprintf>. See below for more details | |
4840 | and see L<sprintf(3)> or L<printf(3)> on your system for an explanation of | |
4841 | the general principles. | |
4842 | ||
4843 | For example: | |
4844 | ||
4845 | # Format number with up to 8 leading zeroes | |
4846 | $result = sprintf("%08d", $number); | |
4847 | ||
4848 | # Round number to 3 digits after decimal point | |
4849 | $rounded = sprintf("%.3f", $number); | |
74a77017 | 4850 | |
19799a22 GS |
4851 | Perl does its own C<sprintf> formatting--it emulates the C |
4852 | function C<sprintf>, but it doesn't use it (except for floating-point | |
74a77017 | 4853 | numbers, and even then only the standard modifiers are allowed). As a |
19799a22 | 4854 | result, any non-standard extensions in your local C<sprintf> are not |
74a77017 CS |
4855 | available from Perl. |
4856 | ||
194e7b38 DC |
4857 | Unlike C<printf>, C<sprintf> does not do what you probably mean when you |
4858 | pass it an array as your first argument. The array is given scalar context, | |
4859 | and instead of using the 0th element of the array as the format, Perl will | |
4860 | use the count of elements in the array as the format, which is almost never | |
4861 | useful. | |
4862 | ||
19799a22 | 4863 | Perl's C<sprintf> permits the following universally-known conversions: |
74a77017 CS |
4864 | |
4865 | %% a percent sign | |
4866 | %c a character with the given number | |
4867 | %s a string | |
4868 | %d a signed integer, in decimal | |
4869 | %u an unsigned integer, in decimal | |
4870 | %o an unsigned integer, in octal | |
4871 | %x an unsigned integer, in hexadecimal | |
4872 | %e a floating-point number, in scientific notation | |
4873 | %f a floating-point number, in fixed decimal notation | |
4874 | %g a floating-point number, in %e or %f notation | |
4875 | ||
1b3f7d21 | 4876 | In addition, Perl permits the following widely-supported conversions: |
74a77017 | 4877 | |
74a77017 CS |
4878 | %X like %x, but using upper-case letters |
4879 | %E like %e, but using an upper-case "E" | |
4880 | %G like %g, but with an upper-case "E" (if applicable) | |
4f19785b | 4881 | %b an unsigned integer, in binary |
74a77017 | 4882 | %p a pointer (outputs the Perl value's address in hexadecimal) |
1b3f7d21 | 4883 | %n special: *stores* the number of characters output so far |
b76cc8ba | 4884 | into the next variable in the parameter list |
74a77017 | 4885 | |
1b3f7d21 CS |
4886 | Finally, for backward (and we do mean "backward") compatibility, Perl |
4887 | permits these unnecessary but widely-supported conversions: | |
74a77017 | 4888 | |
1b3f7d21 | 4889 | %i a synonym for %d |
74a77017 CS |
4890 | %D a synonym for %ld |
4891 | %U a synonym for %lu | |
4892 | %O a synonym for %lo | |
4893 | %F a synonym for %f | |
4894 | ||
7b8dd722 HS |
4895 | Note that the number of exponent digits in the scientific notation produced |
4896 | by C<%e>, C<%E>, C<%g> and C<%G> for numbers with the modulus of the | |
b73fd64e JH |
4897 | exponent less than 100 is system-dependent: it may be three or less |
4898 | (zero-padded as necessary). In other words, 1.23 times ten to the | |
4899 | 99th may be either "1.23e99" or "1.23e099". | |
d764f01a | 4900 | |
7b8dd722 HS |
4901 | Between the C<%> and the format letter, you may specify a number of |
4902 | additional attributes controlling the interpretation of the format. | |
4903 | In order, these are: | |
74a77017 | 4904 | |
7b8dd722 HS |
4905 | =over 4 |
4906 | ||
4907 | =item format parameter index | |
4908 | ||
4909 | An explicit format parameter index, such as C<2$>. By default sprintf | |
4910 | will format the next unused argument in the list, but this allows you | |
4911 | to take the arguments out of order. Eg: | |
4912 | ||
4913 | printf '%2$d %1$d', 12, 34; # prints "34 12" | |
4914 | printf '%3$d %d %1$d', 1, 2, 3; # prints "3 1 1" | |
4915 | ||
4916 | =item flags | |
4917 | ||
4918 | one or more of: | |
74a77017 CS |
4919 | space prefix positive number with a space |
4920 | + prefix positive number with a plus sign | |
4921 | - left-justify within the field | |
4922 | 0 use zeros, not spaces, to right-justify | |
7b8dd722 HS |
4923 | # prefix non-zero octal with "0", non-zero hex with "0x", |
4924 | non-zero binary with "0b" | |
4925 | ||
4926 | For example: | |
4927 | ||
4928 | printf '<% d>', 12; # prints "< 12>" | |
4929 | printf '<%+d>', 12; # prints "<+12>" | |
4930 | printf '<%6s>', 12; # prints "< 12>" | |
4931 | printf '<%-6s>', 12; # prints "<12 >" | |
4932 | printf '<%06s>', 12; # prints "<000012>" | |
4933 | printf '<%#x>', 12; # prints "<0xc>" | |
4934 | ||
4935 | =item vector flag | |
4936 | ||
4937 | The vector flag C<v>, optionally specifying the join string to use. | |
4938 | This flag tells perl to interpret the supplied string as a vector | |
4939 | of integers, one for each character in the string, separated by | |
4940 | a given string (a dot C<.> by default). This can be useful for | |
4941 | displaying ordinal values of characters in arbitrary strings: | |
4942 | ||
4943 | printf "version is v%vd\n", $^V; # Perl's version | |
4944 | ||
4945 | Put an asterisk C<*> before the C<v> to override the string to | |
4946 | use to separate the numbers: | |
4947 | ||
4948 | printf "address is %*vX\n", ":", $addr; # IPv6 address | |
4949 | printf "bits are %0*v8b\n", " ", $bits; # random bitstring | |
4950 | ||
4951 | You can also explicitly specify the argument number to use for | |
4952 | the join string using eg C<*2$v>: | |
4953 | ||
4954 | printf '%*4$vX %*4$vX %*4$vX', @addr[1..3], ":"; # 3 IPv6 addresses | |
4955 | ||
4956 | =item (minimum) width | |
4957 | ||
4958 | Arguments are usually formatted to be only as wide as required to | |
4959 | display the given value. You can override the width by putting | |
4960 | a number here, or get the width from the next argument (with C<*>) | |
a472f209 | 4961 | or from a specified argument (with eg C<*2$>): |
7b8dd722 HS |
4962 | |
4963 | printf '<%s>', "a"; # prints "<a>" | |
4964 | printf '<%6s>', "a"; # prints "< a>" | |
4965 | printf '<%*s>', 6, "a"; # prints "< a>" | |
4966 | printf '<%*2$s>', "a", 6; # prints "< a>" | |
4967 | printf '<%2s>', "long"; # prints "<long>" (does not truncate) | |
4968 | ||
19799a22 GS |
4969 | If a field width obtained through C<*> is negative, it has the same |
4970 | effect as the C<-> flag: left-justification. | |
74a77017 | 4971 | |
7b8dd722 HS |
4972 | =item precision, or maximum width |
4973 | ||
6c8c9a8e | 4974 | You can specify a precision (for numeric conversions) or a maximum |
7b8dd722 HS |
4975 | width (for string conversions) by specifying a C<.> followed by a number. |
4976 | For floating point formats, this specifies the number of decimal places | |
4977 | to show (the default being 6), eg: | |
4978 | ||
4979 | # these examples are subject to system-specific variation | |
4980 | printf '<%f>', 1; # prints "<1.000000>" | |
4981 | printf '<%.1f>', 1; # prints "<1.0>" | |
4982 | printf '<%.0f>', 1; # prints "<1>" | |
4983 | printf '<%e>', 10; # prints "<1.000000e+01>" | |
4984 | printf '<%.1e>', 10; # prints "<1.0e+01>" | |
4985 | ||
4986 | For integer conversions, specifying a precision implies that the | |
4987 | output of the number itself should be zero-padded to this width: | |
4988 | ||
4989 | printf '<%.6x>', 1; # prints "<000001>" | |
4990 | printf '<%#.6x>', 1; # prints "<0x000001>" | |
4991 | printf '<%-10.6x>', 1; # prints "<000001 >" | |
4992 | ||
4993 | For string conversions, specifying a precision truncates the string | |
4994 | to fit in the specified width: | |
4995 | ||
4996 | printf '<%.5s>', "truncated"; # prints "<trunc>" | |
4997 | printf '<%10.5s>', "truncated"; # prints "< trunc>" | |
4998 | ||
4999 | You can also get the precision from the next argument using C<.*>: | |
b22c7a20 | 5000 | |
7b8dd722 HS |
5001 | printf '<%.6x>', 1; # prints "<000001>" |
5002 | printf '<%.*x>', 6, 1; # prints "<000001>" | |
5003 | ||
5004 | You cannot currently get the precision from a specified number, | |
5005 | but it is intended that this will be possible in the future using | |
5006 | eg C<.*2$>: | |
5007 | ||
5008 | printf '<%.*2$x>', 1, 6; # INVALID, but in future will print "<000001>" | |
5009 | ||
5010 | =item size | |
5011 | ||
5012 | For numeric conversions, you can specify the size to interpret the | |
5013 | number as using C<l>, C<h>, C<V>, C<q>, C<L> or C<ll>. For integer | |
5014 | conversions, numbers are usually assumed to be whatever the default | |
5015 | integer size is on your platform (usually 32 or 64 bits), but you | |
5016 | can override this to use instead one of the standard C types, as | |
5017 | supported by the compiler used to build Perl: | |
5018 | ||
5019 | l interpret integer as C type "long" or "unsigned long" | |
5020 | h interpret integer as C type "short" or "unsigned short" | |
5021 | q, L or ll interpret integer as C type "long long" or "unsigned long long" | |
5022 | (if your platform supports such a type, else it is an error) | |
5023 | ||
5024 | For floating point conversions, numbers are usually assumed to be | |
5025 | the default floating point size on your platform (double or long double), | |
5026 | but you can force 'long double' with C<q>, C<L> or C<ll> if your | |
5027 | platform supports them. | |
5028 | ||
5029 | The size specifier 'V' has no effect for Perl code, but it supported | |
5030 | for compatibility with XS code; it means 'use the standard size for | |
5031 | a Perl integer (or floating-point number)', which is already the | |
5032 | default for Perl code. | |
5033 | ||
a472f209 HS |
5034 | =item order of arguments |
5035 | ||
5036 | Normally, sprintf takes the next unused argument as the value to | |
5037 | format for each format specification. If the format specification | |
5038 | uses C<*> to require additional arguments, these are consumed from | |
5039 | the argument list in the order in which they appear in the format | |
5040 | specification I<before> the value to format. Where an argument is | |
5041 | specified using an explicit index, this does not affect the normal | |
5042 | order for the arguments (even when the explicitly specified index | |
5043 | would have been the next argument in any case). | |
5044 | ||
5045 | So: | |
5046 | ||
5047 | printf '<%*.*s>', $a, $b, $c; | |
5048 | ||
5049 | would use C<$a> for the width, C<$b> for the precision and C<$c> | |
5050 | as the value to format, while: | |
5051 | ||
5052 | print '<%*1$.*s>', $a, $b; | |
5053 | ||
5054 | would use C<$a> for the width and the precision, and C<$b> as the | |
5055 | value to format. | |
5056 | ||
5057 | Here are some more examples - beware that when using an explicit | |
5058 | index, the C<$> may need to be escaped: | |
5059 | ||
5060 | printf "%2\$d %d\n", 12, 34; # will print "34 12\n" | |
5061 | printf "%2\$d %d %d\n", 12, 34; # will print "34 12 34\n" | |
5062 | printf "%3\$d %d %d\n", 12, 34, 56; # will print "56 12 34\n" | |
5063 | printf "%2\$*3\$d %d\n", 12, 34, 3; # will print " 34 12\n" | |
5064 | ||
7b8dd722 | 5065 | =back |
b22c7a20 | 5066 | |
74a77017 CS |
5067 | If C<use locale> is in effect, the character used for the decimal |
5068 | point in formatted real numbers is affected by the LC_NUMERIC locale. | |
5069 | See L<perllocale>. | |
a0d0e21e | 5070 | |
07158430 | 5071 | If Perl understands "quads" (64-bit integers) (this requires |
a8764340 GS |
5072 | either that the platform natively support quads or that Perl |
5073 | be specifically compiled to support quads), the characters | |
07158430 JH |
5074 | |
5075 | d u o x X b i D U O | |
5076 | ||
5077 | print quads, and they may optionally be preceded by | |
5078 | ||
5079 | ll L q | |
5080 | ||
5081 | For example | |
5082 | ||
5083 | %lld %16LX %qo | |
5084 | ||
46465067 | 5085 | You can find out whether your Perl supports quads via L<Config>: |
07158430 JH |
5086 | |
5087 | use Config; | |
10cc9d2a | 5088 | ($Config{use64bitint} eq 'define' || $Config{longsize} == 8) && |
46465067 | 5089 | print "quads\n"; |
07158430 JH |
5090 | |
5091 | If Perl understands "long doubles" (this requires that the platform | |
a8764340 | 5092 | support long doubles), the flags |
07158430 JH |
5093 | |
5094 | e f g E F G | |
5095 | ||
5096 | may optionally be preceded by | |
5097 | ||
5098 | ll L | |
5099 | ||
5100 | For example | |
5101 | ||
5102 | %llf %Lg | |
5103 | ||
5104 | You can find out whether your Perl supports long doubles via L<Config>: | |
5105 | ||
5106 | use Config; | |
46465067 | 5107 | $Config{d_longdbl} eq 'define' && print "long doubles\n"; |
07158430 | 5108 | |
a0d0e21e LW |
5109 | =item sqrt EXPR |
5110 | ||
54310121 | 5111 | =item sqrt |
bbce6d69 | 5112 | |
a0d0e21e | 5113 | Return the square root of EXPR. If EXPR is omitted, returns square |
2b5ab1e7 TC |
5114 | root of C<$_>. Only works on non-negative operands, unless you've |
5115 | loaded the standard Math::Complex module. | |
5116 | ||
5117 | use Math::Complex; | |
5118 | print sqrt(-2); # prints 1.4142135623731i | |
a0d0e21e LW |
5119 | |
5120 | =item srand EXPR | |
5121 | ||
93dc8474 CS |
5122 | =item srand |
5123 | ||
0686c0b8 JH |
5124 | Sets the random number seed for the C<rand> operator. |
5125 | ||
0686c0b8 JH |
5126 | The point of the function is to "seed" the C<rand> function so that |
5127 | C<rand> can produce a different sequence each time you run your | |
e0b236fe | 5128 | program. |
0686c0b8 | 5129 | |
e0b236fe JH |
5130 | If srand() is not called explicitly, it is called implicitly at the |
5131 | first use of the C<rand> operator. However, this was not the case in | |
5132 | versions of Perl before 5.004, so if your script will run under older | |
5133 | Perl versions, it should call C<srand>. | |
93dc8474 | 5134 | |
e0b236fe JH |
5135 | Most programs won't even call srand() at all, except those that |
5136 | need a cryptographically-strong starting point rather than the | |
5137 | generally acceptable default, which is based on time of day, | |
5138 | process ID, and memory allocation, or the F</dev/urandom> device, | |
67408cae | 5139 | if available. |
9be67dbc | 5140 | |
e0b236fe JH |
5141 | You can call srand($seed) with the same $seed to reproduce the |
5142 | I<same> sequence from rand(), but this is usually reserved for | |
5143 | generating predictable results for testing or debugging. | |
5144 | Otherwise, don't call srand() more than once in your program. | |
0686c0b8 | 5145 | |
3a3e71eb JH |
5146 | Do B<not> call srand() (i.e. without an argument) more than once in |
5147 | a script. The internal state of the random number generator should | |
0686c0b8 | 5148 | contain more entropy than can be provided by any seed, so calling |
e0b236fe | 5149 | srand() again actually I<loses> randomness. |
0686c0b8 | 5150 | |
e0b236fe JH |
5151 | Most implementations of C<srand> take an integer and will silently |
5152 | truncate decimal numbers. This means C<srand(42)> will usually | |
5153 | produce the same results as C<srand(42.1)>. To be safe, always pass | |
5154 | C<srand> an integer. | |
0686c0b8 JH |
5155 | |
5156 | In versions of Perl prior to 5.004 the default seed was just the | |
5157 | current C<time>. This isn't a particularly good seed, so many old | |
5158 | programs supply their own seed value (often C<time ^ $$> or C<time ^ | |
5159 | ($$ + ($$ << 15))>), but that isn't necessary any more. | |
93dc8474 | 5160 | |
2f9daede TP |
5161 | Note that you need something much more random than the default seed for |
5162 | cryptographic purposes. Checksumming the compressed output of one or more | |
5163 | rapidly changing operating system status programs is the usual method. For | |
5164 | example: | |
28757baa | 5165 | |
5166 | srand (time ^ $$ ^ unpack "%L*", `ps axww | gzip`); | |
5167 | ||
7660c0ab | 5168 | If you're particularly concerned with this, see the C<Math::TrulyRandom> |
0078ec44 RS |
5169 | module in CPAN. |
5170 | ||
54310121 | 5171 | Frequently called programs (like CGI scripts) that simply use |
28757baa | 5172 | |
5173 | time ^ $$ | |
5174 | ||
54310121 | 5175 | for a seed can fall prey to the mathematical property that |
28757baa | 5176 | |
5177 | a^b == (a+1)^(b+1) | |
5178 | ||
0078ec44 | 5179 | one-third of the time. So don't do that. |
f86702cc | 5180 | |
a0d0e21e LW |
5181 | =item stat FILEHANDLE |
5182 | ||
5183 | =item stat EXPR | |
5184 | ||
54310121 | 5185 | =item stat |
bbce6d69 | 5186 | |
1d2dff63 GS |
5187 | Returns a 13-element list giving the status info for a file, either |
5188 | the file opened via FILEHANDLE, or named by EXPR. If EXPR is omitted, | |
7660c0ab | 5189 | it stats C<$_>. Returns a null list if the stat fails. Typically used |
1d2dff63 | 5190 | as follows: |
a0d0e21e LW |
5191 | |
5192 | ($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size, | |
5193 | $atime,$mtime,$ctime,$blksize,$blocks) | |
5194 | = stat($filename); | |
5195 | ||
54310121 | 5196 | Not all fields are supported on all filesystem types. Here are the |
c07a80fd | 5197 | meaning of the fields: |
5198 | ||
54310121 | 5199 | 0 dev device number of filesystem |
5200 | 1 ino inode number | |
5201 | 2 mode file mode (type and permissions) | |
5202 | 3 nlink number of (hard) links to the file | |
5203 | 4 uid numeric user ID of file's owner | |
5204 | 5 gid numeric group ID of file's owner | |
5205 | 6 rdev the device identifier (special files only) | |
5206 | 7 size total size of file, in bytes | |
1c74f1bd GS |
5207 | 8 atime last access time in seconds since the epoch |
5208 | 9 mtime last modify time in seconds since the epoch | |
df2a7e48 | 5209 | 10 ctime inode change time in seconds since the epoch (*) |
54310121 | 5210 | 11 blksize preferred block size for file system I/O |
5211 | 12 blocks actual number of blocks allocated | |
c07a80fd | 5212 | |
5213 | (The epoch was at 00:00 January 1, 1970 GMT.) | |
5214 | ||
df2a7e48 JH |
5215 | (*) The ctime field is non-portable, in particular you cannot expect |
5216 | it to be a "creation time", see L<perlport/"Files and Filesystems"> | |
5217 | for details. | |
5218 | ||
a0d0e21e LW |
5219 | If stat is passed the special filehandle consisting of an underline, no |
5220 | stat is done, but the current contents of the stat structure from the | |
5221 | last stat or filetest are returned. Example: | |
5222 | ||
5223 | if (-x $file && (($d) = stat(_)) && $d < 0) { | |
5224 | print "$file is executable NFS file\n"; | |
5225 | } | |
5226 | ||
ca6e1c26 JH |
5227 | (This works on machines only for which the device number is negative |
5228 | under NFS.) | |
a0d0e21e | 5229 | |
2b5ab1e7 | 5230 | Because the mode contains both the file type and its permissions, you |
b76cc8ba | 5231 | should mask off the file type portion and (s)printf using a C<"%o"> |
2b5ab1e7 TC |
5232 | if you want to see the real permissions. |
5233 | ||
5234 | $mode = (stat($filename))[2]; | |
5235 | printf "Permissions are %04o\n", $mode & 07777; | |
5236 | ||
19799a22 | 5237 | In scalar context, C<stat> returns a boolean value indicating success |
1d2dff63 GS |
5238 | or failure, and, if successful, sets the information associated with |
5239 | the special filehandle C<_>. | |
5240 | ||
2b5ab1e7 TC |
5241 | The File::stat module provides a convenient, by-name access mechanism: |
5242 | ||
5243 | use File::stat; | |
5244 | $sb = stat($filename); | |
b76cc8ba | 5245 | printf "File is %s, size is %s, perm %04o, mtime %s\n", |
2b5ab1e7 TC |
5246 | $filename, $sb->size, $sb->mode & 07777, |
5247 | scalar localtime $sb->mtime; | |
5248 | ||
ca6e1c26 JH |
5249 | You can import symbolic mode constants (C<S_IF*>) and functions |
5250 | (C<S_IS*>) from the Fcntl module: | |
5251 | ||
5252 | use Fcntl ':mode'; | |
5253 | ||
5254 | $mode = (stat($filename))[2]; | |
5255 | ||
5256 | $user_rwx = ($mode & S_IRWXU) >> 6; | |
5257 | $group_read = ($mode & S_IRGRP) >> 3; | |
5258 | $other_execute = $mode & S_IXOTH; | |
5259 | ||
3155e0b0 | 5260 | printf "Permissions are %04o\n", S_IMODE($mode), "\n"; |
ca6e1c26 JH |
5261 | |
5262 | $is_setuid = $mode & S_ISUID; | |
5263 | $is_setgid = S_ISDIR($mode); | |
5264 | ||
5265 | You could write the last two using the C<-u> and C<-d> operators. | |
5266 | The commonly available S_IF* constants are | |
5267 | ||
5268 | # Permissions: read, write, execute, for user, group, others. | |
5269 | ||
5270 | S_IRWXU S_IRUSR S_IWUSR S_IXUSR | |
5271 | S_IRWXG S_IRGRP S_IWGRP S_IXGRP | |
5272 | S_IRWXO S_IROTH S_IWOTH S_IXOTH | |
61eff3bc | 5273 | |
ca6e1c26 JH |
5274 | # Setuid/Setgid/Stickiness. |
5275 | ||
5276 | S_ISUID S_ISGID S_ISVTX S_ISTXT | |
5277 | ||
5278 | # File types. Not necessarily all are available on your system. | |
5279 | ||
5280 | S_IFREG S_IFDIR S_IFLNK S_IFBLK S_ISCHR S_IFIFO S_IFSOCK S_IFWHT S_ENFMT | |
5281 | ||
5282 | # The following are compatibility aliases for S_IRUSR, S_IWUSR, S_IXUSR. | |
5283 | ||
5284 | S_IREAD S_IWRITE S_IEXEC | |
5285 | ||
5286 | and the S_IF* functions are | |
5287 | ||
3155e0b0 | 5288 | S_IMODE($mode) the part of $mode containing the permission bits |
ca6e1c26 JH |
5289 | and the setuid/setgid/sticky bits |
5290 | ||
5291 | S_IFMT($mode) the part of $mode containing the file type | |
b76cc8ba | 5292 | which can be bit-anded with e.g. S_IFREG |
ca6e1c26 JH |
5293 | or with the following functions |
5294 | ||
5295 | # The operators -f, -d, -l, -b, -c, -p, and -s. | |
5296 | ||
5297 | S_ISREG($mode) S_ISDIR($mode) S_ISLNK($mode) | |
5298 | S_ISBLK($mode) S_ISCHR($mode) S_ISFIFO($mode) S_ISSOCK($mode) | |
5299 | ||
5300 | # No direct -X operator counterpart, but for the first one | |
5301 | # the -g operator is often equivalent. The ENFMT stands for | |
5302 | # record flocking enforcement, a platform-dependent feature. | |
5303 | ||
5304 | S_ISENFMT($mode) S_ISWHT($mode) | |
5305 | ||
5306 | See your native chmod(2) and stat(2) documentation for more details | |
5307 | about the S_* constants. | |
5308 | ||
a0d0e21e LW |
5309 | =item study SCALAR |
5310 | ||
5311 | =item study | |
5312 | ||
184e9718 | 5313 | Takes extra time to study SCALAR (C<$_> if unspecified) in anticipation of |
a0d0e21e LW |
5314 | doing many pattern matches on the string before it is next modified. |
5315 | This may or may not save time, depending on the nature and number of | |
5316 | patterns you are searching on, and on the distribution of character | |
19799a22 | 5317 | frequencies in the string to be searched--you probably want to compare |
5f05dabc | 5318 | run times with and without it to see which runs faster. Those loops |
a0d0e21e LW |
5319 | which scan for many short constant strings (including the constant |
5320 | parts of more complex patterns) will benefit most. You may have only | |
19799a22 GS |
5321 | one C<study> active at a time--if you study a different scalar the first |
5322 | is "unstudied". (The way C<study> works is this: a linked list of every | |
a0d0e21e | 5323 | character in the string to be searched is made, so we know, for |
7660c0ab | 5324 | example, where all the C<'k'> characters are. From each search string, |
a0d0e21e LW |
5325 | the rarest character is selected, based on some static frequency tables |
5326 | constructed from some C programs and English text. Only those places | |
5327 | that contain this "rarest" character are examined.) | |
5328 | ||
5a964f20 | 5329 | For example, here is a loop that inserts index producing entries |
a0d0e21e LW |
5330 | before any line containing a certain pattern: |
5331 | ||
5332 | while (<>) { | |
5333 | study; | |
2b5ab1e7 TC |
5334 | print ".IX foo\n" if /\bfoo\b/; |
5335 | print ".IX bar\n" if /\bbar\b/; | |
5336 | print ".IX blurfl\n" if /\bblurfl\b/; | |
5a964f20 | 5337 | # ... |
a0d0e21e LW |
5338 | print; |
5339 | } | |
5340 | ||
951ba7fe GS |
5341 | In searching for C</\bfoo\b/>, only those locations in C<$_> that contain C<f> |
5342 | will be looked at, because C<f> is rarer than C<o>. In general, this is | |
a0d0e21e LW |
5343 | a big win except in pathological cases. The only question is whether |
5344 | it saves you more time than it took to build the linked list in the | |
5345 | first place. | |
5346 | ||
5347 | Note that if you have to look for strings that you don't know till | |
19799a22 | 5348 | runtime, you can build an entire loop as a string and C<eval> that to |
a0d0e21e | 5349 | avoid recompiling all your patterns all the time. Together with |
7660c0ab | 5350 | undefining C<$/> to input entire files as one record, this can be very |
f86cebdf | 5351 | fast, often faster than specialized programs like fgrep(1). The following |
184e9718 | 5352 | scans a list of files (C<@files>) for a list of words (C<@words>), and prints |
a0d0e21e LW |
5353 | out the names of those files that contain a match: |
5354 | ||
5355 | $search = 'while (<>) { study;'; | |
5356 | foreach $word (@words) { | |
5357 | $search .= "++\$seen{\$ARGV} if /\\b$word\\b/;\n"; | |
5358 | } | |
5359 | $search .= "}"; | |
5360 | @ARGV = @files; | |
5361 | undef $/; | |
5362 | eval $search; # this screams | |
5f05dabc | 5363 | $/ = "\n"; # put back to normal input delimiter |
a0d0e21e LW |
5364 | foreach $file (sort keys(%seen)) { |
5365 | print $file, "\n"; | |
5366 | } | |
5367 | ||
1d2de774 | 5368 | =item sub NAME BLOCK |
cb1a09d0 | 5369 | |
1d2de774 | 5370 | =item sub NAME (PROTO) BLOCK |
cb1a09d0 | 5371 | |
1d2de774 JH |
5372 | =item sub NAME : ATTRS BLOCK |
5373 | ||
5374 | =item sub NAME (PROTO) : ATTRS BLOCK | |
5375 | ||
5376 | This is subroutine definition, not a real function I<per se>. | |
5377 | Without a BLOCK it's just a forward declaration. Without a NAME, | |
5378 | it's an anonymous function declaration, and does actually return | |
5379 | a value: the CODE ref of the closure you just created. | |
cb1a09d0 | 5380 | |
1d2de774 | 5381 | See L<perlsub> and L<perlref> for details about subroutines and |
0795dc2b | 5382 | references, and L<attributes> and L<Attribute::Handlers> for more |
1d2de774 | 5383 | information about attributes. |
cb1a09d0 | 5384 | |
87275199 | 5385 | =item substr EXPR,OFFSET,LENGTH,REPLACEMENT |
7b8d334a | 5386 | |
87275199 | 5387 | =item substr EXPR,OFFSET,LENGTH |
a0d0e21e LW |
5388 | |
5389 | =item substr EXPR,OFFSET | |
5390 | ||
5391 | Extracts a substring out of EXPR and returns it. First character is at | |
7660c0ab | 5392 | offset C<0>, or whatever you've set C<$[> to (but don't do that). |
84902520 | 5393 | If OFFSET is negative (or more precisely, less than C<$[>), starts |
87275199 GS |
5394 | that far from the end of the string. If LENGTH is omitted, returns |
5395 | everything to the end of the string. If LENGTH is negative, leaves that | |
748a9306 LW |
5396 | many characters off the end of the string. |
5397 | ||
2b5ab1e7 | 5398 | You can use the substr() function as an lvalue, in which case EXPR |
87275199 GS |
5399 | must itself be an lvalue. If you assign something shorter than LENGTH, |
5400 | the string will shrink, and if you assign something longer than LENGTH, | |
2b5ab1e7 | 5401 | the string will grow to accommodate it. To keep the string the same |
19799a22 | 5402 | length you may need to pad or chop your value using C<sprintf>. |
a0d0e21e | 5403 | |
87275199 GS |
5404 | If OFFSET and LENGTH specify a substring that is partly outside the |
5405 | string, only the part within the string is returned. If the substring | |
5406 | is beyond either end of the string, substr() returns the undefined | |
5407 | value and produces a warning. When used as an lvalue, specifying a | |
5408 | substring that is entirely outside the string is a fatal error. | |
5409 | Here's an example showing the behavior for boundary cases: | |
5410 | ||
5411 | my $name = 'fred'; | |
5412 | substr($name, 4) = 'dy'; # $name is now 'freddy' | |
5413 | my $null = substr $name, 6, 2; # returns '' (no warning) | |
5414 | my $oops = substr $name, 7; # returns undef, with warning | |
5415 | substr($name, 7) = 'gap'; # fatal error | |
5416 | ||
2b5ab1e7 | 5417 | An alternative to using substr() as an lvalue is to specify the |
7b8d334a | 5418 | replacement string as the 4th argument. This allows you to replace |
2b5ab1e7 TC |
5419 | parts of the EXPR and return what was there before in one operation, |
5420 | just as you can with splice(). | |
7b8d334a | 5421 | |
a0d0e21e LW |
5422 | =item symlink OLDFILE,NEWFILE |
5423 | ||
5424 | Creates a new filename symbolically linked to the old filename. | |
7660c0ab | 5425 | Returns C<1> for success, C<0> otherwise. On systems that don't support |
a0d0e21e LW |
5426 | symbolic links, produces a fatal error at run time. To check for that, |
5427 | use eval: | |
5428 | ||
2b5ab1e7 | 5429 | $symlink_exists = eval { symlink("",""); 1 }; |
a0d0e21e LW |
5430 | |
5431 | =item syscall LIST | |
5432 | ||
5433 | Calls the system call specified as the first element of the list, | |
5434 | passing the remaining elements as arguments to the system call. If | |
5435 | unimplemented, produces a fatal error. The arguments are interpreted | |
5436 | as follows: if a given argument is numeric, the argument is passed as | |
5437 | an int. If not, the pointer to the string value is passed. You are | |
5438 | responsible to make sure a string is pre-extended long enough to | |
a3cb178b | 5439 | receive any result that might be written into a string. You can't use a |
19799a22 | 5440 | string literal (or other read-only string) as an argument to C<syscall> |
a3cb178b GS |
5441 | because Perl has to assume that any string pointer might be written |
5442 | through. If your | |
a0d0e21e | 5443 | integer arguments are not literals and have never been interpreted in a |
7660c0ab | 5444 | numeric context, you may need to add C<0> to them to force them to look |
19799a22 | 5445 | like numbers. This emulates the C<syswrite> function (or vice versa): |
a0d0e21e LW |
5446 | |
5447 | require 'syscall.ph'; # may need to run h2ph | |
a3cb178b GS |
5448 | $s = "hi there\n"; |
5449 | syscall(&SYS_write, fileno(STDOUT), $s, length $s); | |
a0d0e21e | 5450 | |
5f05dabc | 5451 | Note that Perl supports passing of up to only 14 arguments to your system call, |
a0d0e21e LW |
5452 | which in practice should usually suffice. |
5453 | ||
fb73857a | 5454 | Syscall returns whatever value returned by the system call it calls. |
19799a22 | 5455 | If the system call fails, C<syscall> returns C<-1> and sets C<$!> (errno). |
7660c0ab | 5456 | Note that some system calls can legitimately return C<-1>. The proper |
fb73857a | 5457 | way to handle such calls is to assign C<$!=0;> before the call and |
7660c0ab | 5458 | check the value of C<$!> if syscall returns C<-1>. |
fb73857a | 5459 | |
5460 | There's a problem with C<syscall(&SYS_pipe)>: it returns the file | |
5461 | number of the read end of the pipe it creates. There is no way | |
b76cc8ba | 5462 | to retrieve the file number of the other end. You can avoid this |
19799a22 | 5463 | problem by using C<pipe> instead. |
fb73857a | 5464 | |
c07a80fd | 5465 | =item sysopen FILEHANDLE,FILENAME,MODE |
5466 | ||
5467 | =item sysopen FILEHANDLE,FILENAME,MODE,PERMS | |
5468 | ||
5469 | Opens the file whose filename is given by FILENAME, and associates it | |
5470 | with FILEHANDLE. If FILEHANDLE is an expression, its value is used as | |
5471 | the name of the real filehandle wanted. This function calls the | |
19799a22 | 5472 | underlying operating system's C<open> function with the parameters |
c07a80fd | 5473 | FILENAME, MODE, PERMS. |
5474 | ||
5475 | The possible values and flag bits of the MODE parameter are | |
5476 | system-dependent; they are available via the standard module C<Fcntl>. | |
ea2b5ef6 JH |
5477 | See the documentation of your operating system's C<open> to see which |
5478 | values and flag bits are available. You may combine several flags | |
5479 | using the C<|>-operator. | |
5480 | ||
5481 | Some of the most common values are C<O_RDONLY> for opening the file in | |
5482 | read-only mode, C<O_WRONLY> for opening the file in write-only mode, | |
5483 | and C<O_RDWR> for opening the file in read-write mode, and. | |
5484 | ||
adf5897a DF |
5485 | For historical reasons, some values work on almost every system |
5486 | supported by perl: zero means read-only, one means write-only, and two | |
5487 | means read/write. We know that these values do I<not> work under | |
7c5ffed3 | 5488 | OS/390 & VM/ESA Unix and on the Macintosh; you probably don't want to |
4af147f6 | 5489 | use them in new code. |
c07a80fd | 5490 | |
19799a22 | 5491 | If the file named by FILENAME does not exist and the C<open> call creates |
7660c0ab | 5492 | it (typically because MODE includes the C<O_CREAT> flag), then the value of |
5a964f20 | 5493 | PERMS specifies the permissions of the newly created file. If you omit |
19799a22 | 5494 | the PERMS argument to C<sysopen>, Perl uses the octal value C<0666>. |
5a964f20 | 5495 | These permission values need to be in octal, and are modified by your |
0591cd52 NT |
5496 | process's current C<umask>. |
5497 | ||
ea2b5ef6 JH |
5498 | In many systems the C<O_EXCL> flag is available for opening files in |
5499 | exclusive mode. This is B<not> locking: exclusiveness means here that | |
5500 | if the file already exists, sysopen() fails. The C<O_EXCL> wins | |
5501 | C<O_TRUNC>. | |
5502 | ||
5503 | Sometimes you may want to truncate an already-existing file: C<O_TRUNC>. | |
5504 | ||
19799a22 | 5505 | You should seldom if ever use C<0644> as argument to C<sysopen>, because |
2b5ab1e7 TC |
5506 | that takes away the user's option to have a more permissive umask. |
5507 | Better to omit it. See the perlfunc(1) entry on C<umask> for more | |
5508 | on this. | |
c07a80fd | 5509 | |
4af147f6 CS |
5510 | Note that C<sysopen> depends on the fdopen() C library function. |
5511 | On many UNIX systems, fdopen() is known to fail when file descriptors | |
5512 | exceed a certain value, typically 255. If you need more file | |
5513 | descriptors than that, consider rebuilding Perl to use the C<sfio> | |
5514 | library, or perhaps using the POSIX::open() function. | |
5515 | ||
2b5ab1e7 | 5516 | See L<perlopentut> for a kinder, gentler explanation of opening files. |
28757baa | 5517 | |
a0d0e21e LW |
5518 | =item sysread FILEHANDLE,SCALAR,LENGTH,OFFSET |
5519 | ||
5520 | =item sysread FILEHANDLE,SCALAR,LENGTH | |
5521 | ||
9124316e JH |
5522 | Attempts to read LENGTH I<characters> of data into variable SCALAR from |
5523 | the specified FILEHANDLE, using the system call read(2). It bypasses | |
5524 | buffered IO, so mixing this with other kinds of reads, C<print>, | |
5525 | C<write>, C<seek>, C<tell>, or C<eof> can cause confusion because | |
5526 | stdio usually buffers data. Returns the number of characters actually | |
5527 | read, C<0> at end of file, or undef if there was an error. SCALAR | |
5528 | will be grown or shrunk so that the last byte actually read is the | |
5529 | last byte of the scalar after the read. | |
5530 | ||
5531 | Note the I<characters>: depending on the status of the filehandle, | |
5532 | either (8-bit) bytes or characters are read. By default all | |
5533 | filehandles operate on bytes, but for example if the filehandle has | |
fae2c0fb | 5534 | been opened with the C<:utf8> I/O layer (see L</open>, and the C<open> |
9124316e | 5535 | pragma, L<open>), the I/O will operate on characters, not bytes. |
ff68c719 | 5536 | |
5537 | An OFFSET may be specified to place the read data at some place in the | |
5538 | string other than the beginning. A negative OFFSET specifies | |
9124316e JH |
5539 | placement at that many characters counting backwards from the end of |
5540 | the string. A positive OFFSET greater than the length of SCALAR | |
5541 | results in the string being padded to the required size with C<"\0"> | |
5542 | bytes before the result of the read is appended. | |
a0d0e21e | 5543 | |
2b5ab1e7 TC |
5544 | There is no syseof() function, which is ok, since eof() doesn't work |
5545 | very well on device files (like ttys) anyway. Use sysread() and check | |
19799a22 | 5546 | for a return value for 0 to decide whether you're done. |
2b5ab1e7 | 5547 | |
137443ea | 5548 | =item sysseek FILEHANDLE,POSITION,WHENCE |
5549 | ||
9124316e JH |
5550 | Sets FILEHANDLE's system position I<in bytes> using the system call |
5551 | lseek(2). FILEHANDLE may be an expression whose value gives the name | |
5552 | of the filehandle. The values for WHENCE are C<0> to set the new | |
5553 | position to POSITION, C<1> to set the it to the current position plus | |
5554 | POSITION, and C<2> to set it to EOF plus POSITION (typically | |
5555 | negative). | |
5556 | ||
5557 | Note the I<in bytes>: even if the filehandle has been set to operate | |
fae2c0fb | 5558 | on characters (for example by using the C<:utf8> I/O layer), tell() |
9124316e JH |
5559 | will return byte offsets, not character offsets (because implementing |
5560 | that would render sysseek() very slow). | |
5561 | ||
5562 | sysseek() bypasses normal buffered io, so mixing this with reads (other | |
5563 | than C<sysread>, for example >< or read()) C<print>, C<write>, | |
5564 | C<seek>, C<tell>, or C<eof> may cause confusion. | |
86989e5d JH |
5565 | |
5566 | For WHENCE, you may also use the constants C<SEEK_SET>, C<SEEK_CUR>, | |
5567 | and C<SEEK_END> (start of the file, current position, end of the file) | |
5568 | from the Fcntl module. Use of the constants is also more portable | |
5569 | than relying on 0, 1, and 2. For example to define a "systell" function: | |
5570 | ||
5571 | use Fnctl 'SEEK_CUR'; | |
5572 | sub systell { sysseek($_[0], 0, SEEK_CUR) } | |
8903cb82 | 5573 | |
5574 | Returns the new position, or the undefined value on failure. A position | |
19799a22 GS |
5575 | of zero is returned as the string C<"0 but true">; thus C<sysseek> returns |
5576 | true on success and false on failure, yet you can still easily determine | |
8903cb82 | 5577 | the new position. |
137443ea | 5578 | |
a0d0e21e LW |
5579 | =item system LIST |
5580 | ||
8bf3b016 GS |
5581 | =item system PROGRAM LIST |
5582 | ||
19799a22 GS |
5583 | Does exactly the same thing as C<exec LIST>, except that a fork is |
5584 | done first, and the parent process waits for the child process to | |
5585 | complete. Note that argument processing varies depending on the | |
5586 | number of arguments. If there is more than one argument in LIST, | |
5587 | or if LIST is an array with more than one value, starts the program | |
5588 | given by the first element of the list with arguments given by the | |
5589 | rest of the list. If there is only one scalar argument, the argument | |
5590 | is checked for shell metacharacters, and if there are any, the | |
5591 | entire argument is passed to the system's command shell for parsing | |
5592 | (this is C</bin/sh -c> on Unix platforms, but varies on other | |
5593 | platforms). If there are no shell metacharacters in the argument, | |
5594 | it is split into words and passed directly to C<execvp>, which is | |
5595 | more efficient. | |
5596 | ||
0f897271 GS |
5597 | Beginning with v5.6.0, Perl will attempt to flush all files opened for |
5598 | output before any operation that may do a fork, but this may not be | |
5599 | supported on some platforms (see L<perlport>). To be safe, you may need | |
5600 | to set C<$|> ($AUTOFLUSH in English) or call the C<autoflush()> method | |
5601 | of C<IO::Handle> on any open handles. | |
a2008d6d | 5602 | |
9d6eb86e | 5603 | The return value is the exit status of the program as returned by the |
7717d0e7 | 5604 | C<wait> call. To get the actual exit value shift right by eight (see below). |
9d6eb86e | 5605 | See also L</exec>. This is I<not> what you want to use to capture |
54310121 | 5606 | the output from a command, for that you should use merely backticks or |
d5a9bfb0 IZ |
5607 | C<qx//>, as described in L<perlop/"`STRING`">. Return value of -1 |
5608 | indicates a failure to start the program (inspect $! for the reason). | |
a0d0e21e | 5609 | |
19799a22 GS |
5610 | Like C<exec>, C<system> allows you to lie to a program about its name if |
5611 | you use the C<system PROGRAM LIST> syntax. Again, see L</exec>. | |
8bf3b016 | 5612 | |
9d6eb86e JH |
5613 | Because C<system> and backticks block C<SIGINT> and C<SIGQUIT>, |
5614 | killing the program they're running doesn't actually interrupt | |
5615 | your program. | |
28757baa | 5616 | |
5617 | @args = ("command", "arg1", "arg2"); | |
54310121 | 5618 | system(@args) == 0 |
5619 | or die "system @args failed: $?" | |
28757baa | 5620 | |
5a964f20 TC |
5621 | You can check all the failure possibilities by inspecting |
5622 | C<$?> like this: | |
28757baa | 5623 | |
5a964f20 TC |
5624 | $exit_value = $? >> 8; |
5625 | $signal_num = $? & 127; | |
5626 | $dumped_core = $? & 128; | |
f86702cc | 5627 | |
7717d0e7 | 5628 | or more portably by using the W*() calls of the POSIX extension; |
9d6eb86e JH |
5629 | see L<perlport> for more information. |
5630 | ||
c8db1d39 TC |
5631 | When the arguments get executed via the system shell, results |
5632 | and return codes will be subject to its quirks and capabilities. | |
5633 | See L<perlop/"`STRING`"> and L</exec> for details. | |
bb32b41a | 5634 | |
a0d0e21e LW |
5635 | =item syswrite FILEHANDLE,SCALAR,LENGTH,OFFSET |
5636 | ||
5637 | =item syswrite FILEHANDLE,SCALAR,LENGTH | |
5638 | ||
145d37e2 GA |
5639 | =item syswrite FILEHANDLE,SCALAR |
5640 | ||
9124316e JH |
5641 | Attempts to write LENGTH characters of data from variable SCALAR to |
5642 | the specified FILEHANDLE, using the system call write(2). If LENGTH | |
5643 | is not specified, writes whole SCALAR. It bypasses buffered IO, so | |
5644 | mixing this with reads (other than C<sysread())>, C<print>, C<write>, | |
5645 | C<seek>, C<tell>, or C<eof> may cause confusion because stdio usually | |
5646 | buffers data. Returns the number of characters actually written, or | |
5647 | C<undef> if there was an error. If the LENGTH is greater than the | |
5648 | available data in the SCALAR after the OFFSET, only as much data as is | |
5649 | available will be written. | |
ff68c719 | 5650 | |
5651 | An OFFSET may be specified to write the data from some part of the | |
5652 | string other than the beginning. A negative OFFSET specifies writing | |
9124316e JH |
5653 | that many characters counting backwards from the end of the string. |
5654 | In the case the SCALAR is empty you can use OFFSET but only zero offset. | |
5655 | ||
5656 | Note the I<characters>: depending on the status of the filehandle, | |
5657 | either (8-bit) bytes or characters are written. By default all | |
5658 | filehandles operate on bytes, but for example if the filehandle has | |
fae2c0fb | 5659 | been opened with the C<:utf8> I/O layer (see L</open>, and the open |
9124316e | 5660 | pragma, L<open>), the I/O will operate on characters, not bytes. |
a0d0e21e LW |
5661 | |
5662 | =item tell FILEHANDLE | |
5663 | ||
5664 | =item tell | |
5665 | ||
9124316e JH |
5666 | Returns the current position I<in bytes> for FILEHANDLE, or -1 on |
5667 | error. FILEHANDLE may be an expression whose value gives the name of | |
5668 | the actual filehandle. If FILEHANDLE is omitted, assumes the file | |
5669 | last read. | |
5670 | ||
5671 | Note the I<in bytes>: even if the filehandle has been set to | |
5672 | operate on characters (for example by using the C<:utf8> open | |
fae2c0fb | 5673 | layer), tell() will return byte offsets, not character offsets |
9124316e | 5674 | (because that would render seek() and tell() rather slow). |
2b5ab1e7 | 5675 | |
cfd73201 JH |
5676 | The return value of tell() for the standard streams like the STDIN |
5677 | depends on the operating system: it may return -1 or something else. | |
5678 | tell() on pipes, fifos, and sockets usually returns -1. | |
5679 | ||
19799a22 | 5680 | There is no C<systell> function. Use C<sysseek(FH, 0, 1)> for that. |
a0d0e21e | 5681 | |
9124316e JH |
5682 | Do not use tell() on a filehandle that has been opened using |
5683 | sysopen(), use sysseek() for that as described above. Why? Because | |
5684 | sysopen() creates unbuffered, "raw", filehandles, while open() creates | |
5685 | buffered filehandles. sysseek() make sense only on the first kind, | |
5686 | tell() only makes sense on the second kind. | |
5687 | ||
a0d0e21e LW |
5688 | =item telldir DIRHANDLE |
5689 | ||
19799a22 GS |
5690 | Returns the current position of the C<readdir> routines on DIRHANDLE. |
5691 | Value may be given to C<seekdir> to access a particular location in a | |
a0d0e21e LW |
5692 | directory. Has the same caveats about possible directory compaction as |
5693 | the corresponding system library routine. | |
5694 | ||
4633a7c4 | 5695 | =item tie VARIABLE,CLASSNAME,LIST |
a0d0e21e | 5696 | |
4633a7c4 LW |
5697 | This function binds a variable to a package class that will provide the |
5698 | implementation for the variable. VARIABLE is the name of the variable | |
5699 | to be enchanted. CLASSNAME is the name of a class implementing objects | |
19799a22 | 5700 | of correct type. Any additional arguments are passed to the C<new> |
8a059744 GS |
5701 | method of the class (meaning C<TIESCALAR>, C<TIEHANDLE>, C<TIEARRAY>, |
5702 | or C<TIEHASH>). Typically these are arguments such as might be passed | |
19799a22 GS |
5703 | to the C<dbm_open()> function of C. The object returned by the C<new> |
5704 | method is also returned by the C<tie> function, which would be useful | |
8a059744 | 5705 | if you want to access other methods in CLASSNAME. |
a0d0e21e | 5706 | |
19799a22 | 5707 | Note that functions such as C<keys> and C<values> may return huge lists |
1d2dff63 | 5708 | when used on large objects, like DBM files. You may prefer to use the |
19799a22 | 5709 | C<each> function to iterate over such. Example: |
a0d0e21e LW |
5710 | |
5711 | # print out history file offsets | |
4633a7c4 | 5712 | use NDBM_File; |
da0045b7 | 5713 | tie(%HIST, 'NDBM_File', '/usr/lib/news/history', 1, 0); |
a0d0e21e LW |
5714 | while (($key,$val) = each %HIST) { |
5715 | print $key, ' = ', unpack('L',$val), "\n"; | |
5716 | } | |
5717 | untie(%HIST); | |
5718 | ||
aa689395 | 5719 | A class implementing a hash should have the following methods: |
a0d0e21e | 5720 | |
4633a7c4 | 5721 | TIEHASH classname, LIST |
a0d0e21e LW |
5722 | FETCH this, key |
5723 | STORE this, key, value | |
5724 | DELETE this, key | |
8a059744 | 5725 | CLEAR this |
a0d0e21e LW |
5726 | EXISTS this, key |
5727 | FIRSTKEY this | |
5728 | NEXTKEY this, lastkey | |
8a059744 | 5729 | DESTROY this |
d7da42b7 | 5730 | UNTIE this |
a0d0e21e | 5731 | |
4633a7c4 | 5732 | A class implementing an ordinary array should have the following methods: |
a0d0e21e | 5733 | |
4633a7c4 | 5734 | TIEARRAY classname, LIST |
a0d0e21e LW |
5735 | FETCH this, key |
5736 | STORE this, key, value | |
8a059744 GS |
5737 | FETCHSIZE this |
5738 | STORESIZE this, count | |
5739 | CLEAR this | |
5740 | PUSH this, LIST | |
5741 | POP this | |
5742 | SHIFT this | |
5743 | UNSHIFT this, LIST | |
5744 | SPLICE this, offset, length, LIST | |
5745 | EXTEND this, count | |
5746 | DESTROY this | |
d7da42b7 | 5747 | UNTIE this |
8a059744 GS |
5748 | |
5749 | A class implementing a file handle should have the following methods: | |
5750 | ||
5751 | TIEHANDLE classname, LIST | |
5752 | READ this, scalar, length, offset | |
5753 | READLINE this | |
5754 | GETC this | |
5755 | WRITE this, scalar, length, offset | |
5756 | PRINT this, LIST | |
5757 | PRINTF this, format, LIST | |
e08f2115 GA |
5758 | BINMODE this |
5759 | EOF this | |
5760 | FILENO this | |
5761 | SEEK this, position, whence | |
5762 | TELL this | |
5763 | OPEN this, mode, LIST | |
8a059744 GS |
5764 | CLOSE this |
5765 | DESTROY this | |
d7da42b7 | 5766 | UNTIE this |
a0d0e21e | 5767 | |
4633a7c4 | 5768 | A class implementing a scalar should have the following methods: |
a0d0e21e | 5769 | |
4633a7c4 | 5770 | TIESCALAR classname, LIST |
54310121 | 5771 | FETCH this, |
a0d0e21e | 5772 | STORE this, value |
8a059744 | 5773 | DESTROY this |
d7da42b7 | 5774 | UNTIE this |
8a059744 GS |
5775 | |
5776 | Not all methods indicated above need be implemented. See L<perltie>, | |
2b5ab1e7 | 5777 | L<Tie::Hash>, L<Tie::Array>, L<Tie::Scalar>, and L<Tie::Handle>. |
a0d0e21e | 5778 | |
19799a22 | 5779 | Unlike C<dbmopen>, the C<tie> function will not use or require a module |
4633a7c4 | 5780 | for you--you need to do that explicitly yourself. See L<DB_File> |
19799a22 | 5781 | or the F<Config> module for interesting C<tie> implementations. |
4633a7c4 | 5782 | |
b687b08b | 5783 | For further details see L<perltie>, L<"tied VARIABLE">. |
cc6b7395 | 5784 | |
f3cbc334 RS |
5785 | =item tied VARIABLE |
5786 | ||
5787 | Returns a reference to the object underlying VARIABLE (the same value | |
19799a22 | 5788 | that was originally returned by the C<tie> call that bound the variable |
f3cbc334 RS |
5789 | to a package.) Returns the undefined value if VARIABLE isn't tied to a |
5790 | package. | |
5791 | ||
a0d0e21e LW |
5792 | =item time |
5793 | ||
da0045b7 | 5794 | Returns the number of non-leap seconds since whatever time the system |
8939ba94 | 5795 | considers to be the epoch (that's 00:00:00, January 1, 1904 for Mac OS, |
da0045b7 | 5796 | and 00:00:00 UTC, January 1, 1970 for most other systems). |
19799a22 | 5797 | Suitable for feeding to C<gmtime> and C<localtime>. |
a0d0e21e | 5798 | |
68f8bed4 JH |
5799 | For measuring time in better granularity than one second, |
5800 | you may use either the Time::HiRes module from CPAN, or | |
5801 | if you have gettimeofday(2), you may be able to use the | |
5802 | C<syscall> interface of Perl, see L<perlfaq8> for details. | |
5803 | ||
a0d0e21e LW |
5804 | =item times |
5805 | ||
1d2dff63 | 5806 | Returns a four-element list giving the user and system times, in |
a0d0e21e LW |
5807 | seconds, for this process and the children of this process. |
5808 | ||
5809 | ($user,$system,$cuser,$csystem) = times; | |
5810 | ||
dc19f4fb MJD |
5811 | In scalar context, C<times> returns C<$user>. |
5812 | ||
a0d0e21e LW |
5813 | =item tr/// |
5814 | ||
19799a22 | 5815 | The transliteration operator. Same as C<y///>. See L<perlop>. |
a0d0e21e LW |
5816 | |
5817 | =item truncate FILEHANDLE,LENGTH | |
5818 | ||
5819 | =item truncate EXPR,LENGTH | |
5820 | ||
5821 | Truncates the file opened on FILEHANDLE, or named by EXPR, to the | |
5822 | specified length. Produces a fatal error if truncate isn't implemented | |
19799a22 | 5823 | on your system. Returns true if successful, the undefined value |
a3cb178b | 5824 | otherwise. |
a0d0e21e | 5825 | |
90ddc76f MS |
5826 | The behavior is undefined if LENGTH is greater than the length of the |
5827 | file. | |
5828 | ||
a0d0e21e LW |
5829 | =item uc EXPR |
5830 | ||
54310121 | 5831 | =item uc |
bbce6d69 | 5832 | |
a0d0e21e | 5833 | Returns an uppercased version of EXPR. This is the internal function |
ad0029c4 JH |
5834 | implementing the C<\U> escape in double-quoted strings. Respects |
5835 | current LC_CTYPE locale if C<use locale> in force. See L<perllocale> | |
983ffd37 JH |
5836 | and L<perlunicode> for more details about locale and Unicode support. |
5837 | It does not attempt to do titlecase mapping on initial letters. See | |
5838 | C<ucfirst> for that. | |
a0d0e21e | 5839 | |
7660c0ab | 5840 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 5841 | |
a0d0e21e LW |
5842 | =item ucfirst EXPR |
5843 | ||
54310121 | 5844 | =item ucfirst |
bbce6d69 | 5845 | |
ad0029c4 JH |
5846 | Returns the value of EXPR with the first character in uppercase |
5847 | (titlecase in Unicode). This is the internal function implementing | |
5848 | the C<\u> escape in double-quoted strings. Respects current LC_CTYPE | |
983ffd37 JH |
5849 | locale if C<use locale> in force. See L<perllocale> and L<perlunicode> |
5850 | for more details about locale and Unicode support. | |
a0d0e21e | 5851 | |
7660c0ab | 5852 | If EXPR is omitted, uses C<$_>. |
bbce6d69 | 5853 | |
a0d0e21e LW |
5854 | =item umask EXPR |
5855 | ||
5856 | =item umask | |
5857 | ||
2f9daede | 5858 | Sets the umask for the process to EXPR and returns the previous value. |
eec2d3df GS |
5859 | If EXPR is omitted, merely returns the current umask. |
5860 | ||
0591cd52 NT |
5861 | The Unix permission C<rwxr-x---> is represented as three sets of three |
5862 | bits, or three octal digits: C<0750> (the leading 0 indicates octal | |
b5a41e52 | 5863 | and isn't one of the digits). The C<umask> value is such a number |
0591cd52 NT |
5864 | representing disabled permissions bits. The permission (or "mode") |
5865 | values you pass C<mkdir> or C<sysopen> are modified by your umask, so | |
5866 | even if you tell C<sysopen> to create a file with permissions C<0777>, | |
5867 | if your umask is C<0022> then the file will actually be created with | |
5868 | permissions C<0755>. If your C<umask> were C<0027> (group can't | |
5869 | write; others can't read, write, or execute), then passing | |
19799a22 | 5870 | C<sysopen> C<0666> would create a file with mode C<0640> (C<0666 &~ |
0591cd52 NT |
5871 | 027> is C<0640>). |
5872 | ||
5873 | Here's some advice: supply a creation mode of C<0666> for regular | |
19799a22 GS |
5874 | files (in C<sysopen>) and one of C<0777> for directories (in |
5875 | C<mkdir>) and executable files. This gives users the freedom of | |
0591cd52 NT |
5876 | choice: if they want protected files, they might choose process umasks |
5877 | of C<022>, C<027>, or even the particularly antisocial mask of C<077>. | |
5878 | Programs should rarely if ever make policy decisions better left to | |
5879 | the user. The exception to this is when writing files that should be | |
5880 | kept private: mail files, web browser cookies, I<.rhosts> files, and | |
5881 | so on. | |
5882 | ||
f86cebdf | 5883 | If umask(2) is not implemented on your system and you are trying to |
eec2d3df | 5884 | restrict access for I<yourself> (i.e., (EXPR & 0700) > 0), produces a |
f86cebdf | 5885 | fatal error at run time. If umask(2) is not implemented and you are |
eec2d3df GS |
5886 | not trying to restrict access for yourself, returns C<undef>. |
5887 | ||
5888 | Remember that a umask is a number, usually given in octal; it is I<not> a | |
5889 | string of octal digits. See also L</oct>, if all you have is a string. | |
a0d0e21e LW |
5890 | |
5891 | =item undef EXPR | |
5892 | ||
5893 | =item undef | |
5894 | ||
54310121 | 5895 | Undefines the value of EXPR, which must be an lvalue. Use only on a |
19799a22 GS |
5896 | scalar value, an array (using C<@>), a hash (using C<%>), a subroutine |
5897 | (using C<&>), or a typeglob (using <*>). (Saying C<undef $hash{$key}> | |
20408e3c GS |
5898 | will probably not do what you expect on most predefined variables or |
5899 | DBM list values, so don't do that; see L<delete>.) Always returns the | |
5900 | undefined value. You can omit the EXPR, in which case nothing is | |
5901 | undefined, but you still get an undefined value that you could, for | |
5902 | instance, return from a subroutine, assign to a variable or pass as a | |
5903 | parameter. Examples: | |
a0d0e21e LW |
5904 | |
5905 | undef $foo; | |
f86cebdf | 5906 | undef $bar{'blurfl'}; # Compare to: delete $bar{'blurfl'}; |
a0d0e21e | 5907 | undef @ary; |
aa689395 | 5908 | undef %hash; |
a0d0e21e | 5909 | undef &mysub; |
20408e3c | 5910 | undef *xyz; # destroys $xyz, @xyz, %xyz, &xyz, etc. |
54310121 | 5911 | return (wantarray ? (undef, $errmsg) : undef) if $they_blew_it; |
2f9daede TP |
5912 | select undef, undef, undef, 0.25; |
5913 | ($a, $b, undef, $c) = &foo; # Ignore third value returned | |
a0d0e21e | 5914 | |
5a964f20 TC |
5915 | Note that this is a unary operator, not a list operator. |
5916 | ||
a0d0e21e LW |
5917 | =item unlink LIST |
5918 | ||
54310121 | 5919 | =item unlink |
bbce6d69 | 5920 | |
a0d0e21e LW |
5921 | Deletes a list of files. Returns the number of files successfully |
5922 | deleted. | |
5923 | ||
5924 | $cnt = unlink 'a', 'b', 'c'; | |
5925 | unlink @goners; | |
5926 | unlink <*.bak>; | |
5927 | ||
19799a22 | 5928 | Note: C<unlink> will not delete directories unless you are superuser and |
a0d0e21e LW |
5929 | the B<-U> flag is supplied to Perl. Even if these conditions are |
5930 | met, be warned that unlinking a directory can inflict damage on your | |
19799a22 | 5931 | filesystem. Use C<rmdir> instead. |
a0d0e21e | 5932 | |
7660c0ab | 5933 | If LIST is omitted, uses C<$_>. |
bbce6d69 | 5934 | |
a0d0e21e LW |
5935 | =item unpack TEMPLATE,EXPR |
5936 | ||
19799a22 | 5937 | C<unpack> does the reverse of C<pack>: it takes a string |
2b6c5635 | 5938 | and expands it out into a list of values. |
19799a22 | 5939 | (In scalar context, it returns merely the first value produced.) |
2b6c5635 GS |
5940 | |
5941 | The string is broken into chunks described by the TEMPLATE. Each chunk | |
5942 | is converted separately to a value. Typically, either the string is a result | |
5943 | of C<pack>, or the bytes of the string represent a C structure of some | |
5944 | kind. | |
5945 | ||
19799a22 | 5946 | The TEMPLATE has the same format as in the C<pack> function. |
a0d0e21e LW |
5947 | Here's a subroutine that does substring: |
5948 | ||
5949 | sub substr { | |
5a964f20 | 5950 | my($what,$where,$howmuch) = @_; |
a0d0e21e LW |
5951 | unpack("x$where a$howmuch", $what); |
5952 | } | |
5953 | ||
5954 | and then there's | |
5955 | ||
5956 | sub ordinal { unpack("c",$_[0]); } # same as ord() | |
5957 | ||
2b6c5635 | 5958 | In addition to fields allowed in pack(), you may prefix a field with |
61eff3bc JH |
5959 | a %<number> to indicate that |
5960 | you want a <number>-bit checksum of the items instead of the items | |
2b6c5635 GS |
5961 | themselves. Default is a 16-bit checksum. Checksum is calculated by |
5962 | summing numeric values of expanded values (for string fields the sum of | |
5963 | C<ord($char)> is taken, for bit fields the sum of zeroes and ones). | |
5964 | ||
5965 | For example, the following | |
a0d0e21e LW |
5966 | computes the same number as the System V sum program: |
5967 | ||
19799a22 GS |
5968 | $checksum = do { |
5969 | local $/; # slurp! | |
5970 | unpack("%32C*",<>) % 65535; | |
5971 | }; | |
a0d0e21e LW |
5972 | |
5973 | The following efficiently counts the number of set bits in a bit vector: | |
5974 | ||
5975 | $setbits = unpack("%32b*", $selectmask); | |
5976 | ||
951ba7fe | 5977 | The C<p> and C<P> formats should be used with care. Since Perl |
3160c391 GS |
5978 | has no way of checking whether the value passed to C<unpack()> |
5979 | corresponds to a valid memory location, passing a pointer value that's | |
5980 | not known to be valid is likely to have disastrous consequences. | |
5981 | ||
2b6c5635 GS |
5982 | If the repeat count of a field is larger than what the remainder of |
5983 | the input string allows, repeat count is decreased. If the input string | |
b76cc8ba | 5984 | is longer than one described by the TEMPLATE, the rest is ignored. |
2b6c5635 | 5985 | |
851646ae | 5986 | See L</pack> for more examples and notes. |
5a929a98 | 5987 | |
98293880 JH |
5988 | =item untie VARIABLE |
5989 | ||
19799a22 | 5990 | Breaks the binding between a variable and a package. (See C<tie>.) |
1188453a | 5991 | Has no effect if the variable is not tied. |
98293880 | 5992 | |
a0d0e21e LW |
5993 | =item unshift ARRAY,LIST |
5994 | ||
19799a22 | 5995 | Does the opposite of a C<shift>. Or the opposite of a C<push>, |
a0d0e21e LW |
5996 | depending on how you look at it. Prepends list to the front of the |
5997 | array, and returns the new number of elements in the array. | |
5998 | ||
76e4c2bb | 5999 | unshift(@ARGV, '-e') unless $ARGV[0] =~ /^-/; |
a0d0e21e LW |
6000 | |
6001 | Note the LIST is prepended whole, not one element at a time, so the | |
19799a22 | 6002 | prepended elements stay in the same order. Use C<reverse> to do the |
a0d0e21e LW |
6003 | reverse. |
6004 | ||
f6c8478c GS |
6005 | =item use Module VERSION LIST |
6006 | ||
6007 | =item use Module VERSION | |
6008 | ||
a0d0e21e LW |
6009 | =item use Module LIST |
6010 | ||
6011 | =item use Module | |
6012 | ||
da0045b7 | 6013 | =item use VERSION |
6014 | ||
a0d0e21e LW |
6015 | Imports some semantics into the current package from the named module, |
6016 | generally by aliasing certain subroutine or variable names into your | |
6017 | package. It is exactly equivalent to | |
6018 | ||
6019 | BEGIN { require Module; import Module LIST; } | |
6020 | ||
54310121 | 6021 | except that Module I<must> be a bareword. |
da0045b7 | 6022 | |
3b825e41 RK |
6023 | VERSION may be either a numeric argument such as 5.006, which will be |
6024 | compared to C<$]>, or a literal of the form v5.6.1, which will be compared | |
6025 | to C<$^V> (aka $PERL_VERSION. A fatal error is produced if VERSION is | |
6026 | greater than the version of the current Perl interpreter; Perl will not | |
6027 | attempt to parse the rest of the file. Compare with L</require>, which can | |
6028 | do a similar check at run time. | |
6029 | ||
6030 | Specifying VERSION as a literal of the form v5.6.1 should generally be | |
6031 | avoided, because it leads to misleading error messages under earlier | |
6032 | versions of Perl which do not support this syntax. The equivalent numeric | |
6033 | version should be used instead. | |
16070b82 | 6034 | |
dd629d5b GS |
6035 | use v5.6.1; # compile time version check |
6036 | use 5.6.1; # ditto | |
3b825e41 | 6037 | use 5.006_001; # ditto; preferred for backwards compatibility |
16070b82 GS |
6038 | |
6039 | This is often useful if you need to check the current Perl version before | |
6040 | C<use>ing library modules that have changed in incompatible ways from | |
6041 | older versions of Perl. (We try not to do this more than we have to.) | |
da0045b7 | 6042 | |
19799a22 | 6043 | The C<BEGIN> forces the C<require> and C<import> to happen at compile time. The |
7660c0ab | 6044 | C<require> makes sure the module is loaded into memory if it hasn't been |
19799a22 GS |
6045 | yet. The C<import> is not a builtin--it's just an ordinary static method |
6046 | call into the C<Module> package to tell the module to import the list of | |
a0d0e21e | 6047 | features back into the current package. The module can implement its |
19799a22 GS |
6048 | C<import> method any way it likes, though most modules just choose to |
6049 | derive their C<import> method via inheritance from the C<Exporter> class that | |
6050 | is defined in the C<Exporter> module. See L<Exporter>. If no C<import> | |
10696ff6 | 6051 | method can be found then the call is skipped. |
cb1a09d0 | 6052 | |
31686daf JP |
6053 | If you do not want to call the package's C<import> method (for instance, |
6054 | to stop your namespace from being altered), explicitly supply the empty list: | |
cb1a09d0 AD |
6055 | |
6056 | use Module (); | |
6057 | ||
6058 | That is exactly equivalent to | |
6059 | ||
5a964f20 | 6060 | BEGIN { require Module } |
a0d0e21e | 6061 | |
da0045b7 | 6062 | If the VERSION argument is present between Module and LIST, then the |
71be2cbc | 6063 | C<use> will call the VERSION method in class Module with the given |
6064 | version as an argument. The default VERSION method, inherited from | |
44dcb63b | 6065 | the UNIVERSAL class, croaks if the given version is larger than the |
b76cc8ba | 6066 | value of the variable C<$Module::VERSION>. |
f6c8478c GS |
6067 | |
6068 | Again, there is a distinction between omitting LIST (C<import> called | |
6069 | with no arguments) and an explicit empty LIST C<()> (C<import> not | |
6070 | called). Note that there is no comma after VERSION! | |
da0045b7 | 6071 | |
a0d0e21e LW |
6072 | Because this is a wide-open interface, pragmas (compiler directives) |
6073 | are also implemented this way. Currently implemented pragmas are: | |
6074 | ||
f3798619 | 6075 | use constant; |
4633a7c4 | 6076 | use diagnostics; |
f3798619 | 6077 | use integer; |
4438c4b7 JH |
6078 | use sigtrap qw(SEGV BUS); |
6079 | use strict qw(subs vars refs); | |
6080 | use subs qw(afunc blurfl); | |
6081 | use warnings qw(all); | |
58c7fc7c | 6082 | use sort qw(stable _quicksort _mergesort); |
a0d0e21e | 6083 | |
19799a22 | 6084 | Some of these pseudo-modules import semantics into the current |
5a964f20 TC |
6085 | block scope (like C<strict> or C<integer>, unlike ordinary modules, |
6086 | which import symbols into the current package (which are effective | |
6087 | through the end of the file). | |
a0d0e21e | 6088 | |
19799a22 GS |
6089 | There's a corresponding C<no> command that unimports meanings imported |
6090 | by C<use>, i.e., it calls C<unimport Module LIST> instead of C<import>. | |
a0d0e21e LW |
6091 | |
6092 | no integer; | |
6093 | no strict 'refs'; | |
4438c4b7 | 6094 | no warnings; |
a0d0e21e | 6095 | |
ac634a9a | 6096 | See L<perlmodlib> for a list of standard modules and pragmas. See L<perlrun> |
31686daf JP |
6097 | for the C<-M> and C<-m> command-line options to perl that give C<use> |
6098 | functionality from the command-line. | |
a0d0e21e LW |
6099 | |
6100 | =item utime LIST | |
6101 | ||
6102 | Changes the access and modification times on each file of a list of | |
6103 | files. The first two elements of the list must be the NUMERICAL access | |
6104 | and modification times, in that order. Returns the number of files | |
46cdf678 | 6105 | successfully changed. The inode change time of each file is set |
19799a22 | 6106 | to the current time. This code has the same effect as the C<touch> |
a3cb178b | 6107 | command if the files already exist: |
a0d0e21e LW |
6108 | |
6109 | #!/usr/bin/perl | |
6110 | $now = time; | |
6111 | utime $now, $now, @ARGV; | |
6112 | ||
c6f7b413 RS |
6113 | If the first two elements of the list are C<undef>, then the utime(2) |
6114 | function in the C library will be called with a null second argument. | |
6115 | On most systems, this will set the file's access and modification | |
6116 | times to the current time. (i.e. equivalent to the example above.) | |
6117 | ||
6118 | utime undef, undef, @ARGV; | |
6119 | ||
aa689395 | 6120 | =item values HASH |
a0d0e21e | 6121 | |
1d2dff63 GS |
6122 | Returns a list consisting of all the values of the named hash. (In a |
6123 | scalar context, returns the number of values.) The values are | |
ab192400 GS |
6124 | returned in an apparently random order. The actual random order is |
6125 | subject to change in future versions of perl, but it is guaranteed to | |
19799a22 | 6126 | be the same order as either the C<keys> or C<each> function would |
ab192400 GS |
6127 | produce on the same (unmodified) hash. |
6128 | ||
8ea1e5d4 GS |
6129 | Note that the values are not copied, which means modifying them will |
6130 | modify the contents of the hash: | |
2b5ab1e7 | 6131 | |
8ea1e5d4 GS |
6132 | for (values %hash) { s/foo/bar/g } # modifies %hash values |
6133 | for (@hash{keys %hash}) { s/foo/bar/g } # same | |
2b5ab1e7 TC |
6134 | |
6135 | As a side effect, calling values() resets the HASH's internal iterator. | |
19799a22 | 6136 | See also C<keys>, C<each>, and C<sort>. |
a0d0e21e LW |
6137 | |
6138 | =item vec EXPR,OFFSET,BITS | |
6139 | ||
e69129f1 GS |
6140 | Treats the string in EXPR as a bit vector made up of elements of |
6141 | width BITS, and returns the value of the element specified by OFFSET | |
6142 | as an unsigned integer. BITS therefore specifies the number of bits | |
6143 | that are reserved for each element in the bit vector. This must | |
6144 | be a power of two from 1 to 32 (or 64, if your platform supports | |
6145 | that). | |
c5a0f51a | 6146 | |
b76cc8ba | 6147 | If BITS is 8, "elements" coincide with bytes of the input string. |
c73032f5 IZ |
6148 | |
6149 | If BITS is 16 or more, bytes of the input string are grouped into chunks | |
6150 | of size BITS/8, and each group is converted to a number as with | |
b1866b2d | 6151 | pack()/unpack() with big-endian formats C<n>/C<N> (and analogously |
c73032f5 IZ |
6152 | for BITS==64). See L<"pack"> for details. |
6153 | ||
6154 | If bits is 4 or less, the string is broken into bytes, then the bits | |
6155 | of each byte are broken into 8/BITS groups. Bits of a byte are | |
6156 | numbered in a little-endian-ish way, as in C<0x01>, C<0x02>, | |
6157 | C<0x04>, C<0x08>, C<0x10>, C<0x20>, C<0x40>, C<0x80>. For example, | |
6158 | breaking the single input byte C<chr(0x36)> into two groups gives a list | |
6159 | C<(0x6, 0x3)>; breaking it into 4 groups gives C<(0x2, 0x1, 0x3, 0x0)>. | |
6160 | ||
81e118e0 JH |
6161 | C<vec> may also be assigned to, in which case parentheses are needed |
6162 | to give the expression the correct precedence as in | |
22dc801b | 6163 | |
6164 | vec($image, $max_x * $x + $y, 8) = 3; | |
a0d0e21e | 6165 | |
fe58ced6 MG |
6166 | If the selected element is outside the string, the value 0 is returned. |
6167 | If an element off the end of the string is written to, Perl will first | |
6168 | extend the string with sufficiently many zero bytes. It is an error | |
6169 | to try to write off the beginning of the string (i.e. negative OFFSET). | |
fac70343 | 6170 | |
33b45480 SB |
6171 | The string should not contain any character with the value > 255 (which |
6172 | can only happen if you're using UTF8 encoding). If it does, it will be | |
6173 | treated as something which is not UTF8 encoded. When the C<vec> was | |
6174 | assigned to, other parts of your program will also no longer consider the | |
6175 | string to be UTF8 encoded. In other words, if you do have such characters | |
6176 | in your string, vec() will operate on the actual byte string, and not the | |
6177 | conceptual character string. | |
246fae53 | 6178 | |
fac70343 GS |
6179 | Strings created with C<vec> can also be manipulated with the logical |
6180 | operators C<|>, C<&>, C<^>, and C<~>. These operators will assume a bit | |
6181 | vector operation is desired when both operands are strings. | |
c5a0f51a | 6182 | See L<perlop/"Bitwise String Operators">. |
a0d0e21e | 6183 | |
7660c0ab | 6184 | The following code will build up an ASCII string saying C<'PerlPerlPerl'>. |
19799a22 | 6185 | The comments show the string after each step. Note that this code works |
cca87523 GS |
6186 | in the same way on big-endian or little-endian machines. |
6187 | ||
6188 | my $foo = ''; | |
6189 | vec($foo, 0, 32) = 0x5065726C; # 'Perl' | |
e69129f1 GS |
6190 | |
6191 | # $foo eq "Perl" eq "\x50\x65\x72\x6C", 32 bits | |
6192 | print vec($foo, 0, 8); # prints 80 == 0x50 == ord('P') | |
6193 | ||
cca87523 GS |
6194 | vec($foo, 2, 16) = 0x5065; # 'PerlPe' |
6195 | vec($foo, 3, 16) = 0x726C; # 'PerlPerl' | |
6196 | vec($foo, 8, 8) = 0x50; # 'PerlPerlP' | |
6197 | vec($foo, 9, 8) = 0x65; # 'PerlPerlPe' | |
6198 | vec($foo, 20, 4) = 2; # 'PerlPerlPe' . "\x02" | |
f86cebdf GS |
6199 | vec($foo, 21, 4) = 7; # 'PerlPerlPer' |
6200 | # 'r' is "\x72" | |
cca87523 GS |
6201 | vec($foo, 45, 2) = 3; # 'PerlPerlPer' . "\x0c" |
6202 | vec($foo, 93, 1) = 1; # 'PerlPerlPer' . "\x2c" | |
f86cebdf GS |
6203 | vec($foo, 94, 1) = 1; # 'PerlPerlPerl' |
6204 | # 'l' is "\x6c" | |
cca87523 | 6205 | |
19799a22 | 6206 | To transform a bit vector into a string or list of 0's and 1's, use these: |
a0d0e21e LW |
6207 | |
6208 | $bits = unpack("b*", $vector); | |
6209 | @bits = split(//, unpack("b*", $vector)); | |
6210 | ||
7660c0ab | 6211 | If you know the exact length in bits, it can be used in place of the C<*>. |
a0d0e21e | 6212 | |
e69129f1 GS |
6213 | Here is an example to illustrate how the bits actually fall in place: |
6214 | ||
6215 | #!/usr/bin/perl -wl | |
6216 | ||
6217 | print <<'EOT'; | |
b76cc8ba | 6218 | 0 1 2 3 |
e69129f1 GS |
6219 | unpack("V",$_) 01234567890123456789012345678901 |
6220 | ------------------------------------------------------------------ | |
6221 | EOT | |
6222 | ||
6223 | for $w (0..3) { | |
6224 | $width = 2**$w; | |
6225 | for ($shift=0; $shift < $width; ++$shift) { | |
6226 | for ($off=0; $off < 32/$width; ++$off) { | |
6227 | $str = pack("B*", "0"x32); | |
6228 | $bits = (1<<$shift); | |
6229 | vec($str, $off, $width) = $bits; | |
6230 | $res = unpack("b*",$str); | |
6231 | $val = unpack("V", $str); | |
6232 | write; | |
6233 | } | |
6234 | } | |
6235 | } | |
6236 | ||
6237 | format STDOUT = | |
6238 | vec($_,@#,@#) = @<< == @######### @>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> | |
6239 | $off, $width, $bits, $val, $res | |
6240 | . | |
6241 | __END__ | |
6242 | ||
6243 | Regardless of the machine architecture on which it is run, the above | |
6244 | example should print the following table: | |
6245 | ||
b76cc8ba | 6246 | 0 1 2 3 |
e69129f1 GS |
6247 | unpack("V",$_) 01234567890123456789012345678901 |
6248 | ------------------------------------------------------------------ | |
6249 | vec($_, 0, 1) = 1 == 1 10000000000000000000000000000000 | |
6250 | vec($_, 1, 1) = 1 == 2 01000000000000000000000000000000 | |
6251 | vec($_, 2, 1) = 1 == 4 00100000000000000000000000000000 | |
6252 | vec($_, 3, 1) = 1 == 8 00010000000000000000000000000000 | |
6253 | vec($_, 4, 1) = 1 == 16 00001000000000000000000000000000 | |
6254 | vec($_, 5, 1) = 1 == 32 00000100000000000000000000000000 | |
6255 | vec($_, 6, 1) = 1 == 64 00000010000000000000000000000000 | |
6256 | vec($_, 7, 1) = 1 == 128 00000001000000000000000000000000 | |
6257 | vec($_, 8, 1) = 1 == 256 00000000100000000000000000000000 | |
6258 | vec($_, 9, 1) = 1 == 512 00000000010000000000000000000000 | |
6259 | vec($_,10, 1) = 1 == 1024 00000000001000000000000000000000 | |
6260 | vec($_,11, 1) = 1 == 2048 00000000000100000000000000000000 | |
6261 | vec($_,12, 1) = 1 == 4096 00000000000010000000000000000000 | |
6262 | vec($_,13, 1) = 1 == 8192 00000000000001000000000000000000 | |
6263 | vec($_,14, 1) = 1 == 16384 00000000000000100000000000000000 | |
6264 | vec($_,15, 1) = 1 == 32768 00000000000000010000000000000000 | |
6265 | vec($_,16, 1) = 1 == 65536 00000000000000001000000000000000 | |
6266 | vec($_,17, 1) = 1 == 131072 00000000000000000100000000000000 | |
6267 | vec($_,18, 1) = 1 == 262144 00000000000000000010000000000000 | |
6268 | vec($_,19, 1) = 1 == 524288 00000000000000000001000000000000 | |
6269 | vec($_,20, 1) = 1 == 1048576 00000000000000000000100000000000 | |
6270 | vec($_,21, 1) = 1 == 2097152 00000000000000000000010000000000 | |
6271 | vec($_,22, 1) = 1 == 4194304 00000000000000000000001000000000 | |
6272 | vec($_,23, 1) = 1 == 8388608 00000000000000000000000100000000 | |
6273 | vec($_,24, 1) = 1 == 16777216 00000000000000000000000010000000 | |
6274 | vec($_,25, 1) = 1 == 33554432 00000000000000000000000001000000 | |
6275 | vec($_,26, 1) = 1 == 67108864 00000000000000000000000000100000 | |
6276 | vec($_,27, 1) = 1 == 134217728 00000000000000000000000000010000 | |
6277 | vec($_,28, 1) = 1 == 268435456 00000000000000000000000000001000 | |
6278 | vec($_,29, 1) = 1 == 536870912 00000000000000000000000000000100 | |
6279 | vec($_,30, 1) = 1 == 1073741824 00000000000000000000000000000010 | |
6280 | vec($_,31, 1) = 1 == 2147483648 00000000000000000000000000000001 | |
6281 | vec($_, 0, 2) = 1 == 1 10000000000000000000000000000000 | |
6282 | vec($_, 1, 2) = 1 == 4 00100000000000000000000000000000 | |
6283 | vec($_, 2, 2) = 1 == 16 00001000000000000000000000000000 | |
6284 | vec($_, 3, 2) = 1 == 64 00000010000000000000000000000000 | |
6285 | vec($_, 4, 2) = 1 == 256 00000000100000000000000000000000 | |
6286 | vec($_, 5, 2) = 1 == 1024 00000000001000000000000000000000 | |
6287 | vec($_, 6, 2) = 1 == 4096 00000000000010000000000000000000 | |
6288 | vec($_, 7, 2) = 1 == 16384 00000000000000100000000000000000 | |
6289 | vec($_, 8, 2) = 1 == 65536 00000000000000001000000000000000 | |
6290 | vec($_, 9, 2) = 1 == 262144 00000000000000000010000000000000 | |
6291 | vec($_,10, 2) = 1 == 1048576 00000000000000000000100000000000 | |
6292 | vec($_,11, 2) = 1 == 4194304 00000000000000000000001000000000 | |
6293 | vec($_,12, 2) = 1 == 16777216 00000000000000000000000010000000 | |
6294 | vec($_,13, 2) = 1 == 67108864 00000000000000000000000000100000 | |
6295 | vec($_,14, 2) = 1 == 268435456 00000000000000000000000000001000 | |
6296 | vec($_,15, 2) = 1 == 1073741824 00000000000000000000000000000010 | |
6297 | vec($_, 0, 2) = 2 == 2 01000000000000000000000000000000 | |
6298 | vec($_, 1, 2) = 2 == 8 00010000000000000000000000000000 | |
6299 | vec($_, 2, 2) = 2 == 32 00000100000000000000000000000000 | |
6300 | vec($_, 3, 2) = 2 == 128 00000001000000000000000000000000 | |
6301 | vec($_, 4, 2) = 2 == 512 00000000010000000000000000000000 | |
6302 | vec($_, 5, 2) = 2 == 2048 00000000000100000000000000000000 | |
6303 | vec($_, 6, 2) = 2 == 8192 00000000000001000000000000000000 | |
6304 | vec($_, 7, 2) = 2 == 32768 00000000000000010000000000000000 | |
6305 | vec($_, 8, 2) = 2 == 131072 00000000000000000100000000000000 | |
6306 | vec($_, 9, 2) = 2 == 524288 00000000000000000001000000000000 | |
6307 | vec($_,10, 2) = 2 == 2097152 00000000000000000000010000000000 | |
6308 | vec($_,11, 2) = 2 == 8388608 00000000000000000000000100000000 | |
6309 | vec($_,12, 2) = 2 == 33554432 00000000000000000000000001000000 | |
6310 | vec($_,13, 2) = 2 == 134217728 00000000000000000000000000010000 | |
6311 | vec($_,14, 2) = 2 == 536870912 00000000000000000000000000000100 | |
6312 | vec($_,15, 2) = 2 == 2147483648 00000000000000000000000000000001 | |
6313 | vec($_, 0, 4) = 1 == 1 10000000000000000000000000000000 | |
6314 | vec($_, 1, 4) = 1 == 16 00001000000000000000000000000000 | |
6315 | vec($_, 2, 4) = 1 == 256 00000000100000000000000000000000 | |
6316 | vec($_, 3, 4) = 1 == 4096 00000000000010000000000000000000 | |
6317 | vec($_, 4, 4) = 1 == 65536 00000000000000001000000000000000 | |
6318 | vec($_, 5, 4) = 1 == 1048576 00000000000000000000100000000000 | |
6319 | vec($_, 6, 4) = 1 == 16777216 00000000000000000000000010000000 | |
6320 | vec($_, 7, 4) = 1 == 268435456 00000000000000000000000000001000 | |
6321 | vec($_, 0, 4) = 2 == 2 01000000000000000000000000000000 | |
6322 | vec($_, 1, 4) = 2 == 32 00000100000000000000000000000000 | |
6323 | vec($_, 2, 4) = 2 == 512 00000000010000000000000000000000 | |
6324 | vec($_, 3, 4) = 2 == 8192 00000000000001000000000000000000 | |
6325 | vec($_, 4, 4) = 2 == 131072 00000000000000000100000000000000 | |
6326 | vec($_, 5, 4) = 2 == 2097152 00000000000000000000010000000000 | |
6327 | vec($_, 6, 4) = 2 == 33554432 00000000000000000000000001000000 | |
6328 | vec($_, 7, 4) = 2 == 536870912 00000000000000000000000000000100 | |
6329 | vec($_, 0, 4) = 4 == 4 00100000000000000000000000000000 | |
6330 | vec($_, 1, 4) = 4 == 64 00000010000000000000000000000000 | |
6331 | vec($_, 2, 4) = 4 == 1024 00000000001000000000000000000000 | |
6332 | vec($_, 3, 4) = 4 == 16384 00000000000000100000000000000000 | |
6333 | vec($_, 4, 4) = 4 == 262144 00000000000000000010000000000000 | |
6334 | vec($_, 5, 4) = 4 == 4194304 00000000000000000000001000000000 | |
6335 | vec($_, 6, 4) = 4 == 67108864 00000000000000000000000000100000 | |
6336 | vec($_, 7, 4) = 4 == 1073741824 00000000000000000000000000000010 | |
6337 | vec($_, 0, 4) = 8 == 8 00010000000000000000000000000000 | |
6338 | vec($_, 1, 4) = 8 == 128 00000001000000000000000000000000 | |
6339 | vec($_, 2, 4) = 8 == 2048 00000000000100000000000000000000 | |
6340 | vec($_, 3, 4) = 8 == 32768 00000000000000010000000000000000 | |
6341 | vec($_, 4, 4) = 8 == 524288 00000000000000000001000000000000 | |
6342 | vec($_, 5, 4) = 8 == 8388608 00000000000000000000000100000000 | |
6343 | vec($_, 6, 4) = 8 == 134217728 00000000000000000000000000010000 | |
6344 | vec($_, 7, 4) = 8 == 2147483648 00000000000000000000000000000001 | |
6345 | vec($_, 0, 8) = 1 == 1 10000000000000000000000000000000 | |
6346 | vec($_, 1, 8) = 1 == 256 00000000100000000000000000000000 | |
6347 | vec($_, 2, 8) = 1 == 65536 00000000000000001000000000000000 | |
6348 | vec($_, 3, 8) = 1 == 16777216 00000000000000000000000010000000 | |
6349 | vec($_, 0, 8) = 2 == 2 01000000000000000000000000000000 | |
6350 | vec($_, 1, 8) = 2 == 512 00000000010000000000000000000000 | |
6351 | vec($_, 2, 8) = 2 == 131072 00000000000000000100000000000000 | |
6352 | vec($_, 3, 8) = 2 == 33554432 00000000000000000000000001000000 | |
6353 | vec($_, 0, 8) = 4 == 4 00100000000000000000000000000000 | |
6354 | vec($_, 1, 8) = 4 == 1024 00000000001000000000000000000000 | |
6355 | vec($_, 2, 8) = 4 == 262144 00000000000000000010000000000000 | |
6356 | vec($_, 3, 8) = 4 == 67108864 00000000000000000000000000100000 | |
6357 | vec($_, 0, 8) = 8 == 8 00010000000000000000000000000000 | |
6358 | vec($_, 1, 8) = 8 == 2048 00000000000100000000000000000000 | |
6359 | vec($_, 2, 8) = 8 == 524288 00000000000000000001000000000000 | |
6360 | vec($_, 3, 8) = 8 == 134217728 00000000000000000000000000010000 | |
6361 | vec($_, 0, 8) = 16 == 16 00001000000000000000000000000000 | |
6362 | vec($_, 1, 8) = 16 == 4096 00000000000010000000000000000000 | |
6363 | vec($_, 2, 8) = 16 == 1048576 00000000000000000000100000000000 | |
6364 | vec($_, 3, 8) = 16 == 268435456 00000000000000000000000000001000 | |
6365 | vec($_, 0, 8) = 32 == 32 00000100000000000000000000000000 | |
6366 | vec($_, 1, 8) = 32 == 8192 00000000000001000000000000000000 | |
6367 | vec($_, 2, 8) = 32 == 2097152 00000000000000000000010000000000 | |
6368 | vec($_, 3, 8) = 32 == 536870912 00000000000000000000000000000100 | |
6369 | vec($_, 0, 8) = 64 == 64 00000010000000000000000000000000 | |
6370 | vec($_, 1, 8) = 64 == 16384 00000000000000100000000000000000 | |
6371 | vec($_, 2, 8) = 64 == 4194304 00000000000000000000001000000000 | |
6372 | vec($_, 3, 8) = 64 == 1073741824 00000000000000000000000000000010 | |
6373 | vec($_, 0, 8) = 128 == 128 00000001000000000000000000000000 | |
6374 | vec($_, 1, 8) = 128 == 32768 00000000000000010000000000000000 | |
6375 | vec($_, 2, 8) = 128 == 8388608 00000000000000000000000100000000 | |
6376 | vec($_, 3, 8) = 128 == 2147483648 00000000000000000000000000000001 | |
6377 | ||
a0d0e21e LW |
6378 | =item wait |
6379 | ||
2b5ab1e7 TC |
6380 | Behaves like the wait(2) system call on your system: it waits for a child |
6381 | process to terminate and returns the pid of the deceased process, or | |
19799a22 | 6382 | C<-1> if there are no child processes. The status is returned in C<$?>. |
2b5ab1e7 TC |
6383 | Note that a return value of C<-1> could mean that child processes are |
6384 | being automatically reaped, as described in L<perlipc>. | |
a0d0e21e LW |
6385 | |
6386 | =item waitpid PID,FLAGS | |
6387 | ||
2b5ab1e7 TC |
6388 | Waits for a particular child process to terminate and returns the pid of |
6389 | the deceased process, or C<-1> if there is no such child process. On some | |
6390 | systems, a value of 0 indicates that there are processes still running. | |
6391 | The status is returned in C<$?>. If you say | |
a0d0e21e | 6392 | |
5f05dabc | 6393 | use POSIX ":sys_wait_h"; |
5a964f20 | 6394 | #... |
b76cc8ba | 6395 | do { |
2ac1ef3d | 6396 | $kid = waitpid(-1, WNOHANG); |
6506d41e | 6397 | } until $kid > 0; |
a0d0e21e | 6398 | |
2b5ab1e7 TC |
6399 | then you can do a non-blocking wait for all pending zombie processes. |
6400 | Non-blocking wait is available on machines supporting either the | |
6401 | waitpid(2) or wait4(2) system calls. However, waiting for a particular | |
6402 | pid with FLAGS of C<0> is implemented everywhere. (Perl emulates the | |
6403 | system call by remembering the status values of processes that have | |
6404 | exited but have not been harvested by the Perl script yet.) | |
a0d0e21e | 6405 | |
2b5ab1e7 TC |
6406 | Note that on some systems, a return value of C<-1> could mean that child |
6407 | processes are being automatically reaped. See L<perlipc> for details, | |
6408 | and for other examples. | |
5a964f20 | 6409 | |
a0d0e21e LW |
6410 | =item wantarray |
6411 | ||
19799a22 GS |
6412 | Returns true if the context of the currently executing subroutine is |
6413 | looking for a list value. Returns false if the context is looking | |
54310121 | 6414 | for a scalar. Returns the undefined value if the context is looking |
6415 | for no value (void context). | |
a0d0e21e | 6416 | |
54310121 | 6417 | return unless defined wantarray; # don't bother doing more |
6418 | my @a = complex_calculation(); | |
6419 | return wantarray ? @a : "@a"; | |
a0d0e21e | 6420 | |
19799a22 GS |
6421 | This function should have been named wantlist() instead. |
6422 | ||
a0d0e21e LW |
6423 | =item warn LIST |
6424 | ||
19799a22 | 6425 | Produces a message on STDERR just like C<die>, but doesn't exit or throw |
774d564b | 6426 | an exception. |
6427 | ||
7660c0ab A |
6428 | If LIST is empty and C<$@> already contains a value (typically from a |
6429 | previous eval) that value is used after appending C<"\t...caught"> | |
19799a22 GS |
6430 | to C<$@>. This is useful for staying almost, but not entirely similar to |
6431 | C<die>. | |
43051805 | 6432 | |
7660c0ab | 6433 | If C<$@> is empty then the string C<"Warning: Something's wrong"> is used. |
43051805 | 6434 | |
774d564b | 6435 | No message is printed if there is a C<$SIG{__WARN__}> handler |
6436 | installed. It is the handler's responsibility to deal with the message | |
19799a22 | 6437 | as it sees fit (like, for instance, converting it into a C<die>). Most |
774d564b | 6438 | handlers must therefore make arrangements to actually display the |
19799a22 | 6439 | warnings that they are not prepared to deal with, by calling C<warn> |
774d564b | 6440 | again in the handler. Note that this is quite safe and will not |
6441 | produce an endless loop, since C<__WARN__> hooks are not called from | |
6442 | inside one. | |
6443 | ||
6444 | You will find this behavior is slightly different from that of | |
6445 | C<$SIG{__DIE__}> handlers (which don't suppress the error text, but can | |
19799a22 | 6446 | instead call C<die> again to change it). |
774d564b | 6447 | |
6448 | Using a C<__WARN__> handler provides a powerful way to silence all | |
6449 | warnings (even the so-called mandatory ones). An example: | |
6450 | ||
6451 | # wipe out *all* compile-time warnings | |
6452 | BEGIN { $SIG{'__WARN__'} = sub { warn $_[0] if $DOWARN } } | |
6453 | my $foo = 10; | |
6454 | my $foo = 20; # no warning about duplicate my $foo, | |
6455 | # but hey, you asked for it! | |
6456 | # no compile-time or run-time warnings before here | |
6457 | $DOWARN = 1; | |
6458 | ||
6459 | # run-time warnings enabled after here | |
6460 | warn "\$foo is alive and $foo!"; # does show up | |
6461 | ||
6462 | See L<perlvar> for details on setting C<%SIG> entries, and for more | |
2b5ab1e7 TC |
6463 | examples. See the Carp module for other kinds of warnings using its |
6464 | carp() and cluck() functions. | |
a0d0e21e LW |
6465 | |
6466 | =item write FILEHANDLE | |
6467 | ||
6468 | =item write EXPR | |
6469 | ||
6470 | =item write | |
6471 | ||
5a964f20 | 6472 | Writes a formatted record (possibly multi-line) to the specified FILEHANDLE, |
a0d0e21e | 6473 | using the format associated with that file. By default the format for |
54310121 | 6474 | a file is the one having the same name as the filehandle, but the |
19799a22 | 6475 | format for the current output channel (see the C<select> function) may be set |
184e9718 | 6476 | explicitly by assigning the name of the format to the C<$~> variable. |
a0d0e21e LW |
6477 | |
6478 | Top of form processing is handled automatically: if there is | |
6479 | insufficient room on the current page for the formatted record, the | |
6480 | page is advanced by writing a form feed, a special top-of-page format | |
6481 | is used to format the new page header, and then the record is written. | |
6482 | By default the top-of-page format is the name of the filehandle with | |
6483 | "_TOP" appended, but it may be dynamically set to the format of your | |
184e9718 | 6484 | choice by assigning the name to the C<$^> variable while the filehandle is |
a0d0e21e | 6485 | selected. The number of lines remaining on the current page is in |
7660c0ab | 6486 | variable C<$->, which can be set to C<0> to force a new page. |
a0d0e21e LW |
6487 | |
6488 | If FILEHANDLE is unspecified, output goes to the current default output | |
6489 | channel, which starts out as STDOUT but may be changed by the | |
19799a22 | 6490 | C<select> operator. If the FILEHANDLE is an EXPR, then the expression |
a0d0e21e LW |
6491 | is evaluated and the resulting string is used to look up the name of |
6492 | the FILEHANDLE at run time. For more on formats, see L<perlform>. | |
6493 | ||
19799a22 | 6494 | Note that write is I<not> the opposite of C<read>. Unfortunately. |
a0d0e21e LW |
6495 | |
6496 | =item y/// | |
6497 | ||
7660c0ab | 6498 | The transliteration operator. Same as C<tr///>. See L<perlop>. |
a0d0e21e LW |
6499 | |
6500 | =back |