summaryrefslogtreecommitdiff
path: root/pod/perlnumber.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-03-19 07:41:46 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-03-19 07:41:46 +0000
commit85add8c20c52762eef70f97d016f6b677c9a4612 (patch)
tree8a66d94b92a464d43995e519c570444959d4680c /pod/perlnumber.pod
parent2a4bf7730d252fcadf5e50c3a9c740b5c94acfe3 (diff)
downloadperl-85add8c20c52762eef70f97d016f6b677c9a4612.tar.gz
pod typo fixes (from Marcel Grunauer <marcel.grunauer@lovely.net>)
p4raw-id: //depot/perl@5823
Diffstat (limited to 'pod/perlnumber.pod')
-rw-r--r--pod/perlnumber.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlnumber.pod b/pod/perlnumber.pod
index 9f628cc9a8..c83e053203 100644
--- a/pod/perlnumber.pod
+++ b/pod/perlnumber.pod
@@ -36,7 +36,7 @@ The term "native" does not mean quite as much when we talk about native
integers, as it does when native floating point numbers are involved.
The only implication of the term "native" on integers is that the limits for
the maximal and the minimal supported true integral quantities are close to
-powers of 2. However, for "native" floats have a most fundamental
+powers of 2. However, "native" floats have a most fundamental
restriction: they may represent only those numbers which have a relatively
"short" representation when converted to a binary fraction. For example,
0.9 cannot be respresented by a native float, since the binary fraction