summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorChip Salzenberg <chip@atlantic.net>1997-03-01 18:40:49 +1200
committerChip Salzenberg <chip@atlantic.net>1997-03-01 18:40:49 +1200
commit11155c9133a662d0930b7253d2ffdaeee3dcc771 (patch)
treeb23db12cb0bdfd1183f90e4d4a605f2d85dc512f /pod
parent1d5de609d1347ca1156d122626b38b1386a60617 (diff)
downloadperl-11155c9133a662d0930b7253d2ffdaeee3dcc771.tar.gz
Clarify C<crypt> documentation
(this is the same change as commit f827b0a6c8a4efd53c50a16b098f59ac04fd670d, but as applied)
Diffstat (limited to 'pod')
-rw-r--r--pod/perlfunc.pod8
1 files changed, 4 insertions, 4 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index cf5dd8fef2..09b5ad3df7 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -606,8 +606,10 @@ extirpated as a potential munition). This can prove useful for checking
the password file for lousy passwords, amongst other things. Only the
guys wearing white hats should do this.
-Note that there is no corresponding decrypt, so this fucntion isn't
-all that useful for cryptography. (For that, see your nearby CPAN mirror.)
+Note that crypt is intended to be a one-way function, much like breaking
+eggs to make an omelette. There is no (known) corresponding decrypt
+function. As a result, this function isn't all that useful for
+cryptography. (For that, see your nearby CPAN mirror.)
Here's an example that makes sure that whoever runs this program knows
their own password:
@@ -704,8 +706,6 @@ Examples:
print "$val\n" while defined($val = pop(@ary));
die "Can't readlink $sym: $!"
unless defined($value = readlink $sym);
- eval '@foo = ()' if defined(@foo);
- die "No XYZ package defined" unless defined %_XYZ;
sub foo { defined &$bar ? &$bar(@_) : die "No bar"; }
$debugging = 0 unless defined $debugging;