Commit | Line | Data |
---|---|---|
a0d0e21e | 1 | =head1 NAME |
d74e8afc | 2 | X<operator> |
a0d0e21e LW |
3 | |
4 | perlop - Perl operators and precedence | |
5 | ||
d042e63d MS |
6 | =head1 DESCRIPTION |
7 | ||
ae3f7391 | 8 | In Perl, the operator determines what operation is performed, |
ba7f043c | 9 | independent of the type of the operands. For example S<C<$x + $y>> |
db691027 | 10 | is always a numeric addition, and if C<$x> or C<$y> do not contain |
ae3f7391 ML |
11 | numbers, an attempt is made to convert them to numbers first. |
12 | ||
13 | This is in contrast to many other dynamic languages, where the | |
46f8a5ea | 14 | operation is determined by the type of the first argument. It also |
ae3f7391 | 15 | means that Perl has two versions of some operators, one for numeric |
ba7f043c KW |
16 | and one for string comparison. For example S<C<$x == $y>> compares |
17 | two numbers for equality, and S<C<$x eq $y>> compares two strings. | |
ae3f7391 ML |
18 | |
19 | There are a few exceptions though: C<x> can be either string | |
20 | repetition or list repetition, depending on the type of the left | |
0b55efd7 | 21 | operand, and C<&>, C<|>, C<^> and C<~> can be either string or numeric bit |
ae3f7391 ML |
22 | operations. |
23 | ||
89d205f2 | 24 | =head2 Operator Precedence and Associativity |
d74e8afc | 25 | X<operator, precedence> X<precedence> X<associativity> |
d042e63d MS |
26 | |
27 | Operator precedence and associativity work in Perl more or less like | |
28 | they do in mathematics. | |
29 | ||
30 | I<Operator precedence> means some operators are evaluated before | |
ba7f043c KW |
31 | others. For example, in S<C<2 + 4 * 5>>, the multiplication has higher |
32 | precedence so S<C<4 * 5>> is evaluated first yielding S<C<2 + 20 == | |
33 | 22>> and not S<C<6 * 5 == 30>>. | |
d042e63d MS |
34 | |
35 | I<Operator associativity> defines what happens if a sequence of the | |
36 | same operators is used one after another: whether the evaluator will | |
ba7f043c KW |
37 | evaluate the left operations first, or the right first. For example, in |
38 | S<C<8 - 4 - 2>>, subtraction is left associative so Perl evaluates the | |
39 | expression left to right. S<C<8 - 4>> is evaluated first making the | |
40 | expression S<C<4 - 2 == 2>> and not S<C<8 - 2 == 6>>. | |
a0d0e21e LW |
41 | |
42 | Perl operators have the following associativity and precedence, | |
19799a22 GS |
43 | listed from highest precedence to lowest. Operators borrowed from |
44 | C keep the same precedence relationship with each other, even where | |
45 | C's precedence is slightly screwy. (This makes learning Perl easier | |
46 | for C folks.) With very few exceptions, these all operate on scalar | |
47 | values only, not array values. | |
a0d0e21e LW |
48 | |
49 | left terms and list operators (leftward) | |
50 | left -> | |
51 | nonassoc ++ -- | |
52 | right ** | |
53 | right ! ~ \ and unary + and - | |
54310121 | 54 | left =~ !~ |
a0d0e21e LW |
55 | left * / % x |
56 | left + - . | |
57 | left << >> | |
58 | nonassoc named unary operators | |
59 | nonassoc < > <= >= lt gt le ge | |
0d863452 | 60 | nonassoc == != <=> eq ne cmp ~~ |
a0d0e21e LW |
61 | left & |
62 | left | ^ | |
63 | left && | |
c963b151 | 64 | left || // |
137443ea | 65 | nonassoc .. ... |
a0d0e21e | 66 | right ?: |
2ba1f20a | 67 | right = += -= *= etc. goto last next redo dump |
a0d0e21e LW |
68 | left , => |
69 | nonassoc list operators (rightward) | |
a5f75d66 | 70 | right not |
a0d0e21e | 71 | left and |
f23102e2 | 72 | left or xor |
a0d0e21e | 73 | |
3df91f1a DM |
74 | In the following sections, these operators are covered in detail, in the |
75 | same order in which they appear in the table above. | |
a0d0e21e | 76 | |
5a964f20 TC |
77 | Many operators can be overloaded for objects. See L<overload>. |
78 | ||
a0d0e21e | 79 | =head2 Terms and List Operators (Leftward) |
d74e8afc | 80 | X<list operator> X<operator, list> X<term> |
a0d0e21e | 81 | |
62c18ce2 | 82 | A TERM has the highest precedence in Perl. They include variables, |
5f05dabc | 83 | quote and quote-like operators, any expression in parentheses, |
a0d0e21e LW |
84 | and any function whose arguments are parenthesized. Actually, there |
85 | aren't really functions in this sense, just list operators and unary | |
86 | operators behaving as functions because you put parentheses around | |
87 | the arguments. These are all documented in L<perlfunc>. | |
88 | ||
ba7f043c | 89 | If any list operator (C<print()>, etc.) or any unary operator (C<chdir()>, etc.) |
a0d0e21e LW |
90 | is followed by a left parenthesis as the next token, the operator and |
91 | arguments within parentheses are taken to be of highest precedence, | |
92 | just like a normal function call. | |
93 | ||
94 | In the absence of parentheses, the precedence of list operators such as | |
95 | C<print>, C<sort>, or C<chmod> is either very high or very low depending on | |
54310121 | 96 | whether you are looking at the left side or the right side of the operator. |
a0d0e21e LW |
97 | For example, in |
98 | ||
99 | @ary = (1, 3, sort 4, 2); | |
100 | print @ary; # prints 1324 | |
101 | ||
ba7f043c | 102 | the commas on the right of the C<sort> are evaluated before the C<sort>, |
19799a22 GS |
103 | but the commas on the left are evaluated after. In other words, |
104 | list operators tend to gobble up all arguments that follow, and | |
a0d0e21e | 105 | then act like a simple TERM with regard to the preceding expression. |
19799a22 | 106 | Be careful with parentheses: |
a0d0e21e LW |
107 | |
108 | # These evaluate exit before doing the print: | |
109 | print($foo, exit); # Obviously not what you want. | |
110 | print $foo, exit; # Nor is this. | |
111 | ||
112 | # These do the print before evaluating exit: | |
113 | (print $foo), exit; # This is what you want. | |
114 | print($foo), exit; # Or this. | |
115 | print ($foo), exit; # Or even this. | |
116 | ||
117 | Also note that | |
118 | ||
119 | print ($foo & 255) + 1, "\n"; | |
120 | ||
d042e63d MS |
121 | probably doesn't do what you expect at first glance. The parentheses |
122 | enclose the argument list for C<print> which is evaluated (printing | |
ba7f043c | 123 | the result of S<C<$foo & 255>>). Then one is added to the return value |
d042e63d MS |
124 | of C<print> (usually 1). The result is something like this: |
125 | ||
126 | 1 + 1, "\n"; # Obviously not what you meant. | |
127 | ||
128 | To do what you meant properly, you must write: | |
129 | ||
130 | print(($foo & 255) + 1, "\n"); | |
131 | ||
5a0de581 | 132 | See L</Named Unary Operators> for more discussion of this. |
a0d0e21e | 133 | |
ba7f043c | 134 | Also parsed as terms are the S<C<do {}>> and S<C<eval {}>> constructs, as |
54310121 | 135 | well as subroutine and method calls, and the anonymous |
a0d0e21e LW |
136 | constructors C<[]> and C<{}>. |
137 | ||
5a0de581 | 138 | See also L</Quote and Quote-like Operators> toward the end of this section, |
da87341d | 139 | as well as L</"I/O Operators">. |
a0d0e21e LW |
140 | |
141 | =head2 The Arrow Operator | |
d74e8afc | 142 | X<arrow> X<dereference> X<< -> >> |
a0d0e21e | 143 | |
35f2feb0 | 144 | "C<< -> >>" is an infix dereference operator, just as it is in C |
19799a22 GS |
145 | and C++. If the right side is either a C<[...]>, C<{...}>, or a |
146 | C<(...)> subscript, then the left side must be either a hard or | |
147 | symbolic reference to an array, a hash, or a subroutine respectively. | |
148 | (Or technically speaking, a location capable of holding a hard | |
149 | reference, if it's an array or hash reference being used for | |
150 | assignment.) See L<perlreftut> and L<perlref>. | |
a0d0e21e | 151 | |
19799a22 GS |
152 | Otherwise, the right side is a method name or a simple scalar |
153 | variable containing either the method name or a subroutine reference, | |
154 | and the left side must be either an object (a blessed reference) | |
155 | or a class name (that is, a package name). See L<perlobj>. | |
a0d0e21e | 156 | |
821361b6 | 157 | The dereferencing cases (as opposed to method-calling cases) are |
2ad792cd | 158 | somewhat extended by the C<postderef> feature. For the |
821361b6 RS |
159 | details of that feature, consult L<perlref/Postfix Dereference Syntax>. |
160 | ||
5f05dabc | 161 | =head2 Auto-increment and Auto-decrement |
d74e8afc | 162 | X<increment> X<auto-increment> X<++> X<decrement> X<auto-decrement> X<--> |
a0d0e21e | 163 | |
ba7f043c | 164 | C<"++"> and C<"--"> work as in C. That is, if placed before a variable, |
d042e63d MS |
165 | they increment or decrement the variable by one before returning the |
166 | value, and if placed after, increment or decrement after returning the | |
167 | value. | |
168 | ||
169 | $i = 0; $j = 0; | |
170 | print $i++; # prints 0 | |
171 | print ++$j; # prints 1 | |
a0d0e21e | 172 | |
b033823e | 173 | Note that just as in C, Perl doesn't define B<when> the variable is |
46f8a5ea FC |
174 | incremented or decremented. You just know it will be done sometime |
175 | before or after the value is returned. This also means that modifying | |
c543c01b | 176 | a variable twice in the same statement will lead to undefined behavior. |
b033823e A |
177 | Avoid statements like: |
178 | ||
179 | $i = $i ++; | |
180 | print ++ $i + $i ++; | |
181 | ||
182 | Perl will not guarantee what the result of the above statements is. | |
183 | ||
54310121 | 184 | The auto-increment operator has a little extra builtin magic to it. If |
a0d0e21e LW |
185 | you increment a variable that is numeric, or that has ever been used in |
186 | a numeric context, you get a normal increment. If, however, the | |
5f05dabc | 187 | variable has been used in only string contexts since it was set, and |
5a964f20 | 188 | has a value that is not the empty string and matches the pattern |
9c0670e1 | 189 | C</^[a-zA-Z]*[0-9]*\z/>, the increment is done as a string, preserving each |
a0d0e21e LW |
190 | character within its range, with carry: |
191 | ||
c543c01b TC |
192 | print ++($foo = "99"); # prints "100" |
193 | print ++($foo = "a0"); # prints "a1" | |
194 | print ++($foo = "Az"); # prints "Ba" | |
195 | print ++($foo = "zz"); # prints "aaa" | |
a0d0e21e | 196 | |
6a61d433 HS |
197 | C<undef> is always treated as numeric, and in particular is changed |
198 | to C<0> before incrementing (so that a post-increment of an undef value | |
199 | will return C<0> rather than C<undef>). | |
200 | ||
5f05dabc | 201 | The auto-decrement operator is not magical. |
a0d0e21e LW |
202 | |
203 | =head2 Exponentiation | |
d74e8afc | 204 | X<**> X<exponentiation> X<power> |
a0d0e21e | 205 | |
ba7f043c KW |
206 | Binary C<"**"> is the exponentiation operator. It binds even more |
207 | tightly than unary minus, so C<-2**4> is C<-(2**4)>, not C<(-2)**4>. | |
208 | (This is | |
209 | implemented using C's C<pow(3)> function, which actually works on doubles | |
cb1a09d0 | 210 | internally.) |
a0d0e21e | 211 | |
44a465b3 JH |
212 | Note that certain exponentiation expressions are ill-defined: |
213 | these include C<0**0>, C<1**Inf>, and C<Inf**0>. Do not expect | |
214 | any particular results from these special cases, the results | |
215 | are platform-dependent. | |
216 | ||
a0d0e21e | 217 | =head2 Symbolic Unary Operators |
d74e8afc | 218 | X<unary operator> X<operator, unary> |
a0d0e21e | 219 | |
ba7f043c | 220 | Unary C<"!"> performs logical negation, that is, "not". See also C<not> for a lower |
a0d0e21e | 221 | precedence version of this. |
d74e8afc | 222 | X<!> |
a0d0e21e | 223 | |
ba7f043c | 224 | Unary C<"-"> performs arithmetic negation if the operand is numeric, |
da2f94c5 FC |
225 | including any string that looks like a number. If the operand is |
226 | an identifier, a string consisting of a minus sign concatenated | |
227 | with the identifier is returned. Otherwise, if the string starts | |
228 | with a plus or minus, a string starting with the opposite sign is | |
ba7f043c KW |
229 | returned. One effect of these rules is that C<-bareword> is equivalent |
230 | to the string C<"-bareword">. If, however, the string begins with a | |
231 | non-alphabetic character (excluding C<"+"> or C<"-">), Perl will attempt | |
232 | to convert | |
233 | the string to a numeric, and the arithmetic negation is performed. If the | |
06705523 SP |
234 | string cannot be cleanly converted to a numeric, Perl will give the warning |
235 | B<Argument "the string" isn't numeric in negation (-) at ...>. | |
d74e8afc | 236 | X<-> X<negation, arithmetic> |
a0d0e21e | 237 | |
ba7f043c | 238 | Unary C<"~"> performs bitwise negation, that is, 1's complement. For |
5a0de581 LM |
239 | example, S<C<0666 & ~027>> is 0640. (See also L</Integer Arithmetic> and |
240 | L</Bitwise String Operators>.) Note that the width of the result is | |
ba7f043c | 241 | platform-dependent: C<~0> is 32 bits wide on a 32-bit platform, but 64 |
972b05a9 | 242 | bits wide on a 64-bit platform, so if you are expecting a certain bit |
ba7f043c | 243 | width, remember to use the C<"&"> operator to mask off the excess bits. |
d74e8afc | 244 | X<~> X<negation, binary> |
a0d0e21e | 245 | |
f113cf86 TC |
246 | When complementing strings, if all characters have ordinal values under |
247 | 256, then their complements will, also. But if they do not, all | |
248 | characters will be in either 32- or 64-bit complements, depending on your | |
249 | architecture. So for example, C<~"\x{3B1}"> is C<"\x{FFFF_FC4E}"> on | |
250 | 32-bit machines and C<"\x{FFFF_FFFF_FFFF_FC4E}"> on 64-bit machines. | |
251 | ||
ba7f043c KW |
252 | If the experimental "bitwise" feature is enabled via S<C<use feature |
253 | 'bitwise'>>, then unary C<"~"> always treats its argument as a number, and an | |
254 | alternate form of the operator, C<"~.">, always treats its argument as a | |
fb7054ba FC |
255 | string. So C<~0> and C<~"0"> will both give 2**32-1 on 32-bit platforms, |
256 | whereas C<~.0> and C<~."0"> will both yield C<"\xff">. This feature | |
ba7f043c | 257 | produces a warning unless you use S<C<no warnings 'experimental::bitwise'>>. |
fb7054ba | 258 | |
ba7f043c | 259 | Unary C<"+"> has no effect whatsoever, even on strings. It is useful |
a0d0e21e LW |
260 | syntactically for separating a function name from a parenthesized expression |
261 | that would otherwise be interpreted as the complete list of function | |
a95b3d6a | 262 | arguments. (See examples above under L</Terms and List Operators (Leftward)>.) |
d74e8afc | 263 | X<+> |
a0d0e21e | 264 | |
ba7f043c | 265 | Unary C<"\"> creates a reference to whatever follows it. See L<perlreftut> |
19799a22 GS |
266 | and L<perlref>. Do not confuse this behavior with the behavior of |
267 | backslash within a string, although both forms do convey the notion | |
268 | of protecting the next thing from interpolation. | |
d74e8afc | 269 | X<\> X<reference> X<backslash> |
a0d0e21e LW |
270 | |
271 | =head2 Binding Operators | |
d74e8afc | 272 | X<binding> X<operator, binding> X<=~> X<!~> |
a0d0e21e | 273 | |
ba7f043c KW |
274 | Binary C<"=~"> binds a scalar expression to a pattern match. Certain operations |
275 | search or modify the string C<$_> by default. This operator makes that kind | |
cb1a09d0 | 276 | of operation work on some other string. The right argument is a search |
2c268ad5 TP |
277 | pattern, substitution, or transliteration. The left argument is what is |
278 | supposed to be searched, substituted, or transliterated instead of the default | |
ba7f043c KW |
279 | C<$_>. When used in scalar context, the return value generally indicates the |
280 | success of the operation. The exceptions are substitution (C<s///>) | |
281 | and transliteration (C<y///>) with the C</r> (non-destructive) option, | |
8ff32507 FC |
282 | which cause the B<r>eturn value to be the result of the substitution. |
283 | Behavior in list context depends on the particular operator. | |
000c65fc DG |
284 | See L</"Regexp Quote-Like Operators"> for details and L<perlretut> for |
285 | examples using these operators. | |
f8bab1e9 GS |
286 | |
287 | If the right argument is an expression rather than a search pattern, | |
2c268ad5 | 288 | substitution, or transliteration, it is interpreted as a search pattern at run |
46f8a5ea FC |
289 | time. Note that this means that its |
290 | contents will be interpolated twice, so | |
89d205f2 | 291 | |
1ca345ed | 292 | '\\' =~ q'\\'; |
89d205f2 YO |
293 | |
294 | is not ok, as the regex engine will end up trying to compile the | |
295 | pattern C<\>, which it will consider a syntax error. | |
a0d0e21e | 296 | |
ba7f043c | 297 | Binary C<"!~"> is just like C<"=~"> except the return value is negated in |
a0d0e21e LW |
298 | the logical sense. |
299 | ||
ba7f043c KW |
300 | Binary C<"!~"> with a non-destructive substitution (C<s///r>) or transliteration |
301 | (C<y///r>) is a syntax error. | |
4f4d7508 | 302 | |
a0d0e21e | 303 | =head2 Multiplicative Operators |
d74e8afc | 304 | X<operator, multiplicative> |
a0d0e21e | 305 | |
ba7f043c | 306 | Binary C<"*"> multiplies two numbers. |
d74e8afc | 307 | X<*> |
a0d0e21e | 308 | |
ba7f043c | 309 | Binary C<"/"> divides two numbers. |
d74e8afc | 310 | X</> X<slash> |
a0d0e21e | 311 | |
ba7f043c | 312 | Binary C<"%"> is the modulo operator, which computes the division |
f7918450 KW |
313 | remainder of its first argument with respect to its second argument. |
314 | Given integer | |
ba7f043c | 315 | operands C<$m> and C<$n>: If C<$n> is positive, then S<C<$m % $n>> is |
db691027 | 316 | C<$m> minus the largest multiple of C<$n> less than or equal to |
ba7f043c | 317 | C<$m>. If C<$n> is negative, then S<C<$m % $n>> is C<$m> minus the |
db691027 | 318 | smallest multiple of C<$n> that is not less than C<$m> (that is, the |
89b4f0ad | 319 | result will be less than or equal to zero). If the operands |
db691027 | 320 | C<$m> and C<$n> are floating point values and the absolute value of |
ba7f043c | 321 | C<$n> (that is C<abs($n)>) is less than S<C<(UV_MAX + 1)>>, only |
db691027 | 322 | the integer portion of C<$m> and C<$n> will be used in the operation |
4848a83b | 323 | (Note: here C<UV_MAX> means the maximum of the unsigned integer type). |
db691027 | 324 | If the absolute value of the right operand (C<abs($n)>) is greater than |
ba7f043c KW |
325 | or equal to S<C<(UV_MAX + 1)>>, C<"%"> computes the floating-point remainder |
326 | C<$r> in the equation S<C<($r = $m - $i*$n)>> where C<$i> is a certain | |
f7918450 | 327 | integer that makes C<$r> have the same sign as the right operand |
db691027 SF |
328 | C<$n> (B<not> as the left operand C<$m> like C function C<fmod()>) |
329 | and the absolute value less than that of C<$n>. | |
ba7f043c | 330 | Note that when S<C<use integer>> is in scope, C<"%"> gives you direct access |
f7918450 | 331 | to the modulo operator as implemented by your C compiler. This |
55d729e4 GS |
332 | operator is not as well defined for negative operands, but it will |
333 | execute faster. | |
f7918450 | 334 | X<%> X<remainder> X<modulo> X<mod> |
55d729e4 | 335 | |
ba7f043c | 336 | Binary C<"x"> is the repetition operator. In scalar context or if the left |
62d10b70 GS |
337 | operand is not enclosed in parentheses, it returns a string consisting |
338 | of the left operand repeated the number of times specified by the right | |
339 | operand. In list context, if the left operand is enclosed in | |
ba7f043c | 340 | parentheses or is a list formed by C<qw/I<STRING>/>, it repeats the list. |
31201a8e KW |
341 | If the right operand is zero or negative (raising a warning on |
342 | negative), it returns an empty string | |
3585017f | 343 | or an empty list, depending on the context. |
d74e8afc | 344 | X<x> |
a0d0e21e LW |
345 | |
346 | print '-' x 80; # print row of dashes | |
347 | ||
348 | print "\t" x ($tab/8), ' ' x ($tab%8); # tab over | |
349 | ||
350 | @ones = (1) x 80; # a list of 80 1's | |
351 | @ones = (5) x @ones; # set all elements to 5 | |
352 | ||
353 | ||
354 | =head2 Additive Operators | |
d74e8afc | 355 | X<operator, additive> |
a0d0e21e | 356 | |
ba7f043c | 357 | Binary C<"+"> returns the sum of two numbers. |
d74e8afc | 358 | X<+> |
a0d0e21e | 359 | |
ba7f043c | 360 | Binary C<"-"> returns the difference of two numbers. |
d74e8afc | 361 | X<-> |
a0d0e21e | 362 | |
ba7f043c | 363 | Binary C<"."> concatenates two strings. |
d74e8afc ITB |
364 | X<string, concatenation> X<concatenation> |
365 | X<cat> X<concat> X<concatenate> X<.> | |
a0d0e21e LW |
366 | |
367 | =head2 Shift Operators | |
d74e8afc ITB |
368 | X<shift operator> X<operator, shift> X<<< << >>> |
369 | X<<< >> >>> X<right shift> X<left shift> X<bitwise shift> | |
370 | X<shl> X<shr> X<shift, right> X<shift, left> | |
a0d0e21e | 371 | |
ba7f043c | 372 | Binary C<<< "<<" >>> returns the value of its left argument shifted left by the |
55497cff | 373 | number of bits specified by the right argument. Arguments should be |
5a0de581 | 374 | integers. (See also L</Integer Arithmetic>.) |
a0d0e21e | 375 | |
ba7f043c | 376 | Binary C<<< ">>" >>> returns the value of its left argument shifted right by |
55497cff | 377 | the number of bits specified by the right argument. Arguments should |
5a0de581 | 378 | be integers. (See also L</Integer Arithmetic>.) |
a0d0e21e | 379 | |
5a0de581 | 380 | If S<C<use integer>> (see L</Integer Arithmetic>) is in force then |
a63df121 JH |
381 | signed C integers are used (I<arithmetic shift>), otherwise unsigned C |
382 | integers are used (I<logical shift>), even for negative shiftees. | |
383 | In arithmetic right shift the sign bit is replicated on the left, | |
384 | in logical shift zero bits come in from the left. | |
385 | ||
386 | Either way, the implementation isn't going to generate results larger | |
387 | than the size of the integer type Perl was built with (32 bits or 64 bits). | |
388 | ||
389 | Shifting by negative number of bits means the reverse shift: left | |
390 | shift becomes right shift, right shift becomes left shift. This is | |
391 | unlike in C, where negative shift is undefined. | |
392 | ||
393 | Shifting by more bits than the size of the integers means most of the | |
394 | time zero (all bits fall off), except that under S<C<use integer>> | |
395 | right overshifting a negative shiftee results in -1. This is unlike | |
396 | in C, where shifting by too many bits is undefined. A common C | |
397 | behavior is "shift by modulo wordbits", so that for example | |
398 | ||
399 | 1 >> 64 == 1 >> (64 % 64) == 1 >> 0 == 1 # Common C behavior. | |
400 | ||
401 | but that is completely accidental. | |
b16cf6df | 402 | |
1ca345ed | 403 | If you get tired of being subject to your platform's native integers, |
ba7f043c | 404 | the S<C<use bigint>> pragma neatly sidesteps the issue altogether: |
1ca345ed TC |
405 | |
406 | print 20 << 20; # 20971520 | |
407 | print 20 << 40; # 5120 on 32-bit machines, | |
408 | # 21990232555520 on 64-bit machines | |
409 | use bigint; | |
410 | print 20 << 100; # 25353012004564588029934064107520 | |
411 | ||
a0d0e21e | 412 | =head2 Named Unary Operators |
d74e8afc | 413 | X<operator, named unary> |
a0d0e21e LW |
414 | |
415 | The various named unary operators are treated as functions with one | |
568e6d8b | 416 | argument, with optional parentheses. |
a0d0e21e | 417 | |
ba7f043c | 418 | If any list operator (C<print()>, etc.) or any unary operator (C<chdir()>, etc.) |
a0d0e21e LW |
419 | is followed by a left parenthesis as the next token, the operator and |
420 | arguments within parentheses are taken to be of highest precedence, | |
3981b0eb | 421 | just like a normal function call. For example, |
1ca345ed | 422 | because named unary operators are higher precedence than C<||>: |
a0d0e21e LW |
423 | |
424 | chdir $foo || die; # (chdir $foo) || die | |
425 | chdir($foo) || die; # (chdir $foo) || die | |
426 | chdir ($foo) || die; # (chdir $foo) || die | |
427 | chdir +($foo) || die; # (chdir $foo) || die | |
428 | ||
ba7f043c | 429 | but, because C<"*"> is higher precedence than named operators: |
a0d0e21e LW |
430 | |
431 | chdir $foo * 20; # chdir ($foo * 20) | |
432 | chdir($foo) * 20; # (chdir $foo) * 20 | |
433 | chdir ($foo) * 20; # (chdir $foo) * 20 | |
434 | chdir +($foo) * 20; # chdir ($foo * 20) | |
435 | ||
436 | rand 10 * 20; # rand (10 * 20) | |
437 | rand(10) * 20; # (rand 10) * 20 | |
438 | rand (10) * 20; # (rand 10) * 20 | |
439 | rand +(10) * 20; # rand (10 * 20) | |
440 | ||
568e6d8b RGS |
441 | Regarding precedence, the filetest operators, like C<-f>, C<-M>, etc. are |
442 | treated like named unary operators, but they don't follow this functional | |
443 | parenthesis rule. That means, for example, that C<-f($file).".bak"> is | |
ba7f043c | 444 | equivalent to S<C<-f "$file.bak">>. |
d74e8afc | 445 | X<-X> X<filetest> X<operator, filetest> |
568e6d8b | 446 | |
5a0de581 | 447 | See also L</"Terms and List Operators (Leftward)">. |
a0d0e21e LW |
448 | |
449 | =head2 Relational Operators | |
d74e8afc | 450 | X<relational operator> X<operator, relational> |
a0d0e21e | 451 | |
1ca345ed TC |
452 | Perl operators that return true or false generally return values |
453 | that can be safely used as numbers. For example, the relational | |
454 | operators in this section and the equality operators in the next | |
455 | one return C<1> for true and a special version of the defined empty | |
456 | string, C<"">, which counts as a zero but is exempt from warnings | |
ba7f043c | 457 | about improper numeric conversions, just as S<C<"0 but true">> is. |
1ca345ed | 458 | |
ba7f043c | 459 | Binary C<< "<" >> returns true if the left argument is numerically less than |
a0d0e21e | 460 | the right argument. |
d74e8afc | 461 | X<< < >> |
a0d0e21e | 462 | |
ba7f043c | 463 | Binary C<< ">" >> returns true if the left argument is numerically greater |
a0d0e21e | 464 | than the right argument. |
d74e8afc | 465 | X<< > >> |
a0d0e21e | 466 | |
ba7f043c | 467 | Binary C<< "<=" >> returns true if the left argument is numerically less than |
a0d0e21e | 468 | or equal to the right argument. |
d74e8afc | 469 | X<< <= >> |
a0d0e21e | 470 | |
ba7f043c | 471 | Binary C<< ">=" >> returns true if the left argument is numerically greater |
a0d0e21e | 472 | than or equal to the right argument. |
d74e8afc | 473 | X<< >= >> |
a0d0e21e | 474 | |
ba7f043c | 475 | Binary C<"lt"> returns true if the left argument is stringwise less than |
a0d0e21e | 476 | the right argument. |
d74e8afc | 477 | X<< lt >> |
a0d0e21e | 478 | |
ba7f043c | 479 | Binary C<"gt"> returns true if the left argument is stringwise greater |
a0d0e21e | 480 | than the right argument. |
d74e8afc | 481 | X<< gt >> |
a0d0e21e | 482 | |
ba7f043c | 483 | Binary C<"le"> returns true if the left argument is stringwise less than |
a0d0e21e | 484 | or equal to the right argument. |
d74e8afc | 485 | X<< le >> |
a0d0e21e | 486 | |
ba7f043c | 487 | Binary C<"ge"> returns true if the left argument is stringwise greater |
a0d0e21e | 488 | than or equal to the right argument. |
d74e8afc | 489 | X<< ge >> |
a0d0e21e LW |
490 | |
491 | =head2 Equality Operators | |
d74e8afc | 492 | X<equality> X<equal> X<equals> X<operator, equality> |
a0d0e21e | 493 | |
ba7f043c | 494 | Binary C<< "==" >> returns true if the left argument is numerically equal to |
a0d0e21e | 495 | the right argument. |
d74e8afc | 496 | X<==> |
a0d0e21e | 497 | |
ba7f043c | 498 | Binary C<< "!=" >> returns true if the left argument is numerically not equal |
a0d0e21e | 499 | to the right argument. |
d74e8afc | 500 | X<!=> |
a0d0e21e | 501 | |
ba7f043c | 502 | Binary C<< "<=>" >> returns -1, 0, or 1 depending on whether the left |
6ee5d4e7 | 503 | argument is numerically less than, equal to, or greater than the right |
ba7f043c KW |
504 | argument. If your platform supports C<NaN>'s (not-a-numbers) as numeric |
505 | values, using them with C<< "<=>" >> returns undef. C<NaN> is not | |
506 | C<< "<" >>, C<< "==" >>, C<< ">" >>, C<< "<=" >> or C<< ">=" >> anything | |
507 | (even C<NaN>), so those 5 return false. S<C<< NaN != NaN >>> returns | |
508 | true, as does S<C<NaN !=> I<anything else>>. If your platform doesn't | |
509 | support C<NaN>'s then C<NaN> is just a string with numeric value 0. | |
510 | X<< <=> >> | |
511 | X<spaceship> | |
7d3a9d88 | 512 | |
db691027 SF |
513 | $ perl -le '$x = "NaN"; print "No NaN support here" if $x == $x' |
514 | $ perl -le '$x = "NaN"; print "NaN support here" if $x != $x' | |
1ca345ed | 515 | |
db691027 | 516 | (Note that the L<bigint>, L<bigrat>, and L<bignum> pragmas all |
ba7f043c | 517 | support C<"NaN">.) |
a0d0e21e | 518 | |
ba7f043c | 519 | Binary C<"eq"> returns true if the left argument is stringwise equal to |
a0d0e21e | 520 | the right argument. |
d74e8afc | 521 | X<eq> |
a0d0e21e | 522 | |
ba7f043c | 523 | Binary C<"ne"> returns true if the left argument is stringwise not equal |
a0d0e21e | 524 | to the right argument. |
d74e8afc | 525 | X<ne> |
a0d0e21e | 526 | |
ba7f043c | 527 | Binary C<"cmp"> returns -1, 0, or 1 depending on whether the left |
d4ad863d JH |
528 | argument is stringwise less than, equal to, or greater than the right |
529 | argument. | |
d74e8afc | 530 | X<cmp> |
a0d0e21e | 531 | |
ba7f043c | 532 | Binary C<"~~"> does a smartmatch between its arguments. Smart matching |
1ca345ed | 533 | is described in the next section. |
0d863452 RH |
534 | X<~~> |
535 | ||
ba7f043c KW |
536 | C<"lt">, C<"le">, C<"ge">, C<"gt"> and C<"cmp"> use the collation (sort) |
537 | order specified by the current C<LC_COLLATE> locale if a S<C<use | |
538 | locale>> form that includes collation is in effect. See L<perllocale>. | |
539 | Do not mix these with Unicode, | |
540 | only use them with legacy 8-bit locale encodings. | |
541 | The standard C<L<Unicode::Collate>> and | |
542 | C<L<Unicode::Collate::Locale>> modules offer much more powerful | |
543 | solutions to collation issues. | |
1ca345ed | 544 | |
82365311 DG |
545 | For case-insensitive comparisions, look at the L<perlfunc/fc> case-folding |
546 | function, available in Perl v5.16 or later: | |
547 | ||
548 | if ( fc($x) eq fc($y) ) { ... } | |
549 | ||
1ca345ed TC |
550 | =head2 Smartmatch Operator |
551 | ||
552 | First available in Perl 5.10.1 (the 5.10.0 version behaved differently), | |
553 | binary C<~~> does a "smartmatch" between its arguments. This is mostly | |
554 | used implicitly in the C<when> construct described in L<perlsyn>, although | |
555 | not all C<when> clauses call the smartmatch operator. Unique among all of | |
cc08d69f RS |
556 | Perl's operators, the smartmatch operator can recurse. The smartmatch |
557 | operator is L<experimental|perlpolicy/experimental> and its behavior is | |
558 | subject to change. | |
1ca345ed TC |
559 | |
560 | It is also unique in that all other Perl operators impose a context | |
561 | (usually string or numeric context) on their operands, autoconverting | |
562 | those operands to those imposed contexts. In contrast, smartmatch | |
563 | I<infers> contexts from the actual types of its operands and uses that | |
564 | type information to select a suitable comparison mechanism. | |
565 | ||
566 | The C<~~> operator compares its operands "polymorphically", determining how | |
567 | to compare them according to their actual types (numeric, string, array, | |
568 | hash, etc.) Like the equality operators with which it shares the same | |
569 | precedence, C<~~> returns 1 for true and C<""> for false. It is often best | |
570 | read aloud as "in", "inside of", or "is contained in", because the left | |
571 | operand is often looked for I<inside> the right operand. That makes the | |
40bec8a5 | 572 | order of the operands to the smartmatch operand often opposite that of |
1ca345ed TC |
573 | the regular match operator. In other words, the "smaller" thing is usually |
574 | placed in the left operand and the larger one in the right. | |
575 | ||
576 | The behavior of a smartmatch depends on what type of things its arguments | |
577 | are, as determined by the following table. The first row of the table | |
578 | whose types apply determines the smartmatch behavior. Because what | |
579 | actually happens is mostly determined by the type of the second operand, | |
580 | the table is sorted on the right operand instead of on the left. | |
581 | ||
582 | Left Right Description and pseudocode | |
583 | =============================================================== | |
584 | Any undef check whether Any is undefined | |
585 | like: !defined Any | |
586 | ||
587 | Any Object invoke ~~ overloading on Object, or die | |
588 | ||
589 | Right operand is an ARRAY: | |
590 | ||
591 | Left Right Description and pseudocode | |
592 | =============================================================== | |
593 | ARRAY1 ARRAY2 recurse on paired elements of ARRAY1 and ARRAY2[2] | |
594 | like: (ARRAY1[0] ~~ ARRAY2[0]) | |
595 | && (ARRAY1[1] ~~ ARRAY2[1]) && ... | |
596 | HASH ARRAY any ARRAY elements exist as HASH keys | |
597 | like: grep { exists HASH->{$_} } ARRAY | |
598 | Regexp ARRAY any ARRAY elements pattern match Regexp | |
599 | like: grep { /Regexp/ } ARRAY | |
600 | undef ARRAY undef in ARRAY | |
601 | like: grep { !defined } ARRAY | |
40bec8a5 | 602 | Any ARRAY smartmatch each ARRAY element[3] |
1ca345ed TC |
603 | like: grep { Any ~~ $_ } ARRAY |
604 | ||
605 | Right operand is a HASH: | |
606 | ||
607 | Left Right Description and pseudocode | |
608 | =============================================================== | |
609 | HASH1 HASH2 all same keys in both HASHes | |
610 | like: keys HASH1 == | |
611 | grep { exists HASH2->{$_} } keys HASH1 | |
612 | ARRAY HASH any ARRAY elements exist as HASH keys | |
613 | like: grep { exists HASH->{$_} } ARRAY | |
614 | Regexp HASH any HASH keys pattern match Regexp | |
615 | like: grep { /Regexp/ } keys HASH | |
616 | undef HASH always false (undef can't be a key) | |
617 | like: 0 == 1 | |
618 | Any HASH HASH key existence | |
619 | like: exists HASH->{Any} | |
620 | ||
621 | Right operand is CODE: | |
f703fc96 | 622 | |
1ca345ed TC |
623 | Left Right Description and pseudocode |
624 | =============================================================== | |
625 | ARRAY CODE sub returns true on all ARRAY elements[1] | |
626 | like: !grep { !CODE->($_) } ARRAY | |
627 | HASH CODE sub returns true on all HASH keys[1] | |
628 | like: !grep { !CODE->($_) } keys HASH | |
629 | Any CODE sub passed Any returns true | |
630 | like: CODE->(Any) | |
631 | ||
632 | Right operand is a Regexp: | |
633 | ||
634 | Left Right Description and pseudocode | |
635 | =============================================================== | |
636 | ARRAY Regexp any ARRAY elements match Regexp | |
637 | like: grep { /Regexp/ } ARRAY | |
638 | HASH Regexp any HASH keys match Regexp | |
639 | like: grep { /Regexp/ } keys HASH | |
640 | Any Regexp pattern match | |
641 | like: Any =~ /Regexp/ | |
642 | ||
643 | Other: | |
644 | ||
645 | Left Right Description and pseudocode | |
646 | =============================================================== | |
647 | Object Any invoke ~~ overloading on Object, | |
648 | or fall back to... | |
649 | ||
650 | Any Num numeric equality | |
651 | like: Any == Num | |
652 | Num nummy[4] numeric equality | |
653 | like: Num == nummy | |
654 | undef Any check whether undefined | |
655 | like: !defined(Any) | |
656 | Any Any string equality | |
657 | like: Any eq Any | |
658 | ||
659 | ||
660 | Notes: | |
661 | ||
662 | =over | |
663 | ||
664 | =item 1. | |
665 | Empty hashes or arrays match. | |
666 | ||
667 | =item 2. | |
40bec8a5 | 668 | That is, each element smartmatches the element of the same index in the other array.[3] |
1ca345ed TC |
669 | |
670 | =item 3. | |
671 | If a circular reference is found, fall back to referential equality. | |
672 | ||
673 | =item 4. | |
674 | Either an actual number, or a string that looks like one. | |
675 | ||
676 | =back | |
677 | ||
678 | The smartmatch implicitly dereferences any non-blessed hash or array | |
679 | reference, so the C<I<HASH>> and C<I<ARRAY>> entries apply in those cases. | |
680 | For blessed references, the C<I<Object>> entries apply. Smartmatches | |
681 | involving hashes only consider hash keys, never hash values. | |
682 | ||
683 | The "like" code entry is not always an exact rendition. For example, the | |
40bec8a5 | 684 | smartmatch operator short-circuits whenever possible, but C<grep> does |
1ca345ed TC |
685 | not. Also, C<grep> in scalar context returns the number of matches, but |
686 | C<~~> returns only true or false. | |
687 | ||
688 | Unlike most operators, the smartmatch operator knows to treat C<undef> | |
689 | specially: | |
690 | ||
691 | use v5.10.1; | |
692 | @array = (1, 2, 3, undef, 4, 5); | |
693 | say "some elements undefined" if undef ~~ @array; | |
694 | ||
695 | Each operand is considered in a modified scalar context, the modification | |
696 | being that array and hash variables are passed by reference to the | |
697 | operator, which implicitly dereferences them. Both elements | |
698 | of each pair are the same: | |
699 | ||
700 | use v5.10.1; | |
701 | ||
702 | my %hash = (red => 1, blue => 2, green => 3, | |
703 | orange => 4, yellow => 5, purple => 6, | |
704 | black => 7, grey => 8, white => 9); | |
705 | ||
706 | my @array = qw(red blue green); | |
707 | ||
708 | say "some array elements in hash keys" if @array ~~ %hash; | |
709 | say "some array elements in hash keys" if \@array ~~ \%hash; | |
710 | ||
711 | say "red in array" if "red" ~~ @array; | |
712 | say "red in array" if "red" ~~ \@array; | |
713 | ||
714 | say "some keys end in e" if /e$/ ~~ %hash; | |
715 | say "some keys end in e" if /e$/ ~~ \%hash; | |
716 | ||
40bec8a5 TC |
717 | Two arrays smartmatch if each element in the first array smartmatches |
718 | (that is, is "in") the corresponding element in the second array, | |
719 | recursively. | |
1ca345ed TC |
720 | |
721 | use v5.10.1; | |
722 | my @little = qw(red blue green); | |
723 | my @bigger = ("red", "blue", [ "orange", "green" ] ); | |
724 | if (@little ~~ @bigger) { # true! | |
725 | say "little is contained in bigger"; | |
726 | } | |
727 | ||
728 | Because the smartmatch operator recurses on nested arrays, this | |
729 | will still report that "red" is in the array. | |
730 | ||
731 | use v5.10.1; | |
732 | my @array = qw(red blue green); | |
733 | my $nested_array = [[[[[[[ @array ]]]]]]]; | |
734 | say "red in array" if "red" ~~ $nested_array; | |
735 | ||
736 | If two arrays smartmatch each other, then they are deep | |
737 | copies of each others' values, as this example reports: | |
738 | ||
739 | use v5.12.0; | |
740 | my @a = (0, 1, 2, [3, [4, 5], 6], 7); | |
741 | my @b = (0, 1, 2, [3, [4, 5], 6], 7); | |
742 | ||
743 | if (@a ~~ @b && @b ~~ @a) { | |
744 | say "a and b are deep copies of each other"; | |
745 | } | |
746 | elsif (@a ~~ @b) { | |
747 | say "a smartmatches in b"; | |
748 | } | |
749 | elsif (@b ~~ @a) { | |
750 | say "b smartmatches in a"; | |
751 | } | |
752 | else { | |
753 | say "a and b don't smartmatch each other at all"; | |
754 | } | |
755 | ||
756 | ||
ba7f043c KW |
757 | If you were to set S<C<$b[3] = 4>>, then instead of reporting that "a and b |
758 | are deep copies of each other", it now reports that C<"b smartmatches in a">. | |
759 | That's because the corresponding position in C<@a> contains an array that | |
1ca345ed TC |
760 | (eventually) has a 4 in it. |
761 | ||
762 | Smartmatching one hash against another reports whether both contain the | |
46f8a5ea | 763 | same keys, no more and no less. This could be used to see whether two |
1ca345ed TC |
764 | records have the same field names, without caring what values those fields |
765 | might have. For example: | |
766 | ||
767 | use v5.10.1; | |
768 | sub make_dogtag { | |
769 | state $REQUIRED_FIELDS = { name=>1, rank=>1, serial_num=>1 }; | |
770 | ||
771 | my ($class, $init_fields) = @_; | |
772 | ||
773 | die "Must supply (only) name, rank, and serial number" | |
774 | unless $init_fields ~~ $REQUIRED_FIELDS; | |
775 | ||
776 | ... | |
777 | } | |
778 | ||
1b590b38 LM |
779 | However, this only does what you mean if C<$init_fields> is indeed a hash |
780 | reference. The condition C<$init_fields ~~ $REQUIRED_FIELDS> also allows the | |
781 | strings C<"name">, C<"rank">, C<"serial_num"> as well as any array reference | |
782 | that contains C<"name"> or C<"rank"> or C<"serial_num"> anywhere to pass | |
783 | through. | |
1ca345ed TC |
784 | |
785 | The smartmatch operator is most often used as the implicit operator of a | |
786 | C<when> clause. See the section on "Switch Statements" in L<perlsyn>. | |
787 | ||
788 | =head3 Smartmatching of Objects | |
789 | ||
40bec8a5 TC |
790 | To avoid relying on an object's underlying representation, if the |
791 | smartmatch's right operand is an object that doesn't overload C<~~>, | |
792 | it raises the exception "C<Smartmatching a non-overloaded object | |
46f8a5ea FC |
793 | breaks encapsulation>". That's because one has no business digging |
794 | around to see whether something is "in" an object. These are all | |
40bec8a5 | 795 | illegal on objects without a C<~~> overload: |
1ca345ed TC |
796 | |
797 | %hash ~~ $object | |
798 | 42 ~~ $object | |
799 | "fred" ~~ $object | |
800 | ||
801 | However, you can change the way an object is smartmatched by overloading | |
46f8a5ea FC |
802 | the C<~~> operator. This is allowed to |
803 | extend the usual smartmatch semantics. | |
1ca345ed TC |
804 | For objects that do have an C<~~> overload, see L<overload>. |
805 | ||
806 | Using an object as the left operand is allowed, although not very useful. | |
807 | Smartmatching rules take precedence over overloading, so even if the | |
808 | object in the left operand has smartmatch overloading, this will be | |
809 | ignored. A left operand that is a non-overloaded object falls back on a | |
810 | string or numeric comparison of whatever the C<ref> operator returns. That | |
811 | means that | |
812 | ||
813 | $object ~~ X | |
814 | ||
815 | does I<not> invoke the overload method with C<I<X>> as an argument. | |
816 | Instead the above table is consulted as normal, and based on the type of | |
817 | C<I<X>>, overloading may or may not be invoked. For simple strings or | |
ba7f043c | 818 | numbers, "in" becomes equivalent to this: |
1ca345ed TC |
819 | |
820 | $object ~~ $number ref($object) == $number | |
821 | $object ~~ $string ref($object) eq $string | |
822 | ||
823 | For example, this reports that the handle smells IOish | |
824 | (but please don't really do this!): | |
825 | ||
826 | use IO::Handle; | |
827 | my $fh = IO::Handle->new(); | |
828 | if ($fh ~~ /\bIO\b/) { | |
829 | say "handle smells IOish"; | |
830 | } | |
831 | ||
832 | That's because it treats C<$fh> as a string like | |
833 | C<"IO::Handle=GLOB(0x8039e0)">, then pattern matches against that. | |
a034a98d | 834 | |
a0d0e21e | 835 | =head2 Bitwise And |
d74e8afc | 836 | X<operator, bitwise, and> X<bitwise and> X<&> |
a0d0e21e | 837 | |
ba7f043c | 838 | Binary C<"&"> returns its operands ANDed together bit by bit. Although no |
c791a246 KW |
839 | warning is currently raised, the result is not well defined when this operation |
840 | is performed on operands that aren't either numbers (see | |
5a0de581 | 841 | L</Integer Arithmetic>) nor bitstrings (see L</Bitwise String Operators>). |
a0d0e21e | 842 | |
ba7f043c | 843 | Note that C<"&"> has lower priority than relational operators, so for example |
1ca345ed | 844 | the parentheses are essential in a test like |
2cdc098b | 845 | |
1ca345ed | 846 | print "Even\n" if ($x & 1) == 0; |
2cdc098b | 847 | |
ba7f043c KW |
848 | If the experimental "bitwise" feature is enabled via S<C<use feature |
849 | 'bitwise'>>, then this operator always treats its operand as numbers. This | |
850 | feature produces a warning unless you also use C<S<no warnings | |
851 | 'experimental::bitwise'>>. | |
fb7054ba | 852 | |
a0d0e21e | 853 | =head2 Bitwise Or and Exclusive Or |
d74e8afc ITB |
854 | X<operator, bitwise, or> X<bitwise or> X<|> X<operator, bitwise, xor> |
855 | X<bitwise xor> X<^> | |
a0d0e21e | 856 | |
ba7f043c | 857 | Binary C<"|"> returns its operands ORed together bit by bit. |
a0d0e21e | 858 | |
ba7f043c | 859 | Binary C<"^"> returns its operands XORed together bit by bit. |
c791a246 KW |
860 | |
861 | Although no warning is currently raised, the results are not well | |
862 | defined when these operations are performed on operands that aren't either | |
5a0de581 | 863 | numbers (see L</Integer Arithmetic>) nor bitstrings (see L</Bitwise String |
c791a246 | 864 | Operators>). |
a0d0e21e | 865 | |
ba7f043c KW |
866 | Note that C<"|"> and C<"^"> have lower priority than relational operators, so |
867 | for example the parentheses are essential in a test like | |
2cdc098b | 868 | |
1ca345ed | 869 | print "false\n" if (8 | 2) != 10; |
2cdc098b | 870 | |
ba7f043c KW |
871 | If the experimental "bitwise" feature is enabled via S<C<use feature |
872 | 'bitwise'>>, then this operator always treats its operand as numbers. This | |
873 | feature produces a warning unless you also use S<C<no warnings | |
874 | 'experimental::bitwise'>>. | |
fb7054ba | 875 | |
a0d0e21e | 876 | =head2 C-style Logical And |
d74e8afc | 877 | X<&&> X<logical and> X<operator, logical, and> |
a0d0e21e | 878 | |
ba7f043c | 879 | Binary C<"&&"> performs a short-circuit logical AND operation. That is, |
a0d0e21e LW |
880 | if the left operand is false, the right operand is not even evaluated. |
881 | Scalar or list context propagates down to the right operand if it | |
882 | is evaluated. | |
883 | ||
884 | =head2 C-style Logical Or | |
d74e8afc | 885 | X<||> X<operator, logical, or> |
a0d0e21e | 886 | |
ba7f043c | 887 | Binary C<"||"> performs a short-circuit logical OR operation. That is, |
a0d0e21e LW |
888 | if the left operand is true, the right operand is not even evaluated. |
889 | Scalar or list context propagates down to the right operand if it | |
890 | is evaluated. | |
891 | ||
26d9d83b | 892 | =head2 Logical Defined-Or |
d74e8afc | 893 | X<//> X<operator, logical, defined-or> |
c963b151 BD |
894 | |
895 | Although it has no direct equivalent in C, Perl's C<//> operator is related | |
ba7f043c | 896 | to its C-style "or". In fact, it's exactly the same as C<||>, except that it |
95bee9ba | 897 | tests the left hand side's definedness instead of its truth. Thus, |
ba7f043c | 898 | S<C<< EXPR1 // EXPR2 >>> returns the value of C<< EXPR1 >> if it's defined, |
46f8a5ea FC |
899 | otherwise, the value of C<< EXPR2 >> is returned. |
900 | (C<< EXPR1 >> is evaluated in scalar context, C<< EXPR2 >> | |
901 | in the context of C<< // >> itself). Usually, | |
ba7f043c KW |
902 | this is the same result as S<C<< defined(EXPR1) ? EXPR1 : EXPR2 >>> (except that |
903 | the ternary-operator form can be used as a lvalue, while S<C<< EXPR1 // EXPR2 >>> | |
46f8a5ea | 904 | cannot). This is very useful for |
bdc7923b | 905 | providing default values for variables. If you actually want to test if |
ba7f043c | 906 | at least one of C<$x> and C<$y> is defined, use S<C<defined($x // $y)>>. |
c963b151 | 907 | |
d042e63d | 908 | The C<||>, C<//> and C<&&> operators return the last value evaluated |
46f8a5ea | 909 | (unlike C's C<||> and C<&&>, which return 0 or 1). Thus, a reasonably |
d042e63d | 910 | portable way to find out the home directory might be: |
a0d0e21e | 911 | |
c543c01b TC |
912 | $home = $ENV{HOME} |
913 | // $ENV{LOGDIR} | |
914 | // (getpwuid($<))[7] | |
915 | // die "You're homeless!\n"; | |
a0d0e21e | 916 | |
5a964f20 TC |
917 | In particular, this means that you shouldn't use this |
918 | for selecting between two aggregates for assignment: | |
919 | ||
bf55d65d LTC |
920 | @a = @b || @c; # This doesn't do the right thing |
921 | @a = scalar(@b) || @c; # because it really means this. | |
922 | @a = @b ? @b : @c; # This works fine, though. | |
5a964f20 | 923 | |
1ca345ed | 924 | As alternatives to C<&&> and C<||> when used for |
f23102e2 | 925 | control flow, Perl provides the C<and> and C<or> operators (see below). |
ba7f043c KW |
926 | The short-circuit behavior is identical. The precedence of C<"and"> |
927 | and C<"or"> is much lower, however, so that you can safely use them after a | |
5a964f20 | 928 | list operator without the need for parentheses: |
a0d0e21e LW |
929 | |
930 | unlink "alpha", "beta", "gamma" | |
931 | or gripe(), next LINE; | |
932 | ||
933 | With the C-style operators that would have been written like this: | |
934 | ||
935 | unlink("alpha", "beta", "gamma") | |
936 | || (gripe(), next LINE); | |
937 | ||
1ca345ed TC |
938 | It would be even more readable to write that this way: |
939 | ||
940 | unless(unlink("alpha", "beta", "gamma")) { | |
941 | gripe(); | |
942 | next LINE; | |
943 | } | |
944 | ||
ba7f043c | 945 | Using C<"or"> for assignment is unlikely to do what you want; see below. |
5a964f20 TC |
946 | |
947 | =head2 Range Operators | |
d74e8afc | 948 | X<operator, range> X<range> X<..> X<...> |
a0d0e21e | 949 | |
ba7f043c | 950 | Binary C<".."> is the range operator, which is really two different |
fb53bbb2 | 951 | operators depending on the context. In list context, it returns a |
54ae734e | 952 | list of values counting (up by ones) from the left value to the right |
2cdbc966 | 953 | value. If the left value is greater than the right value then it |
fb53bbb2 | 954 | returns the empty list. The range operator is useful for writing |
ba7f043c | 955 | S<C<foreach (1..10)>> loops and for doing slice operations on arrays. In |
2cdbc966 JD |
956 | the current implementation, no temporary array is created when the |
957 | range operator is used as the expression in C<foreach> loops, but older | |
958 | versions of Perl might burn a lot of memory when you write something | |
959 | like this: | |
a0d0e21e LW |
960 | |
961 | for (1 .. 1_000_000) { | |
962 | # code | |
54310121 | 963 | } |
a0d0e21e | 964 | |
8f0f46f8 | 965 | The range operator also works on strings, using the magical |
966 | auto-increment, see below. | |
54ae734e | 967 | |
ba7f043c | 968 | In scalar context, C<".."> returns a boolean value. The operator is |
8f0f46f8 | 969 | bistable, like a flip-flop, and emulates the line-range (comma) |
ba7f043c | 970 | operator of B<sed>, B<awk>, and various editors. Each C<".."> operator |
8f0f46f8 | 971 | maintains its own boolean state, even across calls to a subroutine |
46f8a5ea | 972 | that contains it. It is false as long as its left operand is false. |
a0d0e21e LW |
973 | Once the left operand is true, the range operator stays true until the |
974 | right operand is true, I<AFTER> which the range operator becomes false | |
8f0f46f8 | 975 | again. It doesn't become false till the next time the range operator |
976 | is evaluated. It can test the right operand and become false on the | |
977 | same evaluation it became true (as in B<awk>), but it still returns | |
46f8a5ea | 978 | true once. If you don't want it to test the right operand until the |
ba7f043c KW |
979 | next evaluation, as in B<sed>, just use three dots (C<"...">) instead of |
980 | two. In all other regards, C<"..."> behaves just like C<".."> does. | |
19799a22 GS |
981 | |
982 | The right operand is not evaluated while the operator is in the | |
983 | "false" state, and the left operand is not evaluated while the | |
984 | operator is in the "true" state. The precedence is a little lower | |
985 | than || and &&. The value returned is either the empty string for | |
8f0f46f8 | 986 | false, or a sequence number (beginning with 1) for true. The sequence |
987 | number is reset for each range encountered. The final sequence number | |
ba7f043c | 988 | in a range has the string C<"E0"> appended to it, which doesn't affect |
8f0f46f8 | 989 | its numeric value, but gives you something to search for if you want |
990 | to exclude the endpoint. You can exclude the beginning point by | |
991 | waiting for the sequence number to be greater than 1. | |
df5f8116 | 992 | |
ba7f043c | 993 | If either operand of scalar C<".."> is a constant expression, |
df5f8116 CW |
994 | that operand is considered true if it is equal (C<==>) to the current |
995 | input line number (the C<$.> variable). | |
996 | ||
ba7f043c | 997 | To be pedantic, the comparison is actually S<C<int(EXPR) == int(EXPR)>>, |
df5f8116 CW |
998 | but that is only an issue if you use a floating point expression; when |
999 | implicitly using C<$.> as described in the previous paragraph, the | |
ba7f043c | 1000 | comparison is S<C<int(EXPR) == int($.)>> which is only an issue when C<$.> |
df5f8116 | 1001 | is set to a floating point value and you are not reading from a file. |
ba7f043c | 1002 | Furthermore, S<C<"span" .. "spat">> or S<C<2.18 .. 3.14>> will not do what |
df5f8116 CW |
1003 | you want in scalar context because each of the operands are evaluated |
1004 | using their integer representation. | |
1005 | ||
1006 | Examples: | |
a0d0e21e LW |
1007 | |
1008 | As a scalar operator: | |
1009 | ||
df5f8116 | 1010 | if (101 .. 200) { print; } # print 2nd hundred lines, short for |
950b09ed | 1011 | # if ($. == 101 .. $. == 200) { print; } |
9f10b797 RGS |
1012 | |
1013 | next LINE if (1 .. /^$/); # skip header lines, short for | |
f343f960 | 1014 | # next LINE if ($. == 1 .. /^$/); |
9f10b797 RGS |
1015 | # (typically in a loop labeled LINE) |
1016 | ||
1017 | s/^/> / if (/^$/ .. eof()); # quote body | |
a0d0e21e | 1018 | |
5a964f20 TC |
1019 | # parse mail messages |
1020 | while (<>) { | |
1021 | $in_header = 1 .. /^$/; | |
df5f8116 CW |
1022 | $in_body = /^$/ .. eof; |
1023 | if ($in_header) { | |
f343f960 | 1024 | # do something |
df5f8116 | 1025 | } else { # in body |
f343f960 | 1026 | # do something else |
df5f8116 | 1027 | } |
5a964f20 | 1028 | } continue { |
df5f8116 | 1029 | close ARGV if eof; # reset $. each file |
5a964f20 TC |
1030 | } |
1031 | ||
acf31ca5 SF |
1032 | Here's a simple example to illustrate the difference between |
1033 | the two range operators: | |
1034 | ||
1035 | @lines = (" - Foo", | |
1036 | "01 - Bar", | |
1037 | "1 - Baz", | |
1038 | " - Quux"); | |
1039 | ||
9f10b797 RGS |
1040 | foreach (@lines) { |
1041 | if (/0/ .. /1/) { | |
acf31ca5 SF |
1042 | print "$_\n"; |
1043 | } | |
1044 | } | |
1045 | ||
46f8a5ea | 1046 | This program will print only the line containing "Bar". If |
9f10b797 | 1047 | the range operator is changed to C<...>, it will also print the |
acf31ca5 SF |
1048 | "Baz" line. |
1049 | ||
1050 | And now some examples as a list operator: | |
a0d0e21e | 1051 | |
1ca345ed TC |
1052 | for (101 .. 200) { print } # print $_ 100 times |
1053 | @foo = @foo[0 .. $#foo]; # an expensive no-op | |
1054 | @foo = @foo[$#foo-4 .. $#foo]; # slice last 5 items | |
a0d0e21e | 1055 | |
5a964f20 | 1056 | The range operator (in list context) makes use of the magical |
5f05dabc | 1057 | auto-increment algorithm if the operands are strings. You |
a0d0e21e LW |
1058 | can say |
1059 | ||
c543c01b | 1060 | @alphabet = ("A" .. "Z"); |
a0d0e21e | 1061 | |
54ae734e | 1062 | to get all normal letters of the English alphabet, or |
a0d0e21e | 1063 | |
c543c01b | 1064 | $hexdigit = (0 .. 9, "a" .. "f")[$num & 15]; |
a0d0e21e LW |
1065 | |
1066 | to get a hexadecimal digit, or | |
1067 | ||
1ca345ed TC |
1068 | @z2 = ("01" .. "31"); |
1069 | print $z2[$mday]; | |
a0d0e21e | 1070 | |
ea4f5703 YST |
1071 | to get dates with leading zeros. |
1072 | ||
1073 | If the final value specified is not in the sequence that the magical | |
1074 | increment would produce, the sequence goes until the next value would | |
1075 | be longer than the final value specified. | |
1076 | ||
1077 | If the initial value specified isn't part of a magical increment | |
c543c01b | 1078 | sequence (that is, a non-empty string matching C</^[a-zA-Z]*[0-9]*\z/>), |
ea4f5703 YST |
1079 | only the initial value will be returned. So the following will only |
1080 | return an alpha: | |
1081 | ||
c543c01b | 1082 | use charnames "greek"; |
ea4f5703 YST |
1083 | my @greek_small = ("\N{alpha}" .. "\N{omega}"); |
1084 | ||
c543c01b TC |
1085 | To get the 25 traditional lowercase Greek letters, including both sigmas, |
1086 | you could use this instead: | |
ea4f5703 | 1087 | |
c543c01b | 1088 | use charnames "greek"; |
1ca345ed TC |
1089 | my @greek_small = map { chr } ( ord("\N{alpha}") |
1090 | .. | |
1091 | ord("\N{omega}") | |
1092 | ); | |
c543c01b TC |
1093 | |
1094 | However, because there are I<many> other lowercase Greek characters than | |
1095 | just those, to match lowercase Greek characters in a regular expression, | |
47c56cc8 KW |
1096 | you could use the pattern C</(?:(?=\p{Greek})\p{Lower})+/> (or the |
1097 | L<experimental feature|perlrecharclass/Extended Bracketed Character | |
1098 | Classes> C<S</(?[ \p{Greek} & \p{Lower} ])+/>>). | |
a0d0e21e | 1099 | |
ba7f043c | 1100 | Because each operand is evaluated in integer form, S<C<2.18 .. 3.14>> will |
df5f8116 CW |
1101 | return two elements in list context. |
1102 | ||
1103 | @list = (2.18 .. 3.14); # same as @list = (2 .. 3); | |
1104 | ||
a0d0e21e | 1105 | =head2 Conditional Operator |
d74e8afc | 1106 | X<operator, conditional> X<operator, ternary> X<ternary> X<?:> |
a0d0e21e | 1107 | |
ba7f043c KW |
1108 | Ternary C<"?:"> is the conditional operator, just as in C. It works much |
1109 | like an if-then-else. If the argument before the C<?> is true, the | |
1110 | argument before the C<:> is returned, otherwise the argument after the | |
1111 | C<:> is returned. For example: | |
cb1a09d0 | 1112 | |
54310121 | 1113 | printf "I have %d dog%s.\n", $n, |
c543c01b | 1114 | ($n == 1) ? "" : "s"; |
cb1a09d0 AD |
1115 | |
1116 | Scalar or list context propagates downward into the 2nd | |
54310121 | 1117 | or 3rd argument, whichever is selected. |
cb1a09d0 | 1118 | |
db691027 SF |
1119 | $x = $ok ? $y : $z; # get a scalar |
1120 | @x = $ok ? @y : @z; # get an array | |
1121 | $x = $ok ? @y : @z; # oops, that's just a count! | |
cb1a09d0 AD |
1122 | |
1123 | The operator may be assigned to if both the 2nd and 3rd arguments are | |
1124 | legal lvalues (meaning that you can assign to them): | |
a0d0e21e | 1125 | |
db691027 | 1126 | ($x_or_y ? $x : $y) = $z; |
a0d0e21e | 1127 | |
5a964f20 TC |
1128 | Because this operator produces an assignable result, using assignments |
1129 | without parentheses will get you in trouble. For example, this: | |
1130 | ||
db691027 | 1131 | $x % 2 ? $x += 10 : $x += 2 |
5a964f20 TC |
1132 | |
1133 | Really means this: | |
1134 | ||
db691027 | 1135 | (($x % 2) ? ($x += 10) : $x) += 2 |
5a964f20 TC |
1136 | |
1137 | Rather than this: | |
1138 | ||
db691027 | 1139 | ($x % 2) ? ($x += 10) : ($x += 2) |
5a964f20 | 1140 | |
19799a22 GS |
1141 | That should probably be written more simply as: |
1142 | ||
db691027 | 1143 | $x += ($x % 2) ? 10 : 2; |
19799a22 | 1144 | |
4633a7c4 | 1145 | =head2 Assignment Operators |
d74e8afc | 1146 | X<assignment> X<operator, assignment> X<=> X<**=> X<+=> X<*=> X<&=> |
5ac3b81c | 1147 | X<<< <<= >>> X<&&=> X<-=> X</=> X<|=> X<<< >>= >>> X<||=> X<//=> X<.=> |
fb7054ba | 1148 | X<%=> X<^=> X<x=> X<&.=> X<|.=> X<^.=> |
a0d0e21e | 1149 | |
ba7f043c | 1150 | C<"="> is the ordinary assignment operator. |
a0d0e21e LW |
1151 | |
1152 | Assignment operators work as in C. That is, | |
1153 | ||
db691027 | 1154 | $x += 2; |
a0d0e21e LW |
1155 | |
1156 | is equivalent to | |
1157 | ||
db691027 | 1158 | $x = $x + 2; |
a0d0e21e LW |
1159 | |
1160 | although without duplicating any side effects that dereferencing the lvalue | |
ba7f043c | 1161 | might trigger, such as from C<tie()>. Other assignment operators work similarly. |
54310121 | 1162 | The following are recognized: |
a0d0e21e | 1163 | |
fb7054ba FC |
1164 | **= += *= &= &.= <<= &&= |
1165 | -= /= |= |.= >>= ||= | |
1166 | .= %= ^= ^.= //= | |
9f10b797 | 1167 | x= |
a0d0e21e | 1168 | |
19799a22 | 1169 | Although these are grouped by family, they all have the precedence |
82848c10 FC |
1170 | of assignment. These combined assignment operators can only operate on |
1171 | scalars, whereas the ordinary assignment operator can assign to arrays, | |
1172 | hashes, lists and even references. (See L<"Context"|perldata/Context> | |
1173 | and L<perldata/List value constructors>, and L<perlref/Assigning to | |
1174 | References>.) | |
a0d0e21e | 1175 | |
b350dd2f GS |
1176 | Unlike in C, the scalar assignment operator produces a valid lvalue. |
1177 | Modifying an assignment is equivalent to doing the assignment and | |
1178 | then modifying the variable that was assigned to. This is useful | |
1179 | for modifying a copy of something, like this: | |
a0d0e21e | 1180 | |
1ca345ed TC |
1181 | ($tmp = $global) =~ tr/13579/24680/; |
1182 | ||
1183 | Although as of 5.14, that can be also be accomplished this way: | |
1184 | ||
1185 | use v5.14; | |
1186 | $tmp = ($global =~ tr/13579/24680/r); | |
a0d0e21e LW |
1187 | |
1188 | Likewise, | |
1189 | ||
db691027 | 1190 | ($x += 2) *= 3; |
a0d0e21e LW |
1191 | |
1192 | is equivalent to | |
1193 | ||
db691027 SF |
1194 | $x += 2; |
1195 | $x *= 3; | |
a0d0e21e | 1196 | |
b350dd2f GS |
1197 | Similarly, a list assignment in list context produces the list of |
1198 | lvalues assigned to, and a list assignment in scalar context returns | |
1199 | the number of elements produced by the expression on the right hand | |
1200 | side of the assignment. | |
1201 | ||
ba7f043c | 1202 | The three dotted bitwise assignment operators (C<&.=> C<|.=> C<^.=>) are new in |
fb7054ba FC |
1203 | Perl 5.22 and experimental. See L</Bitwise String Operators>. |
1204 | ||
748a9306 | 1205 | =head2 Comma Operator |
d74e8afc | 1206 | X<comma> X<operator, comma> X<,> |
a0d0e21e | 1207 | |
ba7f043c | 1208 | Binary C<","> is the comma operator. In scalar context it evaluates |
a0d0e21e LW |
1209 | its left argument, throws that value away, then evaluates its right |
1210 | argument and returns that value. This is just like C's comma operator. | |
1211 | ||
5a964f20 | 1212 | In list context, it's just the list argument separator, and inserts |
ed5c6d31 PJ |
1213 | both its arguments into the list. These arguments are also evaluated |
1214 | from left to right. | |
a0d0e21e | 1215 | |
ba7f043c KW |
1216 | The C<< => >> operator (sometimes pronounced "fat comma") is a synonym |
1217 | for the comma except that it causes a | |
4e1988c6 | 1218 | word on its left to be interpreted as a string if it begins with a letter |
344f2c40 IG |
1219 | or underscore and is composed only of letters, digits and underscores. |
1220 | This includes operands that might otherwise be interpreted as operators, | |
46f8a5ea | 1221 | constants, single number v-strings or function calls. If in doubt about |
c543c01b | 1222 | this behavior, the left operand can be quoted explicitly. |
344f2c40 IG |
1223 | |
1224 | Otherwise, the C<< => >> operator behaves exactly as the comma operator | |
1225 | or list argument separator, according to context. | |
1226 | ||
1227 | For example: | |
a44e5664 MS |
1228 | |
1229 | use constant FOO => "something"; | |
1230 | ||
1231 | my %h = ( FOO => 23 ); | |
1232 | ||
1233 | is equivalent to: | |
1234 | ||
1235 | my %h = ("FOO", 23); | |
1236 | ||
1237 | It is I<NOT>: | |
1238 | ||
1239 | my %h = ("something", 23); | |
1240 | ||
719b43e8 RGS |
1241 | The C<< => >> operator is helpful in documenting the correspondence |
1242 | between keys and values in hashes, and other paired elements in lists. | |
748a9306 | 1243 | |
a12b8f3c FC |
1244 | %hash = ( $key => $value ); |
1245 | login( $username => $password ); | |
a44e5664 | 1246 | |
4e1988c6 FC |
1247 | The special quoting behavior ignores precedence, and hence may apply to |
1248 | I<part> of the left operand: | |
1249 | ||
1250 | print time.shift => "bbb"; | |
1251 | ||
ba7f043c | 1252 | That example prints something like C<"1314363215shiftbbb">, because the |
4e1988c6 FC |
1253 | C<< => >> implicitly quotes the C<shift> immediately on its left, ignoring |
1254 | the fact that C<time.shift> is the entire left operand. | |
1255 | ||
a0d0e21e | 1256 | =head2 List Operators (Rightward) |
d74e8afc | 1257 | X<operator, list, rightward> X<list operator> |
a0d0e21e | 1258 | |
c543c01b | 1259 | On the right side of a list operator, the comma has very low precedence, |
a0d0e21e LW |
1260 | such that it controls all comma-separated expressions found there. |
1261 | The only operators with lower precedence are the logical operators | |
ba7f043c | 1262 | C<"and">, C<"or">, and C<"not">, which may be used to evaluate calls to list |
1ca345ed TC |
1263 | operators without the need for parentheses: |
1264 | ||
1265 | open HANDLE, "< :utf8", "filename" or die "Can't open: $!\n"; | |
1266 | ||
1267 | However, some people find that code harder to read than writing | |
1268 | it with parentheses: | |
1269 | ||
1270 | open(HANDLE, "< :utf8", "filename") or die "Can't open: $!\n"; | |
1271 | ||
ba7f043c | 1272 | in which case you might as well just use the more customary C<"||"> operator: |
a0d0e21e | 1273 | |
1ca345ed | 1274 | open(HANDLE, "< :utf8", "filename") || die "Can't open: $!\n"; |
a0d0e21e | 1275 | |
a95b3d6a | 1276 | See also discussion of list operators in L</Terms and List Operators (Leftward)>. |
a0d0e21e LW |
1277 | |
1278 | =head2 Logical Not | |
d74e8afc | 1279 | X<operator, logical, not> X<not> |
a0d0e21e | 1280 | |
ba7f043c KW |
1281 | Unary C<"not"> returns the logical negation of the expression to its right. |
1282 | It's the equivalent of C<"!"> except for the very low precedence. | |
a0d0e21e LW |
1283 | |
1284 | =head2 Logical And | |
d74e8afc | 1285 | X<operator, logical, and> X<and> |
a0d0e21e | 1286 | |
ba7f043c | 1287 | Binary C<"and"> returns the logical conjunction of the two surrounding |
c543c01b TC |
1288 | expressions. It's equivalent to C<&&> except for the very low |
1289 | precedence. This means that it short-circuits: the right | |
a0d0e21e LW |
1290 | expression is evaluated only if the left expression is true. |
1291 | ||
59ab9d6e | 1292 | =head2 Logical or and Exclusive Or |
f23102e2 | 1293 | X<operator, logical, or> X<operator, logical, xor> |
59ab9d6e | 1294 | X<operator, logical, exclusive or> |
f23102e2 | 1295 | X<or> X<xor> |
a0d0e21e | 1296 | |
ba7f043c | 1297 | Binary C<"or"> returns the logical disjunction of the two surrounding |
c543c01b TC |
1298 | expressions. It's equivalent to C<||> except for the very low precedence. |
1299 | This makes it useful for control flow: | |
5a964f20 TC |
1300 | |
1301 | print FH $data or die "Can't write to FH: $!"; | |
1302 | ||
c543c01b TC |
1303 | This means that it short-circuits: the right expression is evaluated |
1304 | only if the left expression is false. Due to its precedence, you must | |
1305 | be careful to avoid using it as replacement for the C<||> operator. | |
1306 | It usually works out better for flow control than in assignments: | |
5a964f20 | 1307 | |
db691027 SF |
1308 | $x = $y or $z; # bug: this is wrong |
1309 | ($x = $y) or $z; # really means this | |
1310 | $x = $y || $z; # better written this way | |
5a964f20 | 1311 | |
19799a22 | 1312 | However, when it's a list-context assignment and you're trying to use |
ba7f043c | 1313 | C<||> for control flow, you probably need C<"or"> so that the assignment |
5a964f20 TC |
1314 | takes higher precedence. |
1315 | ||
1316 | @info = stat($file) || die; # oops, scalar sense of stat! | |
1317 | @info = stat($file) or die; # better, now @info gets its due | |
1318 | ||
c963b151 BD |
1319 | Then again, you could always use parentheses. |
1320 | ||
ba7f043c | 1321 | Binary C<"xor"> returns the exclusive-OR of the two surrounding expressions. |
c543c01b | 1322 | It cannot short-circuit (of course). |
a0d0e21e | 1323 | |
59ab9d6e MB |
1324 | There is no low precedence operator for defined-OR. |
1325 | ||
a0d0e21e | 1326 | =head2 C Operators Missing From Perl |
d74e8afc ITB |
1327 | X<operator, missing from perl> X<&> X<*> |
1328 | X<typecasting> X<(TYPE)> | |
a0d0e21e LW |
1329 | |
1330 | Here is what C has that Perl doesn't: | |
1331 | ||
1332 | =over 8 | |
1333 | ||
1334 | =item unary & | |
1335 | ||
ba7f043c | 1336 | Address-of operator. (But see the C<"\"> operator for taking a reference.) |
a0d0e21e LW |
1337 | |
1338 | =item unary * | |
1339 | ||
46f8a5ea | 1340 | Dereference-address operator. (Perl's prefix dereferencing |
ba7f043c | 1341 | operators are typed: C<$>, C<@>, C<%>, and C<&>.) |
a0d0e21e LW |
1342 | |
1343 | =item (TYPE) | |
1344 | ||
19799a22 | 1345 | Type-casting operator. |
a0d0e21e LW |
1346 | |
1347 | =back | |
1348 | ||
5f05dabc | 1349 | =head2 Quote and Quote-like Operators |
89d205f2 | 1350 | X<operator, quote> X<operator, quote-like> X<q> X<qq> X<qx> X<qw> X<m> |
d74e8afc ITB |
1351 | X<qr> X<s> X<tr> X<'> X<''> X<"> X<""> X<//> X<`> X<``> X<<< << >>> |
1352 | X<escape sequence> X<escape> | |
1353 | ||
a0d0e21e LW |
1354 | While we usually think of quotes as literal values, in Perl they |
1355 | function as operators, providing various kinds of interpolating and | |
1356 | pattern matching capabilities. Perl provides customary quote characters | |
1357 | for these behaviors, but also provides a way for you to choose your | |
1358 | quote character for any of them. In the following table, a C<{}> represents | |
9f10b797 | 1359 | any pair of delimiters you choose. |
a0d0e21e | 1360 | |
2c268ad5 TP |
1361 | Customary Generic Meaning Interpolates |
1362 | '' q{} Literal no | |
1363 | "" qq{} Literal yes | |
af9219ee | 1364 | `` qx{} Command yes* |
2c268ad5 | 1365 | qw{} Word list no |
af9219ee MG |
1366 | // m{} Pattern match yes* |
1367 | qr{} Pattern yes* | |
1368 | s{}{} Substitution yes* | |
2c268ad5 | 1369 | tr{}{} Transliteration no (but see below) |
c543c01b | 1370 | y{}{} Transliteration no (but see below) |
7e3b091d | 1371 | <<EOF here-doc yes* |
a0d0e21e | 1372 | |
af9219ee MG |
1373 | * unless the delimiter is ''. |
1374 | ||
87275199 | 1375 | Non-bracketing delimiters use the same character fore and aft, but the four |
c543c01b | 1376 | sorts of ASCII brackets (round, angle, square, curly) all nest, which means |
9f10b797 | 1377 | that |
87275199 | 1378 | |
c543c01b | 1379 | q{foo{bar}baz} |
35f2feb0 | 1380 | |
9f10b797 | 1381 | is the same as |
87275199 | 1382 | |
c543c01b | 1383 | 'foo{bar}baz' |
87275199 GS |
1384 | |
1385 | Note, however, that this does not always work for quoting Perl code: | |
1386 | ||
db691027 | 1387 | $s = q{ if($x eq "}") ... }; # WRONG |
87275199 | 1388 | |
ba7f043c | 1389 | is a syntax error. The C<L<Text::Balanced>> module (standard as of v5.8, |
c543c01b | 1390 | and from CPAN before then) is able to do this properly. |
87275199 | 1391 | |
841bfb48 KW |
1392 | There can (and in some cases, must) be whitespace between the operator |
1393 | and the quoting | |
fb73857a | 1394 | characters, except when C<#> is being used as the quoting character. |
ba7f043c | 1395 | C<q#foo#> is parsed as the string C<foo>, while S<C<q #foo#>> is the |
19799a22 GS |
1396 | operator C<q> followed by a comment. Its argument will be taken |
1397 | from the next line. This allows you to write: | |
fb73857a | 1398 | |
1399 | s {foo} # Replace foo | |
1400 | {bar} # with bar. | |
1401 | ||
841bfb48 KW |
1402 | The cases where whitespace must be used are when the quoting character |
1403 | is a word character (meaning it matches C</\w/>): | |
1404 | ||
1405 | q XfooX # Works: means the string 'foo' | |
1406 | qXfooX # WRONG! | |
1407 | ||
c543c01b TC |
1408 | The following escape sequences are available in constructs that interpolate, |
1409 | and in transliterations: | |
5691ca5f | 1410 | X<\t> X<\n> X<\r> X<\f> X<\b> X<\a> X<\e> X<\x> X<\0> X<\c> X<\N> X<\N{}> |
04341565 | 1411 | X<\o{}> |
5691ca5f | 1412 | |
2c4c1ff2 KW |
1413 | Sequence Note Description |
1414 | \t tab (HT, TAB) | |
1415 | \n newline (NL) | |
1416 | \r return (CR) | |
1417 | \f form feed (FF) | |
1418 | \b backspace (BS) | |
1419 | \a alarm (bell) (BEL) | |
1420 | \e escape (ESC) | |
c543c01b | 1421 | \x{263A} [1,8] hex char (example: SMILEY) |
2c4c1ff2 | 1422 | \x1b [2,8] restricted range hex char (example: ESC) |
fb121860 | 1423 | \N{name} [3] named Unicode character or character sequence |
2c4c1ff2 KW |
1424 | \N{U+263D} [4,8] Unicode character (example: FIRST QUARTER MOON) |
1425 | \c[ [5] control char (example: chr(27)) | |
1426 | \o{23072} [6,8] octal char (example: SMILEY) | |
1427 | \033 [7,8] restricted range octal char (example: ESC) | |
5691ca5f KW |
1428 | |
1429 | =over 4 | |
1430 | ||
1431 | =item [1] | |
1432 | ||
2c4c1ff2 KW |
1433 | The result is the character specified by the hexadecimal number between |
1434 | the braces. See L</[8]> below for details on which character. | |
96448467 | 1435 | |
46f8a5ea | 1436 | Only hexadecimal digits are valid between the braces. If an invalid |
96448467 DG |
1437 | character is encountered, a warning will be issued and the invalid |
1438 | character and all subsequent characters (valid or invalid) within the | |
1439 | braces will be discarded. | |
1440 | ||
1441 | If there are no valid digits between the braces, the generated character is | |
1442 | the NULL character (C<\x{00}>). However, an explicit empty brace (C<\x{}>) | |
c543c01b | 1443 | will not cause a warning (currently). |
40687185 KW |
1444 | |
1445 | =item [2] | |
1446 | ||
2c4c1ff2 KW |
1447 | The result is the character specified by the hexadecimal number in the range |
1448 | 0x00 to 0xFF. See L</[8]> below for details on which character. | |
96448467 DG |
1449 | |
1450 | Only hexadecimal digits are valid following C<\x>. When C<\x> is followed | |
2c4c1ff2 | 1451 | by fewer than two valid digits, any valid digits will be zero-padded. This |
ba7f043c | 1452 | means that C<\x7> will be interpreted as C<\x07>, and a lone C<"\x"> will be |
2c4c1ff2 | 1453 | interpreted as C<\x00>. Except at the end of a string, having fewer than |
c543c01b | 1454 | two valid digits will result in a warning. Note that although the warning |
96448467 DG |
1455 | says the illegal character is ignored, it is only ignored as part of the |
1456 | escape and will still be used as the subsequent character in the string. | |
1457 | For example: | |
1458 | ||
1459 | Original Result Warns? | |
1460 | "\x7" "\x07" no | |
1461 | "\x" "\x00" no | |
1462 | "\x7q" "\x07q" yes | |
1463 | "\xq" "\x00q" yes | |
1464 | ||
40687185 KW |
1465 | =item [3] |
1466 | ||
fb121860 | 1467 | The result is the Unicode character or character sequence given by I<name>. |
2c4c1ff2 | 1468 | See L<charnames>. |
40687185 KW |
1469 | |
1470 | =item [4] | |
1471 | ||
ba7f043c | 1472 | S<C<\N{U+I<hexadecimal number>}>> means the Unicode character whose Unicode code |
2c4c1ff2 | 1473 | point is I<hexadecimal number>. |
40687185 KW |
1474 | |
1475 | =item [5] | |
1476 | ||
5691ca5f KW |
1477 | The character following C<\c> is mapped to some other character as shown in the |
1478 | table: | |
1479 | ||
1480 | Sequence Value | |
1481 | \c@ chr(0) | |
1482 | \cA chr(1) | |
1483 | \ca chr(1) | |
1484 | \cB chr(2) | |
1485 | \cb chr(2) | |
1486 | ... | |
1487 | \cZ chr(26) | |
1488 | \cz chr(26) | |
1489 | \c[ chr(27) | |
ba7f043c | 1490 | # See below for chr(28) |
5691ca5f KW |
1491 | \c] chr(29) |
1492 | \c^ chr(30) | |
c3e9d7a9 | 1493 | \c_ chr(31) |
ba7f043c KW |
1494 | \c? chr(127) # (on ASCII platforms; see below for link to |
1495 | # EBCDIC discussion) | |
5691ca5f | 1496 | |
d813941f | 1497 | In other words, it's the character whose code point has had 64 xor'd with |
c3e9d7a9 KW |
1498 | its uppercase. C<\c?> is DELETE on ASCII platforms because |
1499 | S<C<ord("?") ^ 64>> is 127, and | |
ba7f043c | 1500 | C<\c@> is NULL because the ord of C<"@"> is 64, so xor'ing 64 itself produces 0. |
d813941f | 1501 | |
ba7f043c | 1502 | Also, C<\c\I<X>> yields S<C< chr(28) . "I<X>">> for any I<X>, but cannot come at the |
5691ca5f KW |
1503 | end of a string, because the backslash would be parsed as escaping the end |
1504 | quote. | |
1505 | ||
1506 | On ASCII platforms, the resulting characters from the list above are the | |
1507 | complete set of ASCII controls. This isn't the case on EBCDIC platforms; see | |
c3e9d7a9 KW |
1508 | L<perlebcdic/OPERATOR DIFFERENCES> for a full discussion of the |
1509 | differences between these for ASCII versus EBCDIC platforms. | |
5691ca5f | 1510 | |
c3e9d7a9 | 1511 | Use of any other character following the C<"c"> besides those listed above is |
63a63d81 KW |
1512 | discouraged, and as of Perl v5.20, the only characters actually allowed |
1513 | are the printable ASCII ones, minus the left brace C<"{">. What happens | |
1514 | for any of the allowed other characters is that the value is derived by | |
1515 | xor'ing with the seventh bit, which is 64, and a warning raised if | |
1516 | enabled. Using the non-allowed characters generates a fatal error. | |
5691ca5f KW |
1517 | |
1518 | To get platform independent controls, you can use C<\N{...}>. | |
1519 | ||
40687185 KW |
1520 | =item [6] |
1521 | ||
2c4c1ff2 KW |
1522 | The result is the character specified by the octal number between the braces. |
1523 | See L</[8]> below for details on which character. | |
04341565 DG |
1524 | |
1525 | If a character that isn't an octal digit is encountered, a warning is raised, | |
1526 | and the value is based on the octal digits before it, discarding it and all | |
1527 | following characters up to the closing brace. It is a fatal error if there are | |
1528 | no octal digits at all. | |
1529 | ||
1530 | =item [7] | |
1531 | ||
c543c01b | 1532 | The result is the character specified by the three-digit octal number in the |
2c4c1ff2 KW |
1533 | range 000 to 777 (but best to not use above 077, see next paragraph). See |
1534 | L</[8]> below for details on which character. | |
1535 | ||
1536 | Some contexts allow 2 or even 1 digit, but any usage without exactly | |
40687185 | 1537 | three digits, the first being a zero, may give unintended results. (For |
5db3e519 FC |
1538 | example, in a regular expression it may be confused with a backreference; |
1539 | see L<perlrebackslash/Octal escapes>.) Starting in Perl 5.14, you may | |
c543c01b | 1540 | use C<\o{}> instead, which avoids all these problems. Otherwise, it is best to |
04341565 DG |
1541 | use this construct only for ordinals C<\077> and below, remembering to pad to |
1542 | the left with zeros to make three digits. For larger ordinals, either use | |
ba7f043c KW |
1543 | C<\o{}>, or convert to something else, such as to hex and use C<\N{U+}> |
1544 | (which is portable between platforms with different character sets) or | |
1545 | C<\x{}> instead. | |
40687185 | 1546 | |
2c4c1ff2 KW |
1547 | =item [8] |
1548 | ||
c543c01b | 1549 | Several constructs above specify a character by a number. That number |
2c4c1ff2 | 1550 | gives the character's position in the character set encoding (indexed from 0). |
c543c01b | 1551 | This is called synonymously its ordinal, code position, or code point. Perl |
2c4c1ff2 KW |
1552 | works on platforms that have a native encoding currently of either ASCII/Latin1 |
1553 | or EBCDIC, each of which allow specification of 256 characters. In general, if | |
1554 | the number is 255 (0xFF, 0377) or below, Perl interprets this in the platform's | |
1555 | native encoding. If the number is 256 (0x100, 0400) or above, Perl interprets | |
c543c01b | 1556 | it as a Unicode code point and the result is the corresponding Unicode |
2c4c1ff2 KW |
1557 | character. For example C<\x{50}> and C<\o{120}> both are the number 80 in |
1558 | decimal, which is less than 256, so the number is interpreted in the native | |
1559 | character set encoding. In ASCII the character in the 80th position (indexed | |
ba7f043c | 1560 | from 0) is the letter C<"P">, and in EBCDIC it is the ampersand symbol C<"&">. |
2c4c1ff2 KW |
1561 | C<\x{100}> and C<\o{400}> are both 256 in decimal, so the number is interpreted |
1562 | as a Unicode code point no matter what the native encoding is. The name of the | |
9fef6a0d | 1563 | character in the 256th position (indexed by 0) in Unicode is |
2c4c1ff2 KW |
1564 | C<LATIN CAPITAL LETTER A WITH MACRON>. |
1565 | ||
9fef6a0d | 1566 | There are a couple of exceptions to the above rule. S<C<\N{U+I<hex number>}>> is |
ba7f043c KW |
1567 | always interpreted as a Unicode code point, so that C<\N{U+0050}> is C<"P"> even |
1568 | on EBCDIC platforms. And if C<S<L<use encoding|encoding>>> is in effect, the | |
2c4c1ff2 KW |
1569 | number is considered to be in that encoding, and is translated from that into |
1570 | the platform's native encoding if there is a corresponding native character; | |
1571 | otherwise to Unicode. | |
1572 | ||
5691ca5f | 1573 | =back |
4c77eaa2 | 1574 | |
e526e8bb | 1575 | B<NOTE>: Unlike C and other languages, Perl has no C<\v> escape sequence for |
8b312c40 | 1576 | the vertical tab (VT, which is 11 in both ASCII and EBCDIC), but you may |
ba7f043c | 1577 | use C<\N{VT}>, C<\ck>, C<\N{U+0b}>, or C<\x0b>. (C<\v> |
e526e8bb KW |
1578 | does have meaning in regular expression patterns in Perl, see L<perlre>.) |
1579 | ||
1580 | The following escape sequences are available in constructs that interpolate, | |
904501ec | 1581 | but not in transliterations. |
628253b8 | 1582 | X<\l> X<\u> X<\L> X<\U> X<\E> X<\Q> X<\F> |
904501ec | 1583 | |
c543c01b TC |
1584 | \l lowercase next character only |
1585 | \u titlecase (not uppercase!) next character only | |
e4d34742 EB |
1586 | \L lowercase all characters till \E or end of string |
1587 | \U uppercase all characters till \E or end of string | |
628253b8 | 1588 | \F foldcase all characters till \E or end of string |
736fe711 KW |
1589 | \Q quote (disable) pattern metacharacters till \E or |
1590 | end of string | |
7e31b643 | 1591 | \E end either case modification or quoted section |
c543c01b TC |
1592 | (whichever was last seen) |
1593 | ||
736fe711 KW |
1594 | See L<perlfunc/quotemeta> for the exact definition of characters that |
1595 | are quoted by C<\Q>. | |
1596 | ||
628253b8 | 1597 | C<\L>, C<\U>, C<\F>, and C<\Q> can stack, in which case you need one |
c543c01b TC |
1598 | C<\E> for each. For example: |
1599 | ||
9fef6a0d KW |
1600 | say"This \Qquoting \ubusiness \Uhere isn't quite\E done yet,\E is it?"; |
1601 | This quoting\ Business\ HERE\ ISN\'T\ QUITE\ done\ yet\, is it? | |
a0d0e21e | 1602 | |
ba7f043c KW |
1603 | If a S<C<use locale>> form that includes C<LC_CTYPE> is in effect (see |
1604 | L<perllocale>), the case map used by C<\l>, C<\L>, C<\u>, and C<\U> is | |
1605 | taken from the current locale. If Unicode (for example, C<\N{}> or code | |
1606 | points of 0x100 or beyond) is being used, the case map used by C<\l>, | |
1607 | C<\L>, C<\u>, and C<\U> is as defined by Unicode. That means that | |
1608 | case-mapping a single character can sometimes produce a sequence of | |
1609 | several characters. | |
1610 | Under S<C<use locale>>, C<\F> produces the same results as C<\L> | |
31f05a37 KW |
1611 | for all locales but a UTF-8 one, where it instead uses the Unicode |
1612 | definition. | |
a034a98d | 1613 | |
5a964f20 TC |
1614 | All systems use the virtual C<"\n"> to represent a line terminator, |
1615 | called a "newline". There is no such thing as an unvarying, physical | |
19799a22 | 1616 | newline character. It is only an illusion that the operating system, |
5a964f20 TC |
1617 | device drivers, C libraries, and Perl all conspire to preserve. Not all |
1618 | systems read C<"\r"> as ASCII CR and C<"\n"> as ASCII LF. For example, | |
c543c01b | 1619 | on the ancient Macs (pre-MacOS X) of yesteryear, these used to be reversed, |
ba7f043c | 1620 | and on systems without a line terminator, |
c543c01b | 1621 | printing C<"\n"> might emit no actual data. In general, use C<"\n"> when |
5a964f20 TC |
1622 | you mean a "newline" for your system, but use the literal ASCII when you |
1623 | need an exact character. For example, most networking protocols expect | |
2a380090 | 1624 | and prefer a CR+LF (C<"\015\012"> or C<"\cM\cJ">) for line terminators, |
5a964f20 TC |
1625 | and although they often accept just C<"\012">, they seldom tolerate just |
1626 | C<"\015">. If you get in the habit of using C<"\n"> for networking, | |
1627 | you may be burned some day. | |
d74e8afc ITB |
1628 | X<newline> X<line terminator> X<eol> X<end of line> |
1629 | X<\n> X<\r> X<\r\n> | |
5a964f20 | 1630 | |
904501ec MG |
1631 | For constructs that do interpolate, variables beginning with "C<$>" |
1632 | or "C<@>" are interpolated. Subscripted variables such as C<$a[3]> or | |
ad0f383a A |
1633 | C<< $href->{key}[0] >> are also interpolated, as are array and hash slices. |
1634 | But method calls such as C<< $obj->meth >> are not. | |
af9219ee MG |
1635 | |
1636 | Interpolating an array or slice interpolates the elements in order, | |
1637 | separated by the value of C<$">, so is equivalent to interpolating | |
ba7f043c | 1638 | S<C<join $", @array>>. "Punctuation" arrays such as C<@*> are usually |
c543c01b TC |
1639 | interpolated only if the name is enclosed in braces C<@{*}>, but the |
1640 | arrays C<@_>, C<@+>, and C<@-> are interpolated even without braces. | |
af9219ee | 1641 | |
bc7b91c6 EB |
1642 | For double-quoted strings, the quoting from C<\Q> is applied after |
1643 | interpolation and escapes are processed. | |
1644 | ||
1645 | "abc\Qfoo\tbar$s\Exyz" | |
1646 | ||
1647 | is equivalent to | |
1648 | ||
1649 | "abc" . quotemeta("foo\tbar$s") . "xyz" | |
1650 | ||
1651 | For the pattern of regex operators (C<qr//>, C<m//> and C<s///>), | |
1652 | the quoting from C<\Q> is applied after interpolation is processed, | |
46f8a5ea FC |
1653 | but before escapes are processed. This allows the pattern to match |
1654 | literally (except for C<$> and C<@>). For example, the following matches: | |
bc7b91c6 EB |
1655 | |
1656 | '\s\t' =~ /\Q\s\t/ | |
1657 | ||
1658 | Because C<$> or C<@> trigger interpolation, you'll need to use something | |
1659 | like C</\Quser\E\@\Qhost/> to match them literally. | |
1d2dff63 | 1660 | |
a0d0e21e LW |
1661 | Patterns are subject to an additional level of interpretation as a |
1662 | regular expression. This is done as a second pass, after variables are | |
1663 | interpolated, so that regular expressions may be incorporated into the | |
1664 | pattern from the variables. If this is not what you want, use C<\Q> to | |
1665 | interpolate a variable literally. | |
1666 | ||
19799a22 GS |
1667 | Apart from the behavior described above, Perl does not expand |
1668 | multiple levels of interpolation. In particular, contrary to the | |
1669 | expectations of shell programmers, back-quotes do I<NOT> interpolate | |
1670 | within double quotes, nor do single quotes impede evaluation of | |
1671 | variables when used within double quotes. | |
a0d0e21e | 1672 | |
5f05dabc | 1673 | =head2 Regexp Quote-Like Operators |
d74e8afc | 1674 | X<operator, regexp> |
cb1a09d0 | 1675 | |
5f05dabc | 1676 | Here are the quote-like operators that apply to pattern |
cb1a09d0 AD |
1677 | matching and related activities. |
1678 | ||
a0d0e21e LW |
1679 | =over 8 |
1680 | ||
ba7f043c | 1681 | =item C<qr/I<STRING>/msixpodualn> |
01c6f5f4 | 1682 | X<qr> X</i> X</m> X</o> X</s> X</x> X</p> |
a0d0e21e | 1683 | |
87e95b7f YO |
1684 | This operator quotes (and possibly compiles) its I<STRING> as a regular |
1685 | expression. I<STRING> is interpolated the same way as I<PATTERN> | |
6d314683 YO |
1686 | in C<m/I<PATTERN>/>. If C<"'"> is used as the delimiter, no variable |
1687 | interpolation is done. Returns a Perl value which may be used instead of the | |
ba7f043c | 1688 | corresponding C</I<STRING>/msixpodualn> expression. The returned value is a |
46f8a5ea | 1689 | normalized version of the original pattern. It magically differs from |
1c8ee595 CO |
1690 | a string containing the same characters: C<ref(qr/x/)> returns "Regexp"; |
1691 | however, dereferencing it is not well defined (you currently get the | |
1692 | normalized version of the original pattern, but this may change). | |
1693 | ||
a0d0e21e | 1694 | |
87e95b7f YO |
1695 | For example, |
1696 | ||
1697 | $rex = qr/my.STRING/is; | |
85dd5c8b | 1698 | print $rex; # prints (?si-xm:my.STRING) |
87e95b7f YO |
1699 | s/$rex/foo/; |
1700 | ||
1701 | is equivalent to | |
1702 | ||
1703 | s/my.STRING/foo/is; | |
1704 | ||
1705 | The result may be used as a subpattern in a match: | |
1706 | ||
1707 | $re = qr/$pattern/; | |
7188ca43 KW |
1708 | $string =~ /foo${re}bar/; # can be interpolated in other |
1709 | # patterns | |
87e95b7f YO |
1710 | $string =~ $re; # or used standalone |
1711 | $string =~ /$re/; # or this way | |
1712 | ||
ba7f043c KW |
1713 | Since Perl may compile the pattern at the moment of execution of the C<qr()> |
1714 | operator, using C<qr()> may have speed advantages in some situations, | |
1715 | notably if the result of C<qr()> is used standalone: | |
87e95b7f YO |
1716 | |
1717 | sub match { | |
1718 | my $patterns = shift; | |
1719 | my @compiled = map qr/$_/i, @$patterns; | |
1720 | grep { | |
1721 | my $success = 0; | |
1722 | foreach my $pat (@compiled) { | |
1723 | $success = 1, last if /$pat/; | |
1724 | } | |
1725 | $success; | |
1726 | } @_; | |
5a964f20 TC |
1727 | } |
1728 | ||
87e95b7f | 1729 | Precompilation of the pattern into an internal representation at |
ba7f043c | 1730 | the moment of C<qr()> avoids the need to recompile the pattern every |
87e95b7f YO |
1731 | time a match C</$pat/> is attempted. (Perl has many other internal |
1732 | optimizations, but none would be triggered in the above example if | |
ba7f043c | 1733 | we did not use C<qr()> operator.) |
87e95b7f | 1734 | |
765fa144 | 1735 | Options (specified by the following modifiers) are: |
87e95b7f YO |
1736 | |
1737 | m Treat string as multiple lines. | |
1738 | s Treat string as single line. (Make . match a newline) | |
1739 | i Do case-insensitive pattern matching. | |
1740 | x Use extended regular expressions. | |
1741 | p When matching preserve a copy of the matched string so | |
7188ca43 | 1742 | that ${^PREMATCH}, ${^MATCH}, ${^POSTMATCH} will be |
ba7f043c KW |
1743 | defined (ignored starting in v5.20) as these are always |
1744 | defined starting in that relese | |
87e95b7f | 1745 | o Compile pattern only once. |
7188ca43 | 1746 | a ASCII-restrict: Use ASCII for \d, \s, \w; specifying two |
ba7f043c KW |
1747 | a's further restricts things to that that no ASCII |
1748 | character will match a non-ASCII one under /i. | |
1749 | l Use the current run-time locale's rules. | |
48cbae4f SK |
1750 | u Use Unicode rules. |
1751 | d Use Unicode or native charset, as in 5.12 and earlier. | |
33be4c61 | 1752 | n Non-capture mode. Don't let () fill in $1, $2, etc... |
87e95b7f YO |
1753 | |
1754 | If a precompiled pattern is embedded in a larger pattern then the effect | |
ba7f043c KW |
1755 | of C<"msixpluadn"> will be propagated appropriately. The effect that the |
1756 | C</o> modifier has is not propagated, being restricted to those patterns | |
87e95b7f YO |
1757 | explicitly using it. |
1758 | ||
b6fa137b | 1759 | The last four modifiers listed above, added in Perl 5.14, |
850b7ec9 | 1760 | control the character set rules, but C</a> is the only one you are likely |
18509dec KW |
1761 | to want to specify explicitly; the other three are selected |
1762 | automatically by various pragmas. | |
da392a17 | 1763 | |
ba7f043c | 1764 | See L<perlre> for additional information on valid syntax for I<STRING>, and |
5e2aa8f5 | 1765 | for a detailed look at the semantics of regular expressions. In |
1ca345ed TC |
1766 | particular, all modifiers except the largely obsolete C</o> are further |
1767 | explained in L<perlre/Modifiers>. C</o> is described in the next section. | |
a0d0e21e | 1768 | |
ba7f043c | 1769 | =item C<m/I<PATTERN>/msixpodualngc> |
89d205f2 YO |
1770 | X<m> X<operator, match> |
1771 | X<regexp, options> X<regexp> X<regex, options> X<regex> | |
01c6f5f4 | 1772 | X</m> X</s> X</i> X</x> X</p> X</o> X</g> X</c> |
a0d0e21e | 1773 | |
ba7f043c | 1774 | =item C</I<PATTERN>/msixpodualngc> |
a0d0e21e | 1775 | |
5a964f20 | 1776 | Searches a string for a pattern match, and in scalar context returns |
19799a22 | 1777 | true if it succeeds, false if it fails. If no string is specified |
ba7f043c | 1778 | via the C<=~> or C<!~> operator, the C<$_> string is searched. (The |
19799a22 GS |
1779 | string specified with C<=~> need not be an lvalue--it may be the |
1780 | result of an expression evaluation, but remember the C<=~> binds | |
006671a6 | 1781 | rather tightly.) See also L<perlre>. |
a0d0e21e | 1782 | |
f6050459 | 1783 | Options are as described in C<qr//> above; in addition, the following match |
01c6f5f4 | 1784 | process modifiers are available: |
a0d0e21e | 1785 | |
950b09ed | 1786 | g Match globally, i.e., find all occurrences. |
7188ca43 KW |
1787 | c Do not reset search position on a failed match when /g is |
1788 | in effect. | |
a0d0e21e | 1789 | |
ba7f043c | 1790 | If C<"/"> is the delimiter then the initial C<m> is optional. With the C<m> |
c543c01b | 1791 | you can use any pair of non-whitespace (ASCII) characters |
725a61d7 | 1792 | as delimiters. This is particularly useful for matching path names |
ba7f043c | 1793 | that contain C<"/">, to avoid LTS (leaning toothpick syndrome). If C<"?"> is |
725a61d7 | 1794 | the delimiter, then a match-only-once rule applies, |
ba7f043c | 1795 | described in C<m?I<PATTERN>?> below. If C<"'"> (single quote) is the delimiter, |
6d314683 | 1796 | no variable interpolation is performed on the I<PATTERN>. |
ba7f043c | 1797 | When using a delimiter character valid in an identifier, whitespace is required |
ed02a3bf | 1798 | after the C<m>. |
a0d0e21e | 1799 | |
ba7f043c | 1800 | I<PATTERN> may contain variables, which will be interpolated |
532c9e80 | 1801 | every time the pattern search is evaluated, except |
1f247705 GS |
1802 | for when the delimiter is a single quote. (Note that C<$(>, C<$)>, and |
1803 | C<$|> are not interpolated because they look like end-of-string tests.) | |
532c9e80 KW |
1804 | Perl will not recompile the pattern unless an interpolated |
1805 | variable that it contains changes. You can force Perl to skip the | |
1806 | test and never recompile by adding a C</o> (which stands for "once") | |
1807 | after the trailing delimiter. | |
1808 | Once upon a time, Perl would recompile regular expressions | |
1809 | unnecessarily, and this modifier was useful to tell it not to do so, in the | |
5cc41653 | 1810 | interests of speed. But now, the only reasons to use C</o> are one of: |
532c9e80 KW |
1811 | |
1812 | =over | |
1813 | ||
1814 | =item 1 | |
1815 | ||
1816 | The variables are thousands of characters long and you know that they | |
1817 | don't change, and you need to wring out the last little bit of speed by | |
1818 | having Perl skip testing for that. (There is a maintenance penalty for | |
1819 | doing this, as mentioning C</o> constitutes a promise that you won't | |
18509dec | 1820 | change the variables in the pattern. If you do change them, Perl won't |
532c9e80 KW |
1821 | even notice.) |
1822 | ||
1823 | =item 2 | |
1824 | ||
1825 | you want the pattern to use the initial values of the variables | |
1826 | regardless of whether they change or not. (But there are saner ways | |
1827 | of accomplishing this than using C</o>.) | |
1828 | ||
fa9b8686 DM |
1829 | =item 3 |
1830 | ||
1831 | If the pattern contains embedded code, such as | |
1832 | ||
1833 | use re 'eval'; | |
1834 | $code = 'foo(?{ $x })'; | |
1835 | /$code/ | |
1836 | ||
1837 | then perl will recompile each time, even though the pattern string hasn't | |
1838 | changed, to ensure that the current value of C<$x> is seen each time. | |
1839 | Use C</o> if you want to avoid this. | |
1840 | ||
532c9e80 | 1841 | =back |
a0d0e21e | 1842 | |
18509dec KW |
1843 | The bottom line is that using C</o> is almost never a good idea. |
1844 | ||
ba7f043c | 1845 | =item The empty pattern C<//> |
e9d89077 | 1846 | |
ba7f043c | 1847 | If the I<PATTERN> evaluates to the empty string, the last |
46f8a5ea | 1848 | I<successfully> matched regular expression is used instead. In this |
c543c01b | 1849 | case, only the C<g> and C<c> flags on the empty pattern are honored; |
46f8a5ea | 1850 | the other flags are taken from the original pattern. If no match has |
d65afb4b HS |
1851 | previously succeeded, this will (silently) act instead as a genuine |
1852 | empty pattern (which will always match). | |
a0d0e21e | 1853 | |
89d205f2 YO |
1854 | Note that it's possible to confuse Perl into thinking C<//> (the empty |
1855 | regex) is really C<//> (the defined-or operator). Perl is usually pretty | |
1856 | good about this, but some pathological cases might trigger this, such as | |
ba7f043c KW |
1857 | C<$x///> (is that S<C<($x) / (//)>> or S<C<$x // />>?) and S<C<print $fh //>> |
1858 | (S<C<print $fh(//>> or S<C<print($fh //>>?). In all of these examples, Perl | |
89d205f2 YO |
1859 | will assume you meant defined-or. If you meant the empty regex, just |
1860 | use parentheses or spaces to disambiguate, or even prefix the empty | |
c963b151 BD |
1861 | regex with an C<m> (so C<//> becomes C<m//>). |
1862 | ||
e9d89077 DN |
1863 | =item Matching in list context |
1864 | ||
19799a22 | 1865 | If the C</g> option is not used, C<m//> in list context returns a |
a0d0e21e | 1866 | list consisting of the subexpressions matched by the parentheses in the |
3ff8ecf9 BF |
1867 | pattern, that is, (C<$1>, C<$2>, C<$3>...) (Note that here C<$1> etc. are |
1868 | also set). When there are no parentheses in the pattern, the return | |
1869 | value is the list C<(1)> for success. | |
1870 | With or without parentheses, an empty list is returned upon failure. | |
a0d0e21e LW |
1871 | |
1872 | Examples: | |
1873 | ||
7188ca43 KW |
1874 | open(TTY, "+</dev/tty") |
1875 | || die "can't access /dev/tty: $!"; | |
c543c01b | 1876 | |
7188ca43 | 1877 | <TTY> =~ /^y/i && foo(); # do foo if desired |
a0d0e21e | 1878 | |
7188ca43 | 1879 | if (/Version: *([0-9.]*)/) { $version = $1; } |
a0d0e21e | 1880 | |
7188ca43 | 1881 | next if m#^/usr/spool/uucp#; |
a0d0e21e | 1882 | |
7188ca43 KW |
1883 | # poor man's grep |
1884 | $arg = shift; | |
1885 | while (<>) { | |
1886 | print if /$arg/o; # compile only once (no longer needed!) | |
1887 | } | |
a0d0e21e | 1888 | |
7188ca43 | 1889 | if (($F1, $F2, $Etc) = ($foo =~ /^(\S+)\s+(\S+)\s*(.*)/)) |
a0d0e21e | 1890 | |
ba7f043c KW |
1891 | This last example splits C<$foo> into the first two words and the |
1892 | remainder of the line, and assigns those three fields to C<$F1>, C<$F2>, and | |
1893 | C<$Etc>. The conditional is true if any variables were assigned; that is, | |
c543c01b | 1894 | if the pattern matched. |
a0d0e21e | 1895 | |
19799a22 | 1896 | The C</g> modifier specifies global pattern matching--that is, |
46f8a5ea FC |
1897 | matching as many times as possible within the string. How it behaves |
1898 | depends on the context. In list context, it returns a list of the | |
19799a22 | 1899 | substrings matched by any capturing parentheses in the regular |
46f8a5ea | 1900 | expression. If there are no parentheses, it returns a list of all |
19799a22 GS |
1901 | the matched strings, as if there were parentheses around the whole |
1902 | pattern. | |
a0d0e21e | 1903 | |
7e86de3e | 1904 | In scalar context, each execution of C<m//g> finds the next match, |
19799a22 | 1905 | returning true if it matches, and false if there is no further match. |
3dd93342 | 1906 | The position after the last match can be read or set using the C<pos()> |
46f8a5ea | 1907 | function; see L<perlfunc/pos>. A failed match normally resets the |
7e86de3e | 1908 | search position to the beginning of the string, but you can avoid that |
46f8a5ea | 1909 | by adding the C</c> modifier (for example, C<m//gc>). Modifying the target |
7e86de3e | 1910 | string also resets the search position. |
c90c0ff4 | 1911 | |
ba7f043c | 1912 | =item C<\G I<assertion>> |
e9d89077 | 1913 | |
c90c0ff4 | 1914 | You can intermix C<m//g> matches with C<m/\G.../g>, where C<\G> is a |
3dd93342 | 1915 | zero-width assertion that matches the exact position where the |
46f8a5ea | 1916 | previous C<m//g>, if any, left off. Without the C</g> modifier, the |
3dd93342 | 1917 | C<\G> assertion still anchors at C<pos()> as it was at the start of |
1918 | the operation (see L<perlfunc/pos>), but the match is of course only | |
46f8a5ea | 1919 | attempted once. Using C<\G> without C</g> on a target string that has |
3dd93342 | 1920 | not previously had a C</g> match applied to it is the same as using |
1921 | the C<\A> assertion to match the beginning of the string. Note also | |
1922 | that, currently, C<\G> is only properly supported when anchored at the | |
1923 | very beginning of the pattern. | |
c90c0ff4 | 1924 | |
1925 | Examples: | |
a0d0e21e LW |
1926 | |
1927 | # list context | |
1928 | ($one,$five,$fifteen) = (`uptime` =~ /(\d+\.\d+)/g); | |
1929 | ||
1930 | # scalar context | |
c543c01b TC |
1931 | local $/ = ""; |
1932 | while ($paragraph = <>) { | |
1933 | while ($paragraph =~ /\p{Ll}['")]*[.!?]+['")]*\s/g) { | |
19799a22 | 1934 | $sentences++; |
a0d0e21e LW |
1935 | } |
1936 | } | |
c543c01b TC |
1937 | say $sentences; |
1938 | ||
1939 | Here's another way to check for sentences in a paragraph: | |
1940 | ||
7188ca43 KW |
1941 | my $sentence_rx = qr{ |
1942 | (?: (?<= ^ ) | (?<= \s ) ) # after start-of-string or | |
1943 | # whitespace | |
1944 | \p{Lu} # capital letter | |
1945 | .*? # a bunch of anything | |
1946 | (?<= \S ) # that ends in non- | |
1947 | # whitespace | |
1948 | (?<! \b [DMS]r ) # but isn't a common abbr. | |
1949 | (?<! \b Mrs ) | |
1950 | (?<! \b Sra ) | |
1951 | (?<! \b St ) | |
1952 | [.?!] # followed by a sentence | |
1953 | # ender | |
1954 | (?= $ | \s ) # in front of end-of-string | |
1955 | # or whitespace | |
1956 | }sx; | |
1957 | local $/ = ""; | |
1958 | while (my $paragraph = <>) { | |
1959 | say "NEW PARAGRAPH"; | |
1960 | my $count = 0; | |
1961 | while ($paragraph =~ /($sentence_rx)/g) { | |
1962 | printf "\tgot sentence %d: <%s>\n", ++$count, $1; | |
c543c01b | 1963 | } |
7188ca43 | 1964 | } |
c543c01b TC |
1965 | |
1966 | Here's how to use C<m//gc> with C<\G>: | |
a0d0e21e | 1967 | |
137443ea | 1968 | $_ = "ppooqppqq"; |
44a8e56a | 1969 | while ($i++ < 2) { |
1970 | print "1: '"; | |
c90c0ff4 | 1971 | print $1 while /(o)/gc; print "', pos=", pos, "\n"; |
44a8e56a | 1972 | print "2: '"; |
c90c0ff4 | 1973 | print $1 if /\G(q)/gc; print "', pos=", pos, "\n"; |
44a8e56a | 1974 | print "3: '"; |
c90c0ff4 | 1975 | print $1 while /(p)/gc; print "', pos=", pos, "\n"; |
44a8e56a | 1976 | } |
5d43e42d | 1977 | print "Final: '$1', pos=",pos,"\n" if /\G(.)/; |
44a8e56a | 1978 | |
1979 | The last example should print: | |
1980 | ||
1981 | 1: 'oo', pos=4 | |
137443ea | 1982 | 2: 'q', pos=5 |
44a8e56a | 1983 | 3: 'pp', pos=7 |
1984 | 1: '', pos=7 | |
137443ea | 1985 | 2: 'q', pos=8 |
1986 | 3: '', pos=8 | |
5d43e42d DC |
1987 | Final: 'q', pos=8 |
1988 | ||
1989 | Notice that the final match matched C<q> instead of C<p>, which a match | |
46f8a5ea FC |
1990 | without the C<\G> anchor would have done. Also note that the final match |
1991 | did not update C<pos>. C<pos> is only updated on a C</g> match. If the | |
c543c01b TC |
1992 | final match did indeed match C<p>, it's a good bet that you're running a |
1993 | very old (pre-5.6.0) version of Perl. | |
44a8e56a | 1994 | |
c90c0ff4 | 1995 | A useful idiom for C<lex>-like scanners is C</\G.../gc>. You can |
e7ea3e70 | 1996 | combine several regexps like this to process a string part-by-part, |
c90c0ff4 | 1997 | doing different actions depending on which regexp matched. Each |
1998 | regexp tries to match where the previous one leaves off. | |
e7ea3e70 | 1999 | |
3fe9a6f1 | 2000 | $_ = <<'EOL'; |
7188ca43 KW |
2001 | $url = URI::URL->new( "http://example.com/" ); |
2002 | die if $url eq "xXx"; | |
3fe9a6f1 | 2003 | EOL |
c543c01b TC |
2004 | |
2005 | LOOP: { | |
950b09ed | 2006 | print(" digits"), redo LOOP if /\G\d+\b[,.;]?\s*/gc; |
7188ca43 KW |
2007 | print(" lowercase"), redo LOOP |
2008 | if /\G\p{Ll}+\b[,.;]?\s*/gc; | |
2009 | print(" UPPERCASE"), redo LOOP | |
2010 | if /\G\p{Lu}+\b[,.;]?\s*/gc; | |
2011 | print(" Capitalized"), redo LOOP | |
2012 | if /\G\p{Lu}\p{Ll}+\b[,.;]?\s*/gc; | |
c543c01b | 2013 | print(" MiXeD"), redo LOOP if /\G\pL+\b[,.;]?\s*/gc; |
7188ca43 KW |
2014 | print(" alphanumeric"), redo LOOP |
2015 | if /\G[\p{Alpha}\pN]+\b[,.;]?\s*/gc; | |
c543c01b | 2016 | print(" line-noise"), redo LOOP if /\G\W+/gc; |
950b09ed | 2017 | print ". That's all!\n"; |
c543c01b | 2018 | } |
e7ea3e70 IZ |
2019 | |
2020 | Here is the output (split into several lines): | |
2021 | ||
7188ca43 KW |
2022 | line-noise lowercase line-noise UPPERCASE line-noise UPPERCASE |
2023 | line-noise lowercase line-noise lowercase line-noise lowercase | |
2024 | lowercase line-noise lowercase lowercase line-noise lowercase | |
2025 | lowercase line-noise MiXeD line-noise. That's all! | |
44a8e56a | 2026 | |
ba7f043c | 2027 | =item C<m?I<PATTERN>?msixpodualngc> |
725a61d7 | 2028 | X<?> X<operator, match-once> |
87e95b7f | 2029 | |
ba7f043c | 2030 | =item C<?I<PATTERN>?msixpodualngc> |
55d389e7 | 2031 | |
ba7f043c KW |
2032 | This is just like the C<m/I<PATTERN>/> search, except that it matches |
2033 | only once between calls to the C<reset()> operator. This is a useful | |
87e95b7f | 2034 | optimization when you want to see only the first occurrence of |
ceb131e8 | 2035 | something in each file of a set of files, for instance. Only C<m??> |
87e95b7f YO |
2036 | patterns local to the current package are reset. |
2037 | ||
2038 | while (<>) { | |
ceb131e8 | 2039 | if (m?^$?) { |
87e95b7f YO |
2040 | # blank line between header and body |
2041 | } | |
2042 | } continue { | |
725a61d7 | 2043 | reset if eof; # clear m?? status for next file |
87e95b7f YO |
2044 | } |
2045 | ||
c543c01b TC |
2046 | Another example switched the first "latin1" encoding it finds |
2047 | to "utf8" in a pod file: | |
2048 | ||
2049 | s//utf8/ if m? ^ =encoding \h+ \K latin1 ?x; | |
2050 | ||
2051 | The match-once behavior is controlled by the match delimiter being | |
4932eeca | 2052 | C<?>; with any other delimiter this is the normal C<m//> operator. |
725a61d7 | 2053 | |
ba7f043c | 2054 | In the past, the leading C<m> in C<m?I<PATTERN>?> was optional, but omitting it |
0381ecf1 MH |
2055 | would produce a deprecation warning. As of v5.22.0, omitting it produces a |
2056 | syntax error. If you encounter this construct in older code, you can just add | |
2057 | C<m>. | |
87e95b7f | 2058 | |
ba7f043c | 2059 | =item C<s/I<PATTERN>/I<REPLACEMENT>/msixpodualngcer> |
87e95b7f | 2060 | X<substitute> X<substitution> X<replace> X<regexp, replace> |
4f4d7508 | 2061 | X<regexp, substitute> X</m> X</s> X</i> X</x> X</p> X</o> X</g> X</c> X</e> X</r> |
87e95b7f YO |
2062 | |
2063 | Searches a string for a pattern, and if found, replaces that pattern | |
2064 | with the replacement text and returns the number of substitutions | |
2065 | made. Otherwise it returns false (specifically, the empty string). | |
2066 | ||
c543c01b | 2067 | If the C</r> (non-destructive) option is used then it runs the |
679563bb KW |
2068 | substitution on a copy of the string and instead of returning the |
2069 | number of substitutions, it returns the copy whether or not a | |
c543c01b TC |
2070 | substitution occurred. The original string is never changed when |
2071 | C</r> is used. The copy will always be a plain string, even if the | |
2072 | input is an object or a tied variable. | |
4f4d7508 | 2073 | |
87e95b7f | 2074 | If no string is specified via the C<=~> or C<!~> operator, the C<$_> |
c543c01b TC |
2075 | variable is searched and modified. Unless the C</r> option is used, |
2076 | the string specified must be a scalar variable, an array element, a | |
2077 | hash element, or an assignment to one of those; that is, some sort of | |
2078 | scalar lvalue. | |
87e95b7f | 2079 | |
6d314683 | 2080 | If the delimiter chosen is a single quote, no variable interpolation is |
ba7f043c KW |
2081 | done on either the I<PATTERN> or the I<REPLACEMENT>. Otherwise, if the |
2082 | I<PATTERN> contains a C<$> that looks like a variable rather than an | |
87e95b7f YO |
2083 | end-of-string test, the variable will be interpolated into the pattern |
2084 | at run-time. If you want the pattern compiled only once the first time | |
2085 | the variable is interpolated, use the C</o> option. If the pattern | |
2086 | evaluates to the empty string, the last successfully executed regular | |
2087 | expression is used instead. See L<perlre> for further explanation on these. | |
87e95b7f | 2088 | |
ba7f043c | 2089 | Options are as with C<m//> with the addition of the following replacement |
87e95b7f YO |
2090 | specific options: |
2091 | ||
2092 | e Evaluate the right side as an expression. | |
7188ca43 KW |
2093 | ee Evaluate the right side as a string then eval the |
2094 | result. | |
2095 | r Return substitution and leave the original string | |
2096 | untouched. | |
87e95b7f | 2097 | |
ed02a3bf DN |
2098 | Any non-whitespace delimiter may replace the slashes. Add space after |
2099 | the C<s> when using a character allowed in identifiers. If single quotes | |
2100 | are used, no interpretation is done on the replacement string (the C</e> | |
3ff8ecf9 | 2101 | modifier overrides this, however). Note that Perl treats backticks |
ed02a3bf | 2102 | as normal delimiters; the replacement text is not evaluated as a command. |
ba7f043c | 2103 | If the I<PATTERN> is delimited by bracketing quotes, the I<REPLACEMENT> has |
1ca345ed | 2104 | its own pair of quotes, which may or may not be bracketing quotes, for example, |
87e95b7f YO |
2105 | C<s(foo)(bar)> or C<< s<foo>/bar/ >>. A C</e> will cause the |
2106 | replacement portion to be treated as a full-fledged Perl expression | |
2107 | and evaluated right then and there. It is, however, syntax checked at | |
46f8a5ea | 2108 | compile-time. A second C<e> modifier will cause the replacement portion |
87e95b7f YO |
2109 | to be C<eval>ed before being run as a Perl expression. |
2110 | ||
2111 | Examples: | |
2112 | ||
7188ca43 | 2113 | s/\bgreen\b/mauve/g; # don't change wintergreen |
87e95b7f YO |
2114 | |
2115 | $path =~ s|/usr/bin|/usr/local/bin|; | |
2116 | ||
2117 | s/Login: $foo/Login: $bar/; # run-time pattern | |
2118 | ||
7188ca43 KW |
2119 | ($foo = $bar) =~ s/this/that/; # copy first, then |
2120 | # change | |
2121 | ($foo = "$bar") =~ s/this/that/; # convert to string, | |
2122 | # copy, then change | |
4f4d7508 DC |
2123 | $foo = $bar =~ s/this/that/r; # Same as above using /r |
2124 | $foo = $bar =~ s/this/that/r | |
7188ca43 KW |
2125 | =~ s/that/the other/r; # Chained substitutes |
2126 | # using /r | |
2127 | @foo = map { s/this/that/r } @bar # /r is very useful in | |
2128 | # maps | |
87e95b7f | 2129 | |
7188ca43 | 2130 | $count = ($paragraph =~ s/Mister\b/Mr./g); # get change-cnt |
87e95b7f YO |
2131 | |
2132 | $_ = 'abc123xyz'; | |
2133 | s/\d+/$&*2/e; # yields 'abc246xyz' | |
2134 | s/\d+/sprintf("%5d",$&)/e; # yields 'abc 246xyz' | |
2135 | s/\w/$& x 2/eg; # yields 'aabbcc 224466xxyyzz' | |
2136 | ||
2137 | s/%(.)/$percent{$1}/g; # change percent escapes; no /e | |
2138 | s/%(.)/$percent{$1} || $&/ge; # expr now, so /e | |
2139 | s/^=(\w+)/pod($1)/ge; # use function call | |
2140 | ||
4f4d7508 | 2141 | $_ = 'abc123xyz'; |
db691027 | 2142 | $x = s/abc/def/r; # $x is 'def123xyz' and |
4f4d7508 DC |
2143 | # $_ remains 'abc123xyz'. |
2144 | ||
87e95b7f YO |
2145 | # expand variables in $_, but dynamics only, using |
2146 | # symbolic dereferencing | |
2147 | s/\$(\w+)/${$1}/g; | |
2148 | ||
2149 | # Add one to the value of any numbers in the string | |
2150 | s/(\d+)/1 + $1/eg; | |
2151 | ||
c543c01b TC |
2152 | # Titlecase words in the last 30 characters only |
2153 | substr($str, -30) =~ s/\b(\p{Alpha}+)\b/\u\L$1/g; | |
2154 | ||
87e95b7f YO |
2155 | # This will expand any embedded scalar variable |
2156 | # (including lexicals) in $_ : First $1 is interpolated | |
2157 | # to the variable name, and then evaluated | |
2158 | s/(\$\w+)/$1/eeg; | |
2159 | ||
2160 | # Delete (most) C comments. | |
2161 | $program =~ s { | |
2162 | /\* # Match the opening delimiter. | |
2163 | .*? # Match a minimal number of characters. | |
2164 | \*/ # Match the closing delimiter. | |
2165 | } []gsx; | |
2166 | ||
7188ca43 KW |
2167 | s/^\s*(.*?)\s*$/$1/; # trim whitespace in $_, |
2168 | # expensively | |
87e95b7f | 2169 | |
7188ca43 KW |
2170 | for ($variable) { # trim whitespace in $variable, |
2171 | # cheap | |
87e95b7f YO |
2172 | s/^\s+//; |
2173 | s/\s+$//; | |
2174 | } | |
2175 | ||
2176 | s/([^ ]*) *([^ ]*)/$2 $1/; # reverse 1st two fields | |
2177 | ||
ba7f043c KW |
2178 | Note the use of C<$> instead of C<\> in the last example. Unlike |
2179 | B<sed>, we use the \<I<digit>> form only in the left hand side. | |
87e95b7f YO |
2180 | Anywhere else it's $<I<digit>>. |
2181 | ||
2182 | Occasionally, you can't use just a C</g> to get all the changes | |
2183 | to occur that you might want. Here are two common cases: | |
2184 | ||
2185 | # put commas in the right places in an integer | |
2186 | 1 while s/(\d)(\d\d\d)(?!\d)/$1,$2/g; | |
2187 | ||
2188 | # expand tabs to 8-column spacing | |
2189 | 1 while s/\t+/' ' x (length($&)*8 - length($`)%8)/e; | |
2190 | ||
2191 | =back | |
2192 | ||
2193 | =head2 Quote-Like Operators | |
2194 | X<operator, quote-like> | |
2195 | ||
01c6f5f4 RGS |
2196 | =over 4 |
2197 | ||
ba7f043c | 2198 | =item C<q/I<STRING>/> |
5d44bfff | 2199 | X<q> X<quote, single> X<'> X<''> |
a0d0e21e | 2200 | |
ba7f043c | 2201 | =item C<'I<STRING>'> |
a0d0e21e | 2202 | |
19799a22 | 2203 | A single-quoted, literal string. A backslash represents a backslash |
68dc0745 | 2204 | unless followed by the delimiter or another backslash, in which case |
2205 | the delimiter or backslash is interpolated. | |
a0d0e21e LW |
2206 | |
2207 | $foo = q!I said, "You said, 'She said it.'"!; | |
2208 | $bar = q('This is it.'); | |
68dc0745 | 2209 | $baz = '\n'; # a two-character string |
a0d0e21e | 2210 | |
ba7f043c | 2211 | =item C<qq/I<STRING>/> |
d74e8afc | 2212 | X<qq> X<quote, double> X<"> X<""> |
a0d0e21e | 2213 | |
ba7f043c | 2214 | =item "I<STRING>" |
a0d0e21e LW |
2215 | |
2216 | A double-quoted, interpolated string. | |
2217 | ||
2218 | $_ .= qq | |
2219 | (*** The previous line contains the naughty word "$1".\n) | |
19799a22 | 2220 | if /\b(tcl|java|python)\b/i; # :-) |
68dc0745 | 2221 | $baz = "\n"; # a one-character string |
a0d0e21e | 2222 | |
ba7f043c | 2223 | =item C<qx/I<STRING>/> |
d74e8afc | 2224 | X<qx> X<`> X<``> X<backtick> |
a0d0e21e | 2225 | |
ba7f043c | 2226 | =item C<`I<STRING>`> |
a0d0e21e | 2227 | |
43dd4d21 | 2228 | A string which is (possibly) interpolated and then executed as a |
f703fc96 | 2229 | system command with F</bin/sh> or its equivalent. Shell wildcards, |
43dd4d21 JH |
2230 | pipes, and redirections will be honored. The collected standard |
2231 | output of the command is returned; standard error is unaffected. In | |
2232 | scalar context, it comes back as a single (potentially multi-line) | |
ba7f043c KW |
2233 | string, or C<undef> if the command failed. In list context, returns a |
2234 | list of lines (however you've defined lines with C<$/> or | |
2235 | C<$INPUT_RECORD_SEPARATOR>), or an empty list if the command failed. | |
5a964f20 TC |
2236 | |
2237 | Because backticks do not affect standard error, use shell file descriptor | |
2238 | syntax (assuming the shell supports this) if you care to address this. | |
2239 | To capture a command's STDERR and STDOUT together: | |
a0d0e21e | 2240 | |
5a964f20 TC |
2241 | $output = `cmd 2>&1`; |
2242 | ||
2243 | To capture a command's STDOUT but discard its STDERR: | |
2244 | ||
2245 | $output = `cmd 2>/dev/null`; | |
2246 | ||
2247 | To capture a command's STDERR but discard its STDOUT (ordering is | |
2248 | important here): | |
2249 | ||
2250 | $output = `cmd 2>&1 1>/dev/null`; | |
2251 | ||
2252 | To exchange a command's STDOUT and STDERR in order to capture the STDERR | |
2253 | but leave its STDOUT to come out the old STDERR: | |
2254 | ||
2255 | $output = `cmd 3>&1 1>&2 2>&3 3>&-`; | |
2256 | ||
2257 | To read both a command's STDOUT and its STDERR separately, it's easiest | |
2359510d SD |
2258 | to redirect them separately to files, and then read from those files |
2259 | when the program is done: | |
5a964f20 | 2260 | |
2359510d | 2261 | system("program args 1>program.stdout 2>program.stderr"); |
5a964f20 | 2262 | |
30398227 SP |
2263 | The STDIN filehandle used by the command is inherited from Perl's STDIN. |
2264 | For example: | |
2265 | ||
c543c01b TC |
2266 | open(SPLAT, "stuff") || die "can't open stuff: $!"; |
2267 | open(STDIN, "<&SPLAT") || die "can't dupe SPLAT: $!"; | |
40bbb707 | 2268 | print STDOUT `sort`; |
30398227 | 2269 | |
40bbb707 | 2270 | will print the sorted contents of the file named F<"stuff">. |
30398227 | 2271 | |
5a964f20 TC |
2272 | Using single-quote as a delimiter protects the command from Perl's |
2273 | double-quote interpolation, passing it on to the shell instead: | |
2274 | ||
2275 | $perl_info = qx(ps $$); # that's Perl's $$ | |
2276 | $shell_info = qx'ps $$'; # that's the new shell's $$ | |
2277 | ||
19799a22 | 2278 | How that string gets evaluated is entirely subject to the command |
5a964f20 TC |
2279 | interpreter on your system. On most platforms, you will have to protect |
2280 | shell metacharacters if you want them treated literally. This is in | |
2281 | practice difficult to do, as it's unclear how to escape which characters. | |
ba7f043c | 2282 | See L<perlsec> for a clean and safe example of a manual C<fork()> and C<exec()> |
5a964f20 | 2283 | to emulate backticks safely. |
a0d0e21e | 2284 | |
bb32b41a GS |
2285 | On some platforms (notably DOS-like ones), the shell may not be |
2286 | capable of dealing with multiline commands, so putting newlines in | |
2287 | the string may not get you what you want. You may be able to evaluate | |
2288 | multiple commands in a single line by separating them with the command | |
1ca345ed TC |
2289 | separator character, if your shell supports that (for example, C<;> on |
2290 | many Unix shells and C<&> on the Windows NT C<cmd> shell). | |
bb32b41a | 2291 | |
3ff8ecf9 | 2292 | Perl will attempt to flush all files opened for |
0f897271 GS |
2293 | output before starting the child process, but this may not be supported |
2294 | on some platforms (see L<perlport>). To be safe, you may need to set | |
ba7f043c KW |
2295 | C<$|> (C<$AUTOFLUSH> in C<L<English>>) or call the C<autoflush()> method of |
2296 | C<L<IO::Handle>> on any open handles. | |
0f897271 | 2297 | |
bb32b41a GS |
2298 | Beware that some command shells may place restrictions on the length |
2299 | of the command line. You must ensure your strings don't exceed this | |
2300 | limit after any necessary interpolations. See the platform-specific | |
2301 | release notes for more details about your particular environment. | |
2302 | ||
5a964f20 TC |
2303 | Using this operator can lead to programs that are difficult to port, |
2304 | because the shell commands called vary between systems, and may in | |
2305 | fact not be present at all. As one example, the C<type> command under | |
2306 | the POSIX shell is very different from the C<type> command under DOS. | |
2307 | That doesn't mean you should go out of your way to avoid backticks | |
2308 | when they're the right way to get something done. Perl was made to be | |
2309 | a glue language, and one of the things it glues together is commands. | |
2310 | Just understand what you're getting yourself into. | |
bb32b41a | 2311 | |
7cf4dd3e DB |
2312 | Like C<system>, backticks put the child process exit code in C<$?>. |
2313 | If you'd like to manually inspect failure, you can check all possible | |
2314 | failure modes by inspecting C<$?> like this: | |
2315 | ||
2316 | if ($? == -1) { | |
2317 | print "failed to execute: $!\n"; | |
2318 | } | |
2319 | elsif ($? & 127) { | |
2320 | printf "child died with signal %d, %s coredump\n", | |
2321 | ($? & 127), ($? & 128) ? 'with' : 'without'; | |
2322 | } | |
2323 | else { | |
2324 | printf "child exited with value %d\n", $? >> 8; | |
2325 | } | |
2326 | ||
fe43a9cc TC |
2327 | Use the L<open> pragma to control the I/O layers used when reading the |
2328 | output of the command, for example: | |
2329 | ||
2330 | use open IN => ":encoding(UTF-8)"; | |
2331 | my $x = `cmd-producing-utf-8`; | |
2332 | ||
da87341d | 2333 | See L</"I/O Operators"> for more discussion. |
a0d0e21e | 2334 | |
ba7f043c | 2335 | =item C<qw/I<STRING>/> |
d74e8afc | 2336 | X<qw> X<quote, list> X<quote, words> |
945c54fd | 2337 | |
ba7f043c | 2338 | Evaluates to a list of the words extracted out of I<STRING>, using embedded |
945c54fd JH |
2339 | whitespace as the word delimiters. It can be understood as being roughly |
2340 | equivalent to: | |
2341 | ||
c543c01b | 2342 | split(" ", q/STRING/); |
945c54fd | 2343 | |
efb1e162 CW |
2344 | the differences being that it generates a real list at compile time, and |
2345 | in scalar context it returns the last element in the list. So | |
945c54fd JH |
2346 | this expression: |
2347 | ||
2348 | qw(foo bar baz) | |
2349 | ||
2350 | is semantically equivalent to the list: | |
2351 | ||
c543c01b | 2352 | "foo", "bar", "baz" |
945c54fd JH |
2353 | |
2354 | Some frequently seen examples: | |
2355 | ||
2356 | use POSIX qw( setlocale localeconv ) | |
2357 | @EXPORT = qw( foo bar baz ); | |
2358 | ||
ba7f043c | 2359 | A common mistake is to try to separate the words with commas or to |
945c54fd | 2360 | put comments into a multi-line C<qw>-string. For this reason, the |
ba7f043c KW |
2361 | S<C<use warnings>> pragma and the B<-w> switch (that is, the C<$^W> variable) |
2362 | produces warnings if the I<STRING> contains the C<","> or the C<"#"> character. | |
945c54fd | 2363 | |
ba7f043c | 2364 | =item C<tr/I<SEARCHLIST>/I<REPLACEMENTLIST>/cdsr> |
d74e8afc | 2365 | X<tr> X<y> X<transliterate> X</c> X</d> X</s> |
a0d0e21e | 2366 | |
ba7f043c | 2367 | =item C<y/I<SEARCHLIST>/I<REPLACEMENTLIST>/cdsr> |
a0d0e21e | 2368 | |
2c268ad5 | 2369 | Transliterates all occurrences of the characters found in the search list |
a0d0e21e LW |
2370 | with the corresponding character in the replacement list. It returns |
2371 | the number of characters replaced or deleted. If no string is | |
ba7f043c | 2372 | specified via the C<=~> or C<!~> operator, the C<$_> string is transliterated. |
c543c01b TC |
2373 | |
2374 | If the C</r> (non-destructive) option is present, a new copy of the string | |
2375 | is made and its characters transliterated, and this copy is returned no | |
2376 | matter whether it was modified or not: the original string is always | |
2377 | left unchanged. The new copy is always a plain string, even if the input | |
2378 | string is an object or a tied variable. | |
8ada0baa | 2379 | |
c543c01b TC |
2380 | Unless the C</r> option is used, the string specified with C<=~> must be a |
2381 | scalar variable, an array element, a hash element, or an assignment to one | |
2382 | of those; in other words, an lvalue. | |
8ff32507 | 2383 | |
89d205f2 | 2384 | A character range may be specified with a hyphen, so C<tr/A-J/0-9/> |
2c268ad5 | 2385 | does the same replacement as C<tr/ACEGIBDFHJ/0246813579/>. |
54310121 | 2386 | For B<sed> devotees, C<y> is provided as a synonym for C<tr>. If the |
af2cbe4d KW |
2387 | I<SEARCHLIST> is delimited by bracketing quotes, the I<REPLACEMENTLIST> |
2388 | must have its own pair of quotes, which may or may not be bracketing | |
2389 | quotes; for example, C<tr[aeiouy][yuoiea]> or C<tr(+\-*/)/ABCD/>. | |
c543c01b | 2390 | |
ba7f043c | 2391 | Characters may be literals or any of the escape sequences accepted in |
6d314683 YO |
2392 | double-quoted strings. But there is no variable interpolation, so C<"$"> |
2393 | and C<"@"> are treated as literals. A hyphen at the beginning or end, or | |
ba7f043c KW |
2394 | preceded by a backslash is considered a literal. Escape sequence |
2395 | details are in L<the table near the beginning of this section|/Quote and | |
f4240379 | 2396 | Quote-like Operators>. |
ba7f043c | 2397 | |
c543c01b | 2398 | Note that C<tr> does B<not> do regular expression character classes such as |
ba7f043c | 2399 | C<\d> or C<\pL>. The C<tr> operator is not equivalent to the C<L<tr(1)>> |
af2cbe4d KW |
2400 | utility. C<tr[a-z][A-Z]> will uppercase the 26 letters "a" through "z", |
2401 | but for case changing not confined to ASCII, use | |
2402 | L<C<lc>|perlfunc/lc>, L<C<uc>|perlfunc/uc>, | |
2403 | L<C<lcfirst>|perlfunc/lcfirst>, L<C<ucfirst>|perlfunc/ucfirst> | |
2404 | (all documented in L<perlfunc>), or the | |
2405 | L<substitution operator C<sE<sol>I<PATTERN>E<sol>I<REPLACEMENT>E<sol>>|/sE<sol>PATTERNE<sol>REPLACEMENTE<sol>msixpodualngcer> | |
2406 | (with C<\U>, C<\u>, C<\L>, and C<\l> string-interpolation escapes in the | |
2407 | I<REPLACEMENT> portion). | |
cc255d5f | 2408 | |
f4240379 KW |
2409 | Most ranges are unportable between character sets, but certain ones |
2410 | signal Perl to do special handling to make them portable. There are two | |
2411 | classes of portable ranges. The first are any subsets of the ranges | |
2412 | C<A-Z>, C<a-z>, and C<0-9>, when expressed as literal characters. | |
2413 | ||
2414 | tr/h-k/H-K/ | |
2415 | ||
2416 | capitalizes the letters C<"h">, C<"i">, C<"j">, and C<"k"> and nothing | |
2417 | else, no matter what the platform's character set is. In contrast, all | |
2418 | of | |
2419 | ||
2420 | tr/\x68-\x6B/\x48-\x4B/ | |
2421 | tr/h-\x6B/H-\x4B/ | |
2422 | tr/\x68-k/\x48-K/ | |
2423 | ||
2424 | do the same capitalizations as the previous example when run on ASCII | |
2425 | platforms, but something completely different on EBCDIC ones. | |
2426 | ||
2427 | The second class of portable ranges is invoked when one or both of the | |
2428 | range's end points are expressed as C<\N{...}> | |
2429 | ||
2430 | $string =~ tr/\N{U+20}-\N{U+7E}//d; | |
2431 | ||
2432 | removes from C<$string> all the platform's characters which are | |
2433 | equivalent to any of Unicode U+0020, U+0021, ... U+007D, U+007E. This | |
2434 | is a portable range, and has the same effect on every platform it is | |
2435 | run on. It turns out that in this example, these are the ASCII | |
2436 | printable characters. So after this is run, C<$string> has only | |
2437 | controls and characters which have no ASCII equivalents. | |
2438 | ||
2439 | But, even for portable ranges, it is not generally obvious what is | |
2440 | included without having to look things up. A sound principle is to use | |
2441 | only ranges that begin from and end at either ASCII alphabetics of equal | |
8df98a27 | 2442 | case (C<b-e>, C<B-E>), or digits (C<1-4>). Anything else is unclear |
f4240379 | 2443 | (and unportable unless C<\N{...}> is used). If in doubt, spell out the |
8ada0baa JH |
2444 | character sets in full. |
2445 | ||
a0d0e21e LW |
2446 | Options: |
2447 | ||
2448 | c Complement the SEARCHLIST. | |
2449 | d Delete found but unreplaced characters. | |
2450 | s Squash duplicate replaced characters. | |
8ff32507 FC |
2451 | r Return the modified string and leave the original string |
2452 | untouched. | |
a0d0e21e | 2453 | |
ba7f043c | 2454 | If the C</c> modifier is specified, the I<SEARCHLIST> character set |
19799a22 | 2455 | is complemented. If the C</d> modifier is specified, any characters |
ba7f043c | 2456 | specified by I<SEARCHLIST> not found in I<REPLACEMENTLIST> are deleted. |
19799a22 | 2457 | (Note that this is slightly more flexible than the behavior of some |
ba7f043c | 2458 | B<tr> programs, which delete anything they find in the I<SEARCHLIST>, |
46f8a5ea | 2459 | period.) If the C</s> modifier is specified, sequences of characters |
19799a22 GS |
2460 | that were transliterated to the same character are squashed down |
2461 | to a single instance of the character. | |
a0d0e21e | 2462 | |
ba7f043c KW |
2463 | If the C</d> modifier is used, the I<REPLACEMENTLIST> is always interpreted |
2464 | exactly as specified. Otherwise, if the I<REPLACEMENTLIST> is shorter | |
2465 | than the I<SEARCHLIST>, the final character is replicated till it is long | |
2466 | enough. If the I<REPLACEMENTLIST> is empty, the I<SEARCHLIST> is replicated. | |
a0d0e21e LW |
2467 | This latter is useful for counting characters in a class or for |
2468 | squashing character sequences in a class. | |
2469 | ||
2470 | Examples: | |
2471 | ||
c543c01b | 2472 | $ARGV[1] =~ tr/A-Z/a-z/; # canonicalize to lower case ASCII |
a0d0e21e LW |
2473 | |
2474 | $cnt = tr/*/*/; # count the stars in $_ | |
2475 | ||
2476 | $cnt = $sky =~ tr/*/*/; # count the stars in $sky | |
2477 | ||
2478 | $cnt = tr/0-9//; # count the digits in $_ | |
2479 | ||
2480 | tr/a-zA-Z//s; # bookkeeper -> bokeper | |
2481 | ||
2482 | ($HOST = $host) =~ tr/a-z/A-Z/; | |
c543c01b | 2483 | $HOST = $host =~ tr/a-z/A-Z/r; # same thing |
8ff32507 | 2484 | |
c543c01b | 2485 | $HOST = $host =~ tr/a-z/A-Z/r # chained with s///r |
8ff32507 | 2486 | =~ s/:/ -p/r; |
a0d0e21e LW |
2487 | |
2488 | tr/a-zA-Z/ /cs; # change non-alphas to single space | |
2489 | ||
8ff32507 FC |
2490 | @stripped = map tr/a-zA-Z/ /csr, @original; |
2491 | # /r with map | |
2492 | ||
a0d0e21e | 2493 | tr [\200-\377] |
c543c01b | 2494 | [\000-\177]; # wickedly delete 8th bit |
a0d0e21e | 2495 | |
19799a22 GS |
2496 | If multiple transliterations are given for a character, only the |
2497 | first one is used: | |
748a9306 LW |
2498 | |
2499 | tr/AAA/XYZ/ | |
2500 | ||
2c268ad5 | 2501 | will transliterate any A to X. |
748a9306 | 2502 | |
19799a22 | 2503 | Because the transliteration table is built at compile time, neither |
ba7f043c | 2504 | the I<SEARCHLIST> nor the I<REPLACEMENTLIST> are subjected to double quote |
19799a22 | 2505 | interpolation. That means that if you want to use variables, you |
ba7f043c | 2506 | must use an C<eval()>: |
a0d0e21e LW |
2507 | |
2508 | eval "tr/$oldlist/$newlist/"; | |
2509 | die $@ if $@; | |
2510 | ||
2511 | eval "tr/$oldlist/$newlist/, 1" or die $@; | |
2512 | ||
ba7f043c | 2513 | =item C<< <<I<EOF> >> |
d74e8afc | 2514 | X<here-doc> X<heredoc> X<here-document> X<<< << >>> |
7e3b091d DA |
2515 | |
2516 | A line-oriented form of quoting is based on the shell "here-document" | |
2517 | syntax. Following a C<< << >> you specify a string to terminate | |
2518 | the quoted material, and all lines following the current line down to | |
89d205f2 YO |
2519 | the terminating string are the value of the item. |
2520 | ||
47eb4411 MH |
2521 | Prefixing the terminating string with a C<~> specifies that you |
2522 | want to use L</Indented Here-docs> (see below). | |
2523 | ||
89d205f2 YO |
2524 | The terminating string may be either an identifier (a word), or some |
2525 | quoted text. An unquoted identifier works like double quotes. | |
2526 | There may not be a space between the C<< << >> and the identifier, | |
2527 | unless the identifier is explicitly quoted. (If you put a space it | |
2528 | will be treated as a null identifier, which is valid, and matches the | |
2529 | first empty line.) The terminating string must appear by itself | |
2530 | (unquoted and with no surrounding whitespace) on the terminating line. | |
2531 | ||
2532 | If the terminating string is quoted, the type of quotes used determine | |
2533 | the treatment of the text. | |
2534 | ||
2535 | =over 4 | |
2536 | ||
2537 | =item Double Quotes | |
2538 | ||
2539 | Double quotes indicate that the text will be interpolated using exactly | |
2540 | the same rules as normal double quoted strings. | |
7e3b091d DA |
2541 | |
2542 | print <<EOF; | |
2543 | The price is $Price. | |
2544 | EOF | |
2545 | ||
2546 | print << "EOF"; # same as above | |
2547 | The price is $Price. | |
2548 | EOF | |
2549 | ||
89d205f2 YO |
2550 | |
2551 | =item Single Quotes | |
2552 | ||
2553 | Single quotes indicate the text is to be treated literally with no | |
46f8a5ea | 2554 | interpolation of its content. This is similar to single quoted |
89d205f2 YO |
2555 | strings except that backslashes have no special meaning, with C<\\> |
2556 | being treated as two backslashes and not one as they would in every | |
2557 | other quoting construct. | |
2558 | ||
c543c01b TC |
2559 | Just as in the shell, a backslashed bareword following the C<<< << >>> |
2560 | means the same thing as a single-quoted string does: | |
2561 | ||
2562 | $cost = <<'VISTA'; # hasta la ... | |
2563 | That'll be $10 please, ma'am. | |
2564 | VISTA | |
2565 | ||
2566 | $cost = <<\VISTA; # Same thing! | |
2567 | That'll be $10 please, ma'am. | |
2568 | VISTA | |
2569 | ||
89d205f2 YO |
2570 | This is the only form of quoting in perl where there is no need |
2571 | to worry about escaping content, something that code generators | |
2572 | can and do make good use of. | |
2573 | ||
2574 | =item Backticks | |
2575 | ||
2576 | The content of the here doc is treated just as it would be if the | |
46f8a5ea | 2577 | string were embedded in backticks. Thus the content is interpolated |
89d205f2 YO |
2578 | as though it were double quoted and then executed via the shell, with |
2579 | the results of the execution returned. | |
2580 | ||
2581 | print << `EOC`; # execute command and get results | |
7e3b091d | 2582 | echo hi there |
7e3b091d DA |
2583 | EOC |
2584 | ||
89d205f2 YO |
2585 | =back |
2586 | ||
47eb4411 MH |
2587 | =over 4 |
2588 | ||
2589 | =item Indented Here-docs | |
2590 | ||
2591 | The here-doc modifier C<~> allows you to indent your here-docs to make | |
2592 | the code more readable: | |
2593 | ||
2594 | if ($some_var) { | |
2595 | print <<~EOF; | |
2596 | This is a here-doc | |
2597 | EOF | |
2598 | } | |
2599 | ||
2600 | This will print... | |
2601 | ||
2602 | This is a here-doc | |
2603 | ||
2604 | ...with no leading whitespace. | |
2605 | ||
2606 | The delimiter is used to determine the B<exact> whitespace to | |
2607 | remove from the beginning of each line. All lines B<must> have | |
2608 | at least the same starting whitespace (except lines only | |
2609 | containing a newline) or perl will croak. Tabs and spaces can | |
2610 | be mixed, but are matched exactly. One tab will not be equal to | |
2611 | 8 spaces! | |
2612 | ||
2613 | Additional beginning whitespace (beyond what preceded the | |
2614 | delimiter) will be preserved: | |
2615 | ||
2616 | print <<~EOF; | |
2617 | This text is not indented | |
2618 | This text is indented with two spaces | |
2619 | This text is indented with two tabs | |
2620 | EOF | |
2621 | ||
2622 | Finally, the modifier may be used with all of the forms | |
2623 | mentioned above: | |
2624 | ||
2625 | <<~\EOF; | |
2626 | <<~'EOF' | |
2627 | <<~"EOF" | |
2628 | <<~`EOF` | |
2629 | ||
2630 | And whitespace may be used between the C<~> and quoted delimiters: | |
2631 | ||
2632 | <<~ 'EOF'; # ... "EOF", `EOF` | |
2633 | ||
2634 | =back | |
2635 | ||
89d205f2 YO |
2636 | It is possible to stack multiple here-docs in a row: |
2637 | ||
7e3b091d DA |
2638 | print <<"foo", <<"bar"; # you can stack them |
2639 | I said foo. | |
2640 | foo | |
2641 | I said bar. | |
2642 | bar | |
2643 | ||
2644 | myfunc(<< "THIS", 23, <<'THAT'); | |
2645 | Here's a line | |
2646 | or two. | |
2647 | THIS | |
2648 | and here's another. | |
2649 | THAT | |
2650 | ||
2651 | Just don't forget that you have to put a semicolon on the end | |
2652 | to finish the statement, as Perl doesn't know you're not going to | |
2653 | try to do this: | |
2654 | ||
2655 | print <<ABC | |
2656 | 179231 | |
2657 | ABC | |
2658 | + 20; | |
2659 | ||
872d7e53 TS |
2660 | If you want to remove the line terminator from your here-docs, |
2661 | use C<chomp()>. | |
2662 | ||
2663 | chomp($string = <<'END'); | |
2664 | This is a string. | |
2665 | END | |
2666 | ||
2667 | If you want your here-docs to be indented with the rest of the code, | |
2668 | you'll need to remove leading whitespace from each line manually: | |
7e3b091d DA |
2669 | |
2670 | ($quote = <<'FINIS') =~ s/^\s+//gm; | |
89d205f2 | 2671 | The Road goes ever on and on, |
7e3b091d DA |
2672 | down from the door where it began. |
2673 | FINIS | |
2674 | ||
2675 | If you use a here-doc within a delimited construct, such as in C<s///eg>, | |
1bf48760 FC |
2676 | the quoted material must still come on the line following the |
2677 | C<<< <<FOO >>> marker, which means it may be inside the delimited | |
2678 | construct: | |
7e3b091d DA |
2679 | |
2680 | s/this/<<E . 'that' | |
2681 | the other | |
2682 | E | |
2683 | . 'more '/eg; | |
2684 | ||
1bf48760 FC |
2685 | It works this way as of Perl 5.18. Historically, it was inconsistent, and |
2686 | you would have to write | |
7e3b091d | 2687 | |
89d205f2 YO |
2688 | s/this/<<E . 'that' |
2689 | . 'more '/eg; | |
2690 | the other | |
2691 | E | |
7e3b091d | 2692 | |
1bf48760 FC |
2693 | outside of string evals. |
2694 | ||
c543c01b | 2695 | Additionally, quoting rules for the end-of-string identifier are |
46f8a5ea | 2696 | unrelated to Perl's quoting rules. C<q()>, C<qq()>, and the like are not |
89d205f2 YO |
2697 | supported in place of C<''> and C<"">, and the only interpolation is for |
2698 | backslashing the quoting character: | |
7e3b091d DA |
2699 | |
2700 | print << "abc\"def"; | |
2701 | testing... | |
2702 | abc"def | |
2703 | ||
2704 | Finally, quoted strings cannot span multiple lines. The general rule is | |
2705 | that the identifier must be a string literal. Stick with that, and you | |
2706 | should be safe. | |
2707 | ||
a0d0e21e LW |
2708 | =back |
2709 | ||
75e14d17 | 2710 | =head2 Gory details of parsing quoted constructs |
d74e8afc | 2711 | X<quote, gory details> |
75e14d17 | 2712 | |
19799a22 GS |
2713 | When presented with something that might have several different |
2714 | interpretations, Perl uses the B<DWIM> (that's "Do What I Mean") | |
2715 | principle to pick the most probable interpretation. This strategy | |
2716 | is so successful that Perl programmers often do not suspect the | |
2717 | ambivalence of what they write. But from time to time, Perl's | |
2718 | notions differ substantially from what the author honestly meant. | |
2719 | ||
2720 | This section hopes to clarify how Perl handles quoted constructs. | |
2721 | Although the most common reason to learn this is to unravel labyrinthine | |
2722 | regular expressions, because the initial steps of parsing are the | |
2723 | same for all quoting operators, they are all discussed together. | |
2724 | ||
2725 | The most important Perl parsing rule is the first one discussed | |
2726 | below: when processing a quoted construct, Perl first finds the end | |
2727 | of that construct, then interprets its contents. If you understand | |
2728 | this rule, you may skip the rest of this section on the first | |
2729 | reading. The other rules are likely to contradict the user's | |
2730 | expectations much less frequently than this first one. | |
2731 | ||
2732 | Some passes discussed below are performed concurrently, but because | |
2733 | their results are the same, we consider them individually. For different | |
2734 | quoting constructs, Perl performs different numbers of passes, from | |
6deea57f | 2735 | one to four, but these passes are always performed in the same order. |
75e14d17 | 2736 | |
13a2d996 | 2737 | =over 4 |
75e14d17 IZ |
2738 | |
2739 | =item Finding the end | |
2740 | ||
ba7f043c KW |
2741 | The first pass is finding the end of the quoted construct. This results |
2742 | in saving to a safe location a copy of the text (between the starting | |
2743 | and ending delimiters), normalized as necessary to avoid needing to know | |
2744 | what the original delimiters were. | |
6deea57f TS |
2745 | |
2746 | If the construct is a here-doc, the ending delimiter is a line | |
46f8a5ea | 2747 | that has a terminating string as the content. Therefore C<<<EOF> is |
6deea57f TS |
2748 | terminated by C<EOF> immediately followed by C<"\n"> and starting |
2749 | from the first column of the terminating line. | |
2750 | When searching for the terminating line of a here-doc, nothing | |
46f8a5ea | 2751 | is skipped. In other words, lines after the here-doc syntax |
6deea57f TS |
2752 | are compared with the terminating string line by line. |
2753 | ||
2754 | For the constructs except here-docs, single characters are used as starting | |
46f8a5ea | 2755 | and ending delimiters. If the starting delimiter is an opening punctuation |
6deea57f TS |
2756 | (that is C<(>, C<[>, C<{>, or C<< < >>), the ending delimiter is the |
2757 | corresponding closing punctuation (that is C<)>, C<]>, C<}>, or C<< > >>). | |
2758 | If the starting delimiter is an unpaired character like C</> or a closing | |
ba7f043c | 2759 | punctuation, the ending delimiter is the same as the starting delimiter. |
6deea57f | 2760 | Therefore a C</> terminates a C<qq//> construct, while a C<]> terminates |
fc693347 | 2761 | both C<qq[]> and C<qq]]> constructs. |
6deea57f TS |
2762 | |
2763 | When searching for single-character delimiters, escaped delimiters | |
1ca345ed | 2764 | and C<\\> are skipped. For example, while searching for terminating C</>, |
6deea57f TS |
2765 | combinations of C<\\> and C<\/> are skipped. If the delimiters are |
2766 | bracketing, nested pairs are also skipped. For example, while searching | |
ba7f043c | 2767 | for a closing C<]> paired with the opening C<[>, combinations of C<\\>, C<\]>, |
6deea57f TS |
2768 | and C<\[> are all skipped, and nested C<[> and C<]> are skipped as well. |
2769 | However, when backslashes are used as the delimiters (like C<qq\\> and | |
2770 | C<tr\\\>), nothing is skipped. | |
32581033 | 2771 | During the search for the end, backslashes that escape delimiters or |
7188ca43 | 2772 | other backslashes are removed (exactly speaking, they are not copied to the |
32581033 | 2773 | safe location). |
75e14d17 | 2774 | |
19799a22 GS |
2775 | For constructs with three-part delimiters (C<s///>, C<y///>, and |
2776 | C<tr///>), the search is repeated once more. | |
fc693347 | 2777 | If the first delimiter is not an opening punctuation, the three delimiters must |
d74605e5 FC |
2778 | be the same, such as C<s!!!> and C<tr)))>, |
2779 | in which case the second delimiter | |
6deea57f | 2780 | terminates the left part and starts the right part at once. |
b6538e4f | 2781 | If the left part is delimited by bracketing punctuation (that is C<()>, |
6deea57f | 2782 | C<[]>, C<{}>, or C<< <> >>), the right part needs another pair of |
b6538e4f | 2783 | delimiters such as C<s(){}> and C<tr[]//>. In these cases, whitespace |
ba7f043c | 2784 | and comments are allowed between the two parts, although the comment must follow |
b6538e4f TC |
2785 | at least one whitespace character; otherwise a character expected as the |
2786 | start of the comment may be regarded as the starting delimiter of the right part. | |
75e14d17 | 2787 | |
19799a22 GS |
2788 | During this search no attention is paid to the semantics of the construct. |
2789 | Thus: | |
75e14d17 IZ |
2790 | |
2791 | "$hash{"$foo/$bar"}" | |
2792 | ||
2a94b7ce | 2793 | or: |
75e14d17 | 2794 | |
89d205f2 | 2795 | m/ |
2a94b7ce | 2796 | bar # NOT a comment, this slash / terminated m//! |
75e14d17 IZ |
2797 | /x |
2798 | ||
19799a22 GS |
2799 | do not form legal quoted expressions. The quoted part ends on the |
2800 | first C<"> and C</>, and the rest happens to be a syntax error. | |
2801 | Because the slash that terminated C<m//> was followed by a C<SPACE>, | |
2802 | the example above is not C<m//x>, but rather C<m//> with no C</x> | |
2803 | modifier. So the embedded C<#> is interpreted as a literal C<#>. | |
75e14d17 | 2804 | |
89d205f2 | 2805 | Also no attention is paid to C<\c\> (multichar control char syntax) during |
46f8a5ea | 2806 | this search. Thus the second C<\> in C<qq/\c\/> is interpreted as a part |
89d205f2 | 2807 | of C<\/>, and the following C</> is not recognized as a delimiter. |
0d594e51 TS |
2808 | Instead, use C<\034> or C<\x1c> at the end of quoted constructs. |
2809 | ||
75e14d17 | 2810 | =item Interpolation |
d74e8afc | 2811 | X<interpolation> |
75e14d17 | 2812 | |
19799a22 | 2813 | The next step is interpolation in the text obtained, which is now |
89d205f2 | 2814 | delimiter-independent. There are multiple cases. |
75e14d17 | 2815 | |
13a2d996 | 2816 | =over 4 |
75e14d17 | 2817 | |
89d205f2 | 2818 | =item C<<<'EOF'> |
75e14d17 IZ |
2819 | |
2820 | No interpolation is performed. | |
6deea57f TS |
2821 | Note that the combination C<\\> is left intact, since escaped delimiters |
2822 | are not available for here-docs. | |
75e14d17 | 2823 | |
6deea57f | 2824 | =item C<m''>, the pattern of C<s'''> |
89d205f2 | 2825 | |
6deea57f TS |
2826 | No interpolation is performed at this stage. |
2827 | Any backslashed sequences including C<\\> are treated at the stage | |
2828 | to L</"parsing regular expressions">. | |
89d205f2 | 2829 | |
6deea57f | 2830 | =item C<''>, C<q//>, C<tr'''>, C<y'''>, the replacement of C<s'''> |
75e14d17 | 2831 | |
89d205f2 | 2832 | The only interpolation is removal of C<\> from pairs of C<\\>. |
ba7f043c | 2833 | Therefore C<"-"> in C<tr'''> and C<y'''> is treated literally |
6deea57f TS |
2834 | as a hyphen and no character range is available. |
2835 | C<\1> in the replacement of C<s'''> does not work as C<$1>. | |
89d205f2 YO |
2836 | |
2837 | =item C<tr///>, C<y///> | |
2838 | ||
6deea57f TS |
2839 | No variable interpolation occurs. String modifying combinations for |
2840 | case and quoting such as C<\Q>, C<\U>, and C<\E> are not recognized. | |
2841 | The other escape sequences such as C<\200> and C<\t> and backslashed | |
2842 | characters such as C<\\> and C<\-> are converted to appropriate literals. | |
ba7f043c KW |
2843 | The character C<"-"> is treated specially and therefore C<\-> is treated |
2844 | as a literal C<"-">. | |
75e14d17 | 2845 | |
89d205f2 | 2846 | =item C<"">, C<``>, C<qq//>, C<qx//>, C<< <file*glob> >>, C<<<"EOF"> |
75e14d17 | 2847 | |
628253b8 | 2848 | C<\Q>, C<\U>, C<\u>, C<\L>, C<\l>, C<\F> (possibly paired with C<\E>) are |
19799a22 | 2849 | converted to corresponding Perl constructs. Thus, C<"$foo\Qbaz$bar"> |
ba7f043c | 2850 | is converted to S<C<$foo . (quotemeta("baz" . $bar))>> internally. |
6deea57f TS |
2851 | The other escape sequences such as C<\200> and C<\t> and backslashed |
2852 | characters such as C<\\> and C<\-> are replaced with appropriate | |
2853 | expansions. | |
2a94b7ce | 2854 | |
19799a22 GS |
2855 | Let it be stressed that I<whatever falls between C<\Q> and C<\E>> |
2856 | is interpolated in the usual way. Something like C<"\Q\\E"> has | |
48cbae4f | 2857 | no C<\E> inside. Instead, it has C<\Q>, C<\\>, and C<E>, so the |
19799a22 GS |
2858 | result is the same as for C<"\\\\E">. As a general rule, backslashes |
2859 | between C<\Q> and C<\E> may lead to counterintuitive results. So, | |
2860 | C<"\Q\t\E"> is converted to C<quotemeta("\t")>, which is the same | |
2861 | as C<"\\\t"> (since TAB is not alphanumeric). Note also that: | |
2a94b7ce IZ |
2862 | |
2863 | $str = '\t'; | |
2864 | return "\Q$str"; | |
2865 | ||
2866 | may be closer to the conjectural I<intention> of the writer of C<"\Q\t\E">. | |
2867 | ||
19799a22 | 2868 | Interpolated scalars and arrays are converted internally to the C<join> and |
ba7f043c | 2869 | C<"."> catenation operations. Thus, S<C<"$foo XXX '@arr'">> becomes: |
75e14d17 | 2870 | |
19799a22 | 2871 | $foo . " XXX '" . (join $", @arr) . "'"; |
75e14d17 | 2872 | |
19799a22 | 2873 | All operations above are performed simultaneously, left to right. |
75e14d17 | 2874 | |
ba7f043c | 2875 | Because the result of S<C<"\Q I<STRING> \E">> has all metacharacters |
19799a22 | 2876 | quoted, there is no way to insert a literal C<$> or C<@> inside a |
ba7f043c | 2877 | C<\Q\E> pair. If protected by C<\>, C<$> will be quoted to become |
19799a22 GS |
2878 | C<"\\\$">; if not, it is interpreted as the start of an interpolated |
2879 | scalar. | |
75e14d17 | 2880 | |
19799a22 | 2881 | Note also that the interpolation code needs to make a decision on |
89d205f2 | 2882 | where the interpolated scalar ends. For instance, whether |
ba7f043c | 2883 | S<C<< "a $x -> {c}" >>> really means: |
75e14d17 | 2884 | |
db691027 | 2885 | "a " . $x . " -> {c}"; |
75e14d17 | 2886 | |
2a94b7ce | 2887 | or: |
75e14d17 | 2888 | |
db691027 | 2889 | "a " . $x -> {c}; |
75e14d17 | 2890 | |
19799a22 GS |
2891 | Most of the time, the longest possible text that does not include |
2892 | spaces between components and which contains matching braces or | |
2893 | brackets. because the outcome may be determined by voting based | |
2894 | on heuristic estimators, the result is not strictly predictable. | |
2895 | Fortunately, it's usually correct for ambiguous cases. | |
75e14d17 | 2896 | |
6deea57f | 2897 | =item the replacement of C<s///> |
75e14d17 | 2898 | |
628253b8 | 2899 | Processing of C<\Q>, C<\U>, C<\u>, C<\L>, C<\l>, C<\F> and interpolation |
6deea57f TS |
2900 | happens as with C<qq//> constructs. |
2901 | ||
2902 | It is at this step that C<\1> is begrudgingly converted to C<$1> in | |
2903 | the replacement text of C<s///>, in order to correct the incorrigible | |
2904 | I<sed> hackers who haven't picked up the saner idiom yet. A warning | |
ba7f043c | 2905 | is emitted if the S<C<use warnings>> pragma or the B<-w> command-line flag |
6deea57f TS |
2906 | (that is, the C<$^W> variable) was set. |
2907 | ||
2908 | =item C<RE> in C<?RE?>, C</RE/>, C<m/RE/>, C<s/RE/foo/>, | |
2909 | ||
628253b8 | 2910 | Processing of C<\Q>, C<\U>, C<\u>, C<\L>, C<\l>, C<\F>, C<\E>, |
cc74c5bd TS |
2911 | and interpolation happens (almost) as with C<qq//> constructs. |
2912 | ||
5d03b57c KW |
2913 | Processing of C<\N{...}> is also done here, and compiled into an intermediate |
2914 | form for the regex compiler. (This is because, as mentioned below, the regex | |
2915 | compilation may be done at execution time, and C<\N{...}> is a compile-time | |
2916 | construct.) | |
2917 | ||
cc74c5bd TS |
2918 | However any other combinations of C<\> followed by a character |
2919 | are not substituted but only skipped, in order to parse them | |
2920 | as regular expressions at the following step. | |
6deea57f | 2921 | As C<\c> is skipped at this step, C<@> of C<\c@> in RE is possibly |
1749ea0d | 2922 | treated as an array symbol (for example C<@foo>), |
6deea57f | 2923 | even though the same text in C<qq//> gives interpolation of C<\c@>. |
6deea57f | 2924 | |
e128ab2c DM |
2925 | Code blocks such as C<(?{BLOCK})> are handled by temporarily passing control |
2926 | back to the perl parser, in a similar way that an interpolated array | |
2927 | subscript expression such as C<"foo$array[1+f("[xyz")]bar"> would be. | |
2928 | ||
ba7f043c KW |
2929 | Moreover, inside C<(?{BLOCK})>, S<C<(?# comment )>>, and |
2930 | a C<#>-comment in a C</x>-regular expression, no processing is | |
19799a22 | 2931 | performed whatsoever. This is the first step at which the presence |
ba7f043c | 2932 | of the C</x> modifier is relevant. |
19799a22 | 2933 | |
1749ea0d TS |
2934 | Interpolation in patterns has several quirks: C<$|>, C<$(>, C<$)>, C<@+> |
2935 | and C<@-> are not interpolated, and constructs C<$var[SOMETHING]> are | |
2936 | voted (by several different estimators) to be either an array element | |
2937 | or C<$var> followed by an RE alternative. This is where the notation | |
19799a22 GS |
2938 | C<${arr[$bar]}> comes handy: C</${arr[0-9]}/> is interpreted as |
2939 | array element C<-9>, not as a regular expression from the variable | |
2940 | C<$arr> followed by a digit, which would be the interpretation of | |
2941 | C</$arr[0-9]/>. Since voting among different estimators may occur, | |
2942 | the result is not predictable. | |
2943 | ||
19799a22 GS |
2944 | The lack of processing of C<\\> creates specific restrictions on |
2945 | the post-processed text. If the delimiter is C</>, one cannot get | |
2946 | the combination C<\/> into the result of this step. C</> will | |
2947 | finish the regular expression, C<\/> will be stripped to C</> on | |
2948 | the previous step, and C<\\/> will be left as is. Because C</> is | |
2949 | equivalent to C<\/> inside a regular expression, this does not | |
2950 | matter unless the delimiter happens to be character special to the | |
2951 | RE engine, such as in C<s*foo*bar*>, C<m[foo]>, or C<?foo?>; or an | |
2952 | alphanumeric char, as in: | |
2a94b7ce IZ |
2953 | |
2954 | m m ^ a \s* b mmx; | |
2955 | ||
19799a22 | 2956 | In the RE above, which is intentionally obfuscated for illustration, the |
6deea57f | 2957 | delimiter is C<m>, the modifier is C<mx>, and after delimiter-removal the |
ba7f043c | 2958 | RE is the same as for S<C<m/ ^ a \s* b /mx>>. There's more than one |
19799a22 GS |
2959 | reason you're encouraged to restrict your delimiters to non-alphanumeric, |
2960 | non-whitespace choices. | |
75e14d17 IZ |
2961 | |
2962 | =back | |
2963 | ||
19799a22 | 2964 | This step is the last one for all constructs except regular expressions, |
75e14d17 IZ |
2965 | which are processed further. |
2966 | ||
6deea57f TS |
2967 | =item parsing regular expressions |
2968 | X<regexp, parse> | |
75e14d17 | 2969 | |
19799a22 | 2970 | Previous steps were performed during the compilation of Perl code, |
ac036724 | 2971 | but this one happens at run time, although it may be optimized to |
19799a22 | 2972 | be calculated at compile time if appropriate. After preprocessing |
6deea57f | 2973 | described above, and possibly after evaluation if concatenation, |
19799a22 GS |
2974 | joining, casing translation, or metaquoting are involved, the |
2975 | resulting I<string> is passed to the RE engine for compilation. | |
2976 | ||
2977 | Whatever happens in the RE engine might be better discussed in L<perlre>, | |
2978 | but for the sake of continuity, we shall do so here. | |
2979 | ||
ba7f043c | 2980 | This is another step where the presence of the C</x> modifier is |
19799a22 | 2981 | relevant. The RE engine scans the string from left to right and |
ba7f043c | 2982 | converts it into a finite automaton. |
19799a22 GS |
2983 | |
2984 | Backslashed characters are either replaced with corresponding | |
2985 | literal strings (as with C<\{>), or else they generate special nodes | |
2986 | in the finite automaton (as with C<\b>). Characters special to the | |
2987 | RE engine (such as C<|>) generate corresponding nodes or groups of | |
2988 | nodes. C<(?#...)> comments are ignored. All the rest is either | |
2989 | converted to literal strings to match, or else is ignored (as is | |
ba7f043c | 2990 | whitespace and C<#>-style comments if C</x> is present). |
19799a22 GS |
2991 | |
2992 | Parsing of the bracketed character class construct, C<[...]>, is | |
2993 | rather different than the rule used for the rest of the pattern. | |
2994 | The terminator of this construct is found using the same rules as | |
2995 | for finding the terminator of a C<{}>-delimited construct, the only | |
2996 | exception being that C<]> immediately following C<[> is treated as | |
e128ab2c DM |
2997 | though preceded by a backslash. |
2998 | ||
2999 | The terminator of runtime C<(?{...})> is found by temporarily switching | |
3000 | control to the perl parser, which should stop at the point where the | |
3001 | logically balancing terminating C<}> is found. | |
19799a22 GS |
3002 | |
3003 | It is possible to inspect both the string given to RE engine and the | |
3004 | resulting finite automaton. See the arguments C<debug>/C<debugcolor> | |
ba7f043c | 3005 | in the S<C<use L<re>>> pragma, as well as Perl's B<-Dr> command-line |
4a4eefd0 | 3006 | switch documented in L<perlrun/"Command Switches">. |
75e14d17 IZ |
3007 | |
3008 | =item Optimization of regular expressions | |
d74e8afc | 3009 | X<regexp, optimization> |
75e14d17 | 3010 | |
7522fed5 | 3011 | This step is listed for completeness only. Since it does not change |
75e14d17 | 3012 | semantics, details of this step are not documented and are subject |
19799a22 GS |
3013 | to change without notice. This step is performed over the finite |
3014 | automaton that was generated during the previous pass. | |
2a94b7ce | 3015 | |
19799a22 GS |
3016 | It is at this stage that C<split()> silently optimizes C</^/> to |
3017 | mean C</^/m>. | |
75e14d17 IZ |
3018 | |
3019 | =back | |
3020 | ||
a0d0e21e | 3021 | =head2 I/O Operators |
d74e8afc | 3022 | X<operator, i/o> X<operator, io> X<io> X<while> X<filehandle> |
80a96bfc | 3023 | X<< <> >> X<< <<>> >> X<@ARGV> |
a0d0e21e | 3024 | |
54310121 | 3025 | There are several I/O operators you should know about. |
fbad3eb5 | 3026 | |
7b8d334a | 3027 | A string enclosed by backticks (grave accents) first undergoes |
19799a22 GS |
3028 | double-quote interpolation. It is then interpreted as an external |
3029 | command, and the output of that command is the value of the | |
e9c56f9b JH |
3030 | backtick string, like in a shell. In scalar context, a single string |
3031 | consisting of all output is returned. In list context, a list of | |
3032 | values is returned, one per line of output. (You can set C<$/> to use | |
3033 | a different line terminator.) The command is executed each time the | |
3034 | pseudo-literal is evaluated. The status value of the command is | |
3035 | returned in C<$?> (see L<perlvar> for the interpretation of C<$?>). | |
3036 | Unlike in B<csh>, no translation is done on the return data--newlines | |
3037 | remain newlines. Unlike in any of the shells, single quotes do not | |
3038 | hide variable names in the command from interpretation. To pass a | |
3039 | literal dollar-sign through to the shell you need to hide it with a | |
3040 | backslash. The generalized form of backticks is C<qx//>. (Because | |
3041 | backticks always undergo shell expansion as well, see L<perlsec> for | |
3042 | security concerns.) | |
d74e8afc | 3043 | X<qx> X<`> X<``> X<backtick> X<glob> |
19799a22 GS |
3044 | |
3045 | In scalar context, evaluating a filehandle in angle brackets yields | |
3046 | the next line from that file (the newline, if any, included), or | |
3047 | C<undef> at end-of-file or on error. When C<$/> is set to C<undef> | |
3048 | (sometimes known as file-slurp mode) and the file is empty, it | |
3049 | returns C<''> the first time, followed by C<undef> subsequently. | |
3050 | ||
3051 | Ordinarily you must assign the returned value to a variable, but | |
3052 | there is one situation where an automatic assignment happens. If | |
3053 | and only if the input symbol is the only thing inside the conditional | |
3054 | of a C<while> statement (even if disguised as a C<for(;;)> loop), | |
ba7f043c | 3055 | the value is automatically assigned to the global variable C<$_>, |
19799a22 GS |
3056 | destroying whatever was there previously. (This may seem like an |
3057 | odd thing to you, but you'll use the construct in almost every Perl | |
ba7f043c KW |
3058 | script you write.) The C<$_> variable is not implicitly localized. |
3059 | You'll have to put a S<C<local $_;>> before the loop if you want that | |
19799a22 GS |
3060 | to happen. |
3061 | ||
3062 | The following lines are equivalent: | |
a0d0e21e | 3063 | |
748a9306 | 3064 | while (defined($_ = <STDIN>)) { print; } |
7b8d334a | 3065 | while ($_ = <STDIN>) { print; } |
a0d0e21e LW |
3066 | while (<STDIN>) { print; } |
3067 | for (;<STDIN>;) { print; } | |
748a9306 | 3068 | print while defined($_ = <STDIN>); |
7b8d334a | 3069 | print while ($_ = <STDIN>); |
a0d0e21e LW |
3070 | print while <STDIN>; |
3071 | ||
1ca345ed TC |
3072 | This also behaves similarly, but assigns to a lexical variable |
3073 | instead of to C<$_>: | |
7b8d334a | 3074 | |
89d205f2 | 3075 | while (my $line = <STDIN>) { print $line } |
7b8d334a | 3076 | |
19799a22 GS |
3077 | In these loop constructs, the assigned value (whether assignment |
3078 | is automatic or explicit) is then tested to see whether it is | |
1ca345ed TC |
3079 | defined. The defined test avoids problems where the line has a string |
3080 | value that would be treated as false by Perl; for example a "" or | |
ba7f043c | 3081 | a C<"0"> with no trailing newline. If you really mean for such values |
19799a22 | 3082 | to terminate the loop, they should be tested for explicitly: |
7b8d334a GS |
3083 | |
3084 | while (($_ = <STDIN>) ne '0') { ... } | |
3085 | while (<STDIN>) { last unless $_; ... } | |
3086 | ||
ba7f043c | 3087 | In other boolean contexts, C<< <I<FILEHANDLE>> >> without an |
5ef4d93e | 3088 | explicit C<defined> test or comparison elicits a warning if the |
ba7f043c | 3089 | S<C<use warnings>> pragma or the B<-w> |
19799a22 | 3090 | command-line switch (the C<$^W> variable) is in effect. |
7b8d334a | 3091 | |
5f05dabc | 3092 | The filehandles STDIN, STDOUT, and STDERR are predefined. (The |
19799a22 GS |
3093 | filehandles C<stdin>, C<stdout>, and C<stderr> will also work except |
3094 | in packages, where they would be interpreted as local identifiers | |
3095 | rather than global.) Additional filehandles may be created with | |
ba7f043c | 3096 | the C<open()> function, amongst others. See L<perlopentut> and |
19799a22 | 3097 | L<perlfunc/open> for details on this. |
d74e8afc | 3098 | X<stdin> X<stdout> X<sterr> |
a0d0e21e | 3099 | |
ba7f043c | 3100 | If a C<< <I<FILEHANDLE>> >> is used in a context that is looking for |
19799a22 GS |
3101 | a list, a list comprising all input lines is returned, one line per |
3102 | list element. It's easy to grow to a rather large data space this | |
3103 | way, so use with care. | |
a0d0e21e | 3104 | |
ba7f043c | 3105 | C<< <I<FILEHANDLE>> >> may also be spelled C<readline(*I<FILEHANDLE>)>. |
19799a22 | 3106 | See L<perlfunc/readline>. |
fbad3eb5 | 3107 | |
ba7f043c | 3108 | The null filehandle C<< <> >> is special: it can be used to emulate the |
1ca345ed TC |
3109 | behavior of B<sed> and B<awk>, and any other Unix filter program |
3110 | that takes a list of filenames, doing the same to each line | |
ba7f043c | 3111 | of input from all of them. Input from C<< <> >> comes either from |
a0d0e21e | 3112 | standard input, or from each file listed on the command line. Here's |
ba7f043c KW |
3113 | how it works: the first time C<< <> >> is evaluated, the C<@ARGV> array is |
3114 | checked, and if it is empty, C<$ARGV[0]> is set to C<"-">, which when opened | |
3115 | gives you standard input. The C<@ARGV> array is then processed as a list | |
a0d0e21e LW |
3116 | of filenames. The loop |
3117 | ||
3118 | while (<>) { | |
3119 | ... # code for each line | |
3120 | } | |
3121 | ||
3122 | is equivalent to the following Perl-like pseudo code: | |
3123 | ||
3e3baf6d | 3124 | unshift(@ARGV, '-') unless @ARGV; |
a0d0e21e LW |
3125 | while ($ARGV = shift) { |
3126 | open(ARGV, $ARGV); | |
3127 | while (<ARGV>) { | |
3128 | ... # code for each line | |
3129 | } | |
3130 | } | |
3131 | ||
19799a22 | 3132 | except that it isn't so cumbersome to say, and will actually work. |
ba7f043c KW |
3133 | It really does shift the C<@ARGV> array and put the current filename |
3134 | into the C<$ARGV> variable. It also uses filehandle I<ARGV> | |
3135 | internally. C<< <> >> is just a synonym for C<< <ARGV> >>, which | |
19799a22 | 3136 | is magical. (The pseudo code above doesn't work because it treats |
ba7f043c | 3137 | C<< <ARGV> >> as non-magical.) |
a0d0e21e | 3138 | |
48ab5743 ML |
3139 | Since the null filehandle uses the two argument form of L<perlfunc/open> |
3140 | it interprets special characters, so if you have a script like this: | |
3141 | ||
3142 | while (<>) { | |
3143 | print; | |
3144 | } | |
3145 | ||
ba7f043c | 3146 | and call it with S<C<perl dangerous.pl 'rm -rfv *|'>>, it actually opens a |
48ab5743 ML |
3147 | pipe, executes the C<rm> command and reads C<rm>'s output from that pipe. |
3148 | If you want all items in C<@ARGV> to be interpreted as file names, you | |
1033ba6e PM |
3149 | can use the module C<ARGV::readonly> from CPAN, or use the double bracket: |
3150 | ||
3151 | while (<<>>) { | |
3152 | print; | |
3153 | } | |
3154 | ||
3155 | Using double angle brackets inside of a while causes the open to use the | |
3156 | three argument form (with the second argument being C<< < >>), so all | |
ba7f043c KW |
3157 | arguments in C<ARGV> are treated as literal filenames (including C<"-">). |
3158 | (Note that for convenience, if you use C<< <<>> >> and if C<@ARGV> is | |
80a96bfc | 3159 | empty, it will still read from the standard input.) |
48ab5743 | 3160 | |
ba7f043c | 3161 | You can modify C<@ARGV> before the first C<< <> >> as long as the array ends up |
a0d0e21e | 3162 | containing the list of filenames you really want. Line numbers (C<$.>) |
19799a22 GS |
3163 | continue as though the input were one big happy file. See the example |
3164 | in L<perlfunc/eof> for how to reset line numbers on each file. | |
5a964f20 | 3165 | |
ba7f043c KW |
3166 | If you want to set C<@ARGV> to your own list of files, go right ahead. |
3167 | This sets C<@ARGV> to all plain text files if no C<@ARGV> was given: | |
5a964f20 TC |
3168 | |
3169 | @ARGV = grep { -f && -T } glob('*') unless @ARGV; | |
a0d0e21e | 3170 | |
5a964f20 TC |
3171 | You can even set them to pipe commands. For example, this automatically |
3172 | filters compressed arguments through B<gzip>: | |
3173 | ||
3174 | @ARGV = map { /\.(gz|Z)$/ ? "gzip -dc < $_ |" : $_ } @ARGV; | |
3175 | ||
3176 | If you want to pass switches into your script, you can use one of the | |
ba7f043c | 3177 | C<Getopts> modules or put a loop on the front like this: |
a0d0e21e LW |
3178 | |
3179 | while ($_ = $ARGV[0], /^-/) { | |
3180 | shift; | |
3181 | last if /^--$/; | |
3182 | if (/^-D(.*)/) { $debug = $1 } | |
3183 | if (/^-v/) { $verbose++ } | |
5a964f20 | 3184 | # ... # other switches |
a0d0e21e | 3185 | } |
5a964f20 | 3186 | |
a0d0e21e | 3187 | while (<>) { |
5a964f20 | 3188 | # ... # code for each line |
a0d0e21e LW |
3189 | } |
3190 | ||
ba7f043c | 3191 | The C<< <> >> symbol will return C<undef> for end-of-file only once. |
89d205f2 | 3192 | If you call it again after this, it will assume you are processing another |
ba7f043c | 3193 | C<@ARGV> list, and if you haven't set C<@ARGV>, will read input from STDIN. |
a0d0e21e | 3194 | |
1ca345ed | 3195 | If what the angle brackets contain is a simple scalar variable (for example, |
ba7f043c | 3196 | C<$foo>), then that variable contains the name of the |
19799a22 GS |
3197 | filehandle to input from, or its typeglob, or a reference to the |
3198 | same. For example: | |
cb1a09d0 AD |
3199 | |
3200 | $fh = \*STDIN; | |
3201 | $line = <$fh>; | |
a0d0e21e | 3202 | |
5a964f20 TC |
3203 | If what's within the angle brackets is neither a filehandle nor a simple |
3204 | scalar variable containing a filehandle name, typeglob, or typeglob | |
3205 | reference, it is interpreted as a filename pattern to be globbed, and | |
3206 | either a list of filenames or the next filename in the list is returned, | |
19799a22 | 3207 | depending on context. This distinction is determined on syntactic |
ba7f043c KW |
3208 | grounds alone. That means C<< <$x> >> is always a C<readline()> from |
3209 | an indirect handle, but C<< <$hash{key}> >> is always a C<glob()>. | |
3210 | That's because C<$x> is a simple scalar variable, but C<$hash{key}> is | |
ef191992 YST |
3211 | not--it's a hash element. Even C<< <$x > >> (note the extra space) |
3212 | is treated as C<glob("$x ")>, not C<readline($x)>. | |
5a964f20 TC |
3213 | |
3214 | One level of double-quote interpretation is done first, but you can't | |
35f2feb0 | 3215 | say C<< <$foo> >> because that's an indirect filehandle as explained |
5a964f20 TC |
3216 | in the previous paragraph. (In older versions of Perl, programmers |
3217 | would insert curly brackets to force interpretation as a filename glob: | |
35f2feb0 | 3218 | C<< <${foo}> >>. These days, it's considered cleaner to call the |
5a964f20 | 3219 | internal function directly as C<glob($foo)>, which is probably the right |
19799a22 | 3220 | way to have done it in the first place.) For example: |
a0d0e21e LW |
3221 | |
3222 | while (<*.c>) { | |
3223 | chmod 0644, $_; | |
3224 | } | |
3225 | ||
3a4b19e4 | 3226 | is roughly equivalent to: |
a0d0e21e LW |
3227 | |
3228 | open(FOO, "echo *.c | tr -s ' \t\r\f' '\\012\\012\\012\\012'|"); | |
3229 | while (<FOO>) { | |
5b3eff12 | 3230 | chomp; |
a0d0e21e LW |
3231 | chmod 0644, $_; |
3232 | } | |
3233 | ||
3a4b19e4 | 3234 | except that the globbing is actually done internally using the standard |
ba7f043c | 3235 | C<L<File::Glob>> extension. Of course, the shortest way to do the above is: |
a0d0e21e LW |
3236 | |
3237 | chmod 0644, <*.c>; | |
3238 | ||
19799a22 GS |
3239 | A (file)glob evaluates its (embedded) argument only when it is |
3240 | starting a new list. All values must be read before it will start | |
3241 | over. In list context, this isn't important because you automatically | |
3242 | get them all anyway. However, in scalar context the operator returns | |
069e01df | 3243 | the next value each time it's called, or C<undef> when the list has |
19799a22 GS |
3244 | run out. As with filehandle reads, an automatic C<defined> is |
3245 | generated when the glob occurs in the test part of a C<while>, | |
1ca345ed TC |
3246 | because legal glob returns (for example, |
3247 | a file called F<0>) would otherwise | |
19799a22 GS |
3248 | terminate the loop. Again, C<undef> is returned only once. So if |
3249 | you're expecting a single value from a glob, it is much better to | |
3250 | say | |
4633a7c4 LW |
3251 | |
3252 | ($file) = <blurch*>; | |
3253 | ||
3254 | than | |
3255 | ||
3256 | $file = <blurch*>; | |
3257 | ||
3258 | because the latter will alternate between returning a filename and | |
19799a22 | 3259 | returning false. |
4633a7c4 | 3260 | |
b159ebd3 | 3261 | If you're trying to do variable interpolation, it's definitely better |
ba7f043c | 3262 | to use the C<glob()> function, because the older notation can cause people |
e37d713d | 3263 | to become confused with the indirect filehandle notation. |
4633a7c4 LW |
3264 | |
3265 | @files = glob("$dir/*.[ch]"); | |
3266 | @files = glob($files[$i]); | |
3267 | ||
a0d0e21e | 3268 | =head2 Constant Folding |
d74e8afc | 3269 | X<constant folding> X<folding> |
a0d0e21e LW |
3270 | |
3271 | Like C, Perl does a certain amount of expression evaluation at | |
19799a22 | 3272 | compile time whenever it determines that all arguments to an |
a0d0e21e LW |
3273 | operator are static and have no side effects. In particular, string |
3274 | concatenation happens at compile time between literals that don't do | |
19799a22 | 3275 | variable substitution. Backslash interpolation also happens at |
a0d0e21e LW |
3276 | compile time. You can say |
3277 | ||
1ca345ed TC |
3278 | 'Now is the time for all' |
3279 | . "\n" | |
3280 | . 'good men to come to.' | |
a0d0e21e | 3281 | |
54310121 | 3282 | and this all reduces to one string internally. Likewise, if |
a0d0e21e LW |
3283 | you say |
3284 | ||
3285 | foreach $file (@filenames) { | |
5a964f20 | 3286 | if (-s $file > 5 + 100 * 2**16) { } |
54310121 | 3287 | } |
a0d0e21e | 3288 | |
1ca345ed | 3289 | the compiler precomputes the number which that expression |
19799a22 | 3290 | represents so that the interpreter won't have to. |
a0d0e21e | 3291 | |
fd1abbef | 3292 | =head2 No-ops |
d74e8afc | 3293 | X<no-op> X<nop> |
fd1abbef DN |
3294 | |
3295 | Perl doesn't officially have a no-op operator, but the bare constants | |
1ca345ed | 3296 | C<0> and C<1> are special-cased not to produce a warning in void |
fd1abbef DN |
3297 | context, so you can for example safely do |
3298 | ||
3299 | 1 while foo(); | |
3300 | ||
2c268ad5 | 3301 | =head2 Bitwise String Operators |
fb7054ba | 3302 | X<operator, bitwise, string> X<&.> X<|.> X<^.> X<~.> |
2c268ad5 TP |
3303 | |
3304 | Bitstrings of any size may be manipulated by the bitwise operators | |
3305 | (C<~ | & ^>). | |
3306 | ||
19799a22 GS |
3307 | If the operands to a binary bitwise op are strings of different |
3308 | sizes, B<|> and B<^> ops act as though the shorter operand had | |
3309 | additional zero bits on the right, while the B<&> op acts as though | |
3310 | the longer operand were truncated to the length of the shorter. | |
3311 | The granularity for such extension or truncation is one or more | |
3312 | bytes. | |
2c268ad5 | 3313 | |
89d205f2 | 3314 | # ASCII-based examples |
2c268ad5 TP |
3315 | print "j p \n" ^ " a h"; # prints "JAPH\n" |
3316 | print "JA" | " ph\n"; # prints "japh\n" | |
3317 | print "japh\nJunk" & '_____'; # prints "JAPH\n"; | |
3318 | print 'p N$' ^ " E<H\n"; # prints "Perl\n"; | |
3319 | ||
19799a22 | 3320 | If you are intending to manipulate bitstrings, be certain that |
2c268ad5 | 3321 | you're supplying bitstrings: If an operand is a number, that will imply |
19799a22 | 3322 | a B<numeric> bitwise operation. You may explicitly show which type of |
2c268ad5 TP |
3323 | operation you intend by using C<""> or C<0+>, as in the examples below. |
3324 | ||
4358a253 SS |
3325 | $foo = 150 | 105; # yields 255 (0x96 | 0x69 is 0xFF) |
3326 | $foo = '150' | 105; # yields 255 | |
2c268ad5 TP |
3327 | $foo = 150 | '105'; # yields 255 |
3328 | $foo = '150' | '105'; # yields string '155' (under ASCII) | |
3329 | ||
3330 | $baz = 0+$foo & 0+$bar; # both ops explicitly numeric | |
3331 | $biz = "$foo" ^ "$bar"; # both ops explicitly stringy | |
a0d0e21e | 3332 | |
fb7054ba | 3333 | This somewhat unpredictable behavior can be avoided with the experimental |
ba7f043c KW |
3334 | "bitwise" feature, new in Perl 5.22. You can enable it via S<C<use feature |
3335 | 'bitwise'>>. By default, it will warn unless the C<"experimental::bitwise"> | |
3336 | warnings category has been disabled. (S<C<use experimental 'bitwise'>> will | |
fb7054ba FC |
3337 | enable the feature and disable the warning.) Under this feature, the four |
3338 | standard bitwise operators (C<~ | & ^>) are always numeric. Adding a dot | |
3339 | after each operator (C<~. |. &. ^.>) forces it to treat its operands as | |
3340 | strings: | |
3341 | ||
3342 | use experimental "bitwise"; | |
3343 | $foo = 150 | 105; # yields 255 (0x96 | 0x69 is 0xFF) | |
3344 | $foo = '150' | 105; # yields 255 | |
3345 | $foo = 150 | '105'; # yields 255 | |
3346 | $foo = '150' | '105'; # yields 255 | |
9f1b8172 | 3347 | $foo = 150 |. 105; # yields string '155' |
fb7054ba FC |
3348 | $foo = '150' |. 105; # yields string '155' |
3349 | $foo = 150 |.'105'; # yields string '155' | |
3350 | $foo = '150' |.'105'; # yields string '155' | |
3351 | ||
3352 | $baz = $foo & $bar; # both operands numeric | |
3353 | $biz = $foo ^. $bar; # both operands stringy | |
3354 | ||
3355 | The assignment variants of these operators (C<&= |= ^= &.= |.= ^.=>) | |
3356 | behave likewise under the feature. | |
3357 | ||
737f7534 KW |
3358 | The behavior of these operators is problematic (and subject to change) |
3359 | if either or both of the strings are encoded in UTF-8 (see | |
3360 | L<perlunicode/Byte and Character Semantics>. | |
3361 | ||
1ae175c8 GS |
3362 | See L<perlfunc/vec> for information on how to manipulate individual bits |
3363 | in a bit vector. | |
3364 | ||
55497cff | 3365 | =head2 Integer Arithmetic |
d74e8afc | 3366 | X<integer> |
a0d0e21e | 3367 | |
19799a22 | 3368 | By default, Perl assumes that it must do most of its arithmetic in |
a0d0e21e LW |
3369 | floating point. But by saying |
3370 | ||
3371 | use integer; | |
3372 | ||
3eab78e3 CW |
3373 | you may tell the compiler to use integer operations |
3374 | (see L<integer> for a detailed explanation) from here to the end of | |
3375 | the enclosing BLOCK. An inner BLOCK may countermand this by saying | |
a0d0e21e LW |
3376 | |
3377 | no integer; | |
3378 | ||
19799a22 | 3379 | which lasts until the end of that BLOCK. Note that this doesn't |
3eab78e3 CW |
3380 | mean everything is an integer, merely that Perl will use integer |
3381 | operations for arithmetic, comparison, and bitwise operators. For | |
ba7f043c | 3382 | example, even under S<C<use integer>>, if you take the C<sqrt(2)>, you'll |
3eab78e3 | 3383 | still get C<1.4142135623731> or so. |
19799a22 | 3384 | |
ba7f043c KW |
3385 | Used on numbers, the bitwise operators (C<&> C<|> C<^> C<~> C<< << >> |
3386 | C<< >> >>) always produce integral results. (But see also | |
5a0de581 | 3387 | L</Bitwise String Operators>.) However, S<C<use integer>> still has meaning for |
19799a22 | 3388 | them. By default, their results are interpreted as unsigned integers, but |
ba7f043c | 3389 | if S<C<use integer>> is in effect, their results are interpreted |
19799a22 | 3390 | as signed integers. For example, C<~0> usually evaluates to a large |
ba7f043c | 3391 | integral value. However, S<C<use integer; ~0>> is C<-1> on two's-complement |
19799a22 | 3392 | machines. |
68dc0745 | 3393 | |
3394 | =head2 Floating-point Arithmetic | |
06ce2fa3 | 3395 | |
d74e8afc | 3396 | X<floating-point> X<floating point> X<float> X<real> |
68dc0745 | 3397 | |
ba7f043c | 3398 | While S<C<use integer>> provides integer-only arithmetic, there is no |
19799a22 GS |
3399 | analogous mechanism to provide automatic rounding or truncation to a |
3400 | certain number of decimal places. For rounding to a certain number | |
ba7f043c | 3401 | of digits, C<sprintf()> or C<printf()> is usually the easiest route. |
19799a22 | 3402 | See L<perlfaq4>. |
68dc0745 | 3403 | |
5a964f20 TC |
3404 | Floating-point numbers are only approximations to what a mathematician |
3405 | would call real numbers. There are infinitely more reals than floats, | |
3406 | so some corners must be cut. For example: | |
3407 | ||
3408 | printf "%.20g\n", 123456789123456789; | |
3409 | # produces 123456789123456784 | |
3410 | ||
8548cb57 RGS |
3411 | Testing for exact floating-point equality or inequality is not a |
3412 | good idea. Here's a (relatively expensive) work-around to compare | |
5a964f20 TC |
3413 | whether two floating-point numbers are equal to a particular number of |
3414 | decimal places. See Knuth, volume II, for a more robust treatment of | |
3415 | this topic. | |
3416 | ||
3417 | sub fp_equal { | |
3418 | my ($X, $Y, $POINTS) = @_; | |
3419 | my ($tX, $tY); | |
3420 | $tX = sprintf("%.${POINTS}g", $X); | |
3421 | $tY = sprintf("%.${POINTS}g", $Y); | |
3422 | return $tX eq $tY; | |
3423 | } | |
3424 | ||
68dc0745 | 3425 | The POSIX module (part of the standard perl distribution) implements |
ba7f043c KW |
3426 | C<ceil()>, C<floor()>, and other mathematical and trigonometric functions. |
3427 | The C<L<Math::Complex>> module (part of the standard perl distribution) | |
19799a22 | 3428 | defines mathematical functions that work on both the reals and the |
ba7f043c | 3429 | imaginary numbers. C<Math::Complex> is not as efficient as POSIX, but |
68dc0745 | 3430 | POSIX can't work with complex numbers. |
3431 | ||
3432 | Rounding in financial applications can have serious implications, and | |
3433 | the rounding method used should be specified precisely. In these | |
3434 | cases, it probably pays not to trust whichever system rounding is | |
3435 | being used by Perl, but to instead implement the rounding function you | |
3436 | need yourself. | |
5a964f20 TC |
3437 | |
3438 | =head2 Bigger Numbers | |
d74e8afc | 3439 | X<number, arbitrary precision> |
5a964f20 | 3440 | |
ba7f043c KW |
3441 | The standard C<L<Math::BigInt>>, C<L<Math::BigRat>>, and |
3442 | C<L<Math::BigFloat>> modules, | |
fb1a95c6 | 3443 | along with the C<bignum>, C<bigint>, and C<bigrat> pragmas, provide |
19799a22 | 3444 | variable-precision arithmetic and overloaded operators, although |
46f8a5ea | 3445 | they're currently pretty slow. At the cost of some space and |
19799a22 GS |
3446 | considerable speed, they avoid the normal pitfalls associated with |
3447 | limited-precision representations. | |
5a964f20 | 3448 | |
c543c01b TC |
3449 | use 5.010; |
3450 | use bigint; # easy interface to Math::BigInt | |
3451 | $x = 123456789123456789; | |
3452 | say $x * $x; | |
3453 | +15241578780673678515622620750190521 | |
3454 | ||
3455 | Or with rationals: | |
3456 | ||
db691027 SF |
3457 | use 5.010; |
3458 | use bigrat; | |
3459 | $x = 3/22; | |
3460 | $y = 4/6; | |
3461 | say "x/y is ", $x/$y; | |
3462 | say "x*y is ", $x*$y; | |
3463 | x/y is 9/44 | |
3464 | x*y is 1/11 | |
c543c01b | 3465 | |
ba7f043c KW |
3466 | Several modules let you calculate with unlimited or fixed precision |
3467 | (bound only by memory and CPU time). There | |
46f8a5ea | 3468 | are also some non-standard modules that |
c543c01b | 3469 | provide faster implementations via external C libraries. |
cd5c4fce T |
3470 | |
3471 | Here is a short, but incomplete summary: | |
3472 | ||
950b09ed KW |
3473 | Math::String treat string sequences like numbers |
3474 | Math::FixedPrecision calculate with a fixed precision | |
3475 | Math::Currency for currency calculations | |
3476 | Bit::Vector manipulate bit vectors fast (uses C) | |
3477 | Math::BigIntFast Bit::Vector wrapper for big numbers | |
3478 | Math::Pari provides access to the Pari C library | |
70c45be3 FC |
3479 | Math::Cephes uses the external Cephes C library (no |
3480 | big numbers) | |
950b09ed KW |
3481 | Math::Cephes::Fraction fractions via the Cephes library |
3482 | Math::GMP another one using an external C library | |
70c45be3 FC |
3483 | Math::GMPz an alternative interface to libgmp's big ints |
3484 | Math::GMPq an interface to libgmp's fraction numbers | |
3485 | Math::GMPf an interface to libgmp's floating point numbers | |
cd5c4fce T |
3486 | |
3487 | Choose wisely. | |
16070b82 GS |
3488 | |
3489 | =cut |