projects
/
platform
/
upstream
/
perl.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
9e7f2f8
)
perlfunc.pod: s/definetely/definitely/
author
Piotr Fusik
<pfusik@op.pl>
Sun, 24 Jul 2005 12:55:09 +0000
(14:55 +0200)
committer
H.Merijn Brand
<h.m.brand@xs4all.nl>
Mon, 25 Jul 2005 08:39:08 +0000
(08:39 +0000)
From: "Piotr Fusik" <pfusik@op.pl>
Message-ID: <
004e01c5903e
$
2affb3a0
$
60d24dd5
@piec>
p4raw-id: //depot/perl@25219
pod/perlfunc.pod
patch
|
blob
|
history
diff --git
a/pod/perlfunc.pod
b/pod/perlfunc.pod
index
394153c
..
43dc07b
100644
(file)
--- a/
pod/perlfunc.pod
+++ b/
pod/perlfunc.pod
@@
-3707,7
+3707,7
@@
binary representation (e.g. IEEE floating point format). Even if all
platforms are using IEEE, there may be subtle differences. Being able
to use C<E<gt>> or C<E<lt>> on floating point values can be very useful,
but also very dangerous if you don't know exactly what you're doing.
-It is defin
e
tely not a general way to portably store floating point
+It is defin
i
tely not a general way to portably store floating point
values.
When using C<E<gt>> or C<E<lt>> on an C<()>-group, this will affect