diff options
| author | Karl Williamson <public@khwilliamson.com> | 2012-06-06 11:11:34 -0600 |
|---|---|---|
| committer | Karl Williamson <public@khwilliamson.com> | 2012-06-07 09:55:49 -0600 |
| commit | 3c8317961e30b9ee408493f68b38d723f6748319 (patch) | |
| tree | 1599e13ea50a2fbc804f67aac1f18307ef105d17 /pod/perlfunc.pod | |
| parent | ba207afd4f7e36d6017bca62c51c750ddc6beb7a (diff) | |
| download | perl-3c8317961e30b9ee408493f68b38d723f6748319.tar.gz | |
perlfunc: Add comma
Diffstat (limited to 'pod/perlfunc.pod')
| -rw-r--r-- | pod/perlfunc.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 3482f362eb..99cdeec28e 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -7252,7 +7252,7 @@ Perl versions, it should call C<srand>; otherwise most programs won't call C<srand()> at all. But there are a few situations in recent Perls where programs are likely to -want to call C<srand>. One is for generating predictable results generally for +want to call C<srand>. One is for generating predictable results, generally for testing or debugging. There, you use C<srand($seed)>, with the same C<$seed> each time. Another case is that you may want to call C<srand()> after a C<fork()> to avoid child processes sharing the same seed value as the |