diff options
| author | Tom Christiansen <tchrist@perl.com> | 2011-05-18 22:06:54 -0700 |
|---|---|---|
| committer | Father Chrysostomos <sprout@cpan.org> | 2011-05-19 06:18:27 -0700 |
| commit | f113cf861b647108ad84981d83d24034fd20c6d4 (patch) | |
| tree | b587cd7ad2b2e85f590d66fa721bb687ece74d24 /pod/perlop.pod | |
| parent | 3c8f9076ada56b68da26e5d5d478aab6c20d5c38 (diff) | |
| download | perl-f113cf861b647108ad84981d83d24034fd20c6d4.tar.gz | |
[perl #90594] PATCH for 5.14.1 perlop.pod
Diffstat (limited to 'pod/perlop.pod')
| -rw-r--r-- | pod/perlop.pod | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/pod/perlop.pod b/pod/perlop.pod index 593a46a5fb..469d9aed04 100644 --- a/pod/perlop.pod +++ b/pod/perlop.pod @@ -212,9 +212,15 @@ example, C<0666 & ~027> is 0640. (See also L<Integer Arithmetic> and L<Bitwise String Operators>.) Note that the width of the result is platform-dependent: ~0 is 32 bits wide on a 32-bit platform, but 64 bits wide on a 64-bit platform, so if you are expecting a certain bit -width, remember to use the & operator to mask off the excess bits. +width, remember to use the "&" operator to mask off the excess bits. X<~> X<negation, binary> +When complementing strings, if all characters have ordinal values under +256, then their complements will, also. But if they do not, all +characters will be in either 32- or 64-bit complements, depending on your +architecture. So for example, C<~"\x{3B1}"> is C<"\x{FFFF_FC4E}"> on +32-bit machines and C<"\x{FFFF_FFFF_FFFF_FC4E}"> on 64-bit machines. + Unary "+" has no effect whatsoever, even on strings. It is useful syntactically for separating a function name from a parenthesized expression that would otherwise be interpreted as the complete list of function |