summaryrefslogtreecommitdiff
path: root/pod/perlnumber.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-03-13 21:40:23 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-03-13 21:40:23 +0000
commit4a4eefd0ee0da7b6a2b5b0d021684bca80971b79 (patch)
tree4ba0b9699091601412de42d8581eda4cfc7d6b89 /pod/perlnumber.pod
parentdbe483029183d54ab170feb5939c3b2b8b193b3c (diff)
downloadperl-4a4eefd0ee0da7b6a2b5b0d021684bca80971b79.tar.gz
fixes for broken L<> links (from Wolfgang Laun
<wolfgang.laun@alcatel.at>) p4raw-id: //depot/perl@5715
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 c05b066b43..16d642119a 100644
--- a/pod/perlnumber.pod
+++ b/pod/perlnumber.pod
@@ -61,7 +61,7 @@ numbers. (But realize that what we are discussing the rules for just the
I<storage> of these numbers. The fact that you can store such "large" numbers
does not mean that that the I<operations> over these numbers will use all
of the significant digits.
-See L<"Numeric operations and numeric conversions"> for details.)
+See L<"Numeric operators and numeric conversions"> for details.)
In fact numbers stored in the native integer format may be stored either
in the signed native form, or in the unsigned native form. Thus the limits