diff options
author | Nicholas Clark <nick@ccl4.org> | 2000-08-30 02:12:50 +0100 |
---|---|---|
committer | Jarkko Hietaniemi <jhi@iki.fi> | 2000-08-30 14:46:34 +0000 |
commit | b1866b2db57c4aa1ee77325f2658722f6a7befa2 (patch) | |
tree | 5b73a85e97374f778ffcc77bff341c3ba1435d8a /pod/perlguts.pod | |
parent | 24e657a8ecba3e48980c1390adb658d9f9ad69f5 (diff) | |
download | perl-b1866b2db57c4aa1ee77325f2658722f6a7befa2.tar.gz |
typos in pods
Message-ID: <20000830011249.A61388@plum.flirble.org>
p4raw-id: //depot/perl@6917
Diffstat (limited to 'pod/perlguts.pod')
-rw-r--r-- | pod/perlguts.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlguts.pod b/pod/perlguts.pod index bfdf9facad..2f75cff528 100644 --- a/pod/perlguts.pod +++ b/pod/perlguts.pod @@ -2106,12 +2106,12 @@ However, you must not do this, for example: sv_utf8_upgrade(left); If you do this in a binary operator, you will actually change one of the -strings that came into the operator, and, while it shouldn't be noticable +strings that came into the operator, and, while it shouldn't be noticeable by the end user, it can cause problems. Instead, C<bytes_to_utf8> will give you a UTF8-encoded B<copy> of its string argument. This is useful for having the data available for -comparisons and so on, without harming the orginal SV. There's also +comparisons and so on, without harming the original SV. There's also C<utf8_to_bytes> to go the other way, but naturally, this will fail if the string contains any characters above 255 that can't be represented in a single byte. |