did some massive changes to perlmod to include tim's new modules
file, but then trashed them. not sure what to do about this.
i don't know if there should be a 'man modstyle' or something
instead.
i'm also getting a bit tired of 'perlmod' being in section 1 rather
than in section 7 where it belongs. and that everything begins
with perlblah. but that's another battle.
--tom
diff -r pod/perl.pod npod/perl.pod
288c288,291
< See the perl bugs database at L<http://perl.com/perl/bugs/>.
---
> See the perl bugs database at F<http://perl.com/perl/bugs/>. You may
> mail your bug reports (be sure to include full configuration information
> as output by the myconfig program in the perl source tree) to
> F<perlbug@perl.com>.
diff -r pod/perlfunc.pod npod/perlfunc.pod
826c826,828
< fcntl(2). (fcntl(2) will be automatically used if flock(2) is missing.)
---
> fcntl(2). The fcntl(2) system call will be automatically used if flock(2)
> is missing from your system. This makes flock() the portable file locking
> strategy, although it will only lock entire files, not records.
2381a2384,2387
>
> For delays of finer granularity than one second, you may use Perl's
> syscall() interface to access setitimer(2) if your system supports it,
> or else see L</select()> below.
diff -r pod/perlvar.pod npod/perlvar.pod
65a66,96
> Here are the places where Perl will assume $_ even if you
> don't use it:
>
> =over
>
> =item *
> Various unary functions, including functions like ord() and int(), as well
> as the all file tests (C<-f>, C<-d>) except for C<-t>, which defaults to
> STDIN.
>
> =item *
> Various list functions like print() and unlink().
>
> =item *
> The pattern matching operations C<m//>, C<s///>, and C<tr///> when used
> without an C<=~> operator.
>
> =item *
> The default iterator variable in a C<foreach> loop if no other
> variable is supplied.
>
> =item *
> The implicit iterator variable in the grep() and map() functions.
>
> =item *
> The default place to put an input record when a C<E<lt>FHE<gt>>
> operation's result is tested by itself as the sole criterion of a C<while>
> test. Note that outside of a C<while> test, this will not happen.
>
> =back
>
449d479
<
file, but then trashed them. not sure what to do about this.
i don't know if there should be a 'man modstyle' or something
instead.
i'm also getting a bit tired of 'perlmod' being in section 1 rather
than in section 7 where it belongs. and that everything begins
with perlblah. but that's another battle.
--tom
diff -r pod/perl.pod npod/perl.pod
288c288,291
< See the perl bugs database at L<http://perl.com/perl/bugs/>.
---
> See the perl bugs database at F<http://perl.com/perl/bugs/>. You may
> mail your bug reports (be sure to include full configuration information
> as output by the myconfig program in the perl source tree) to
> F<perlbug@perl.com>.
diff -r pod/perlfunc.pod npod/perlfunc.pod
826c826,828
< fcntl(2). (fcntl(2) will be automatically used if flock(2) is missing.)
---
> fcntl(2). The fcntl(2) system call will be automatically used if flock(2)
> is missing from your system. This makes flock() the portable file locking
> strategy, although it will only lock entire files, not records.
2381a2384,2387
>
> For delays of finer granularity than one second, you may use Perl's
> syscall() interface to access setitimer(2) if your system supports it,
> or else see L</select()> below.
diff -r pod/perlvar.pod npod/perlvar.pod
65a66,96
> Here are the places where Perl will assume $_ even if you
> don't use it:
>
> =over
>
> =item *
> Various unary functions, including functions like ord() and int(), as well
> as the all file tests (C<-f>, C<-d>) except for C<-t>, which defaults to
> STDIN.
>
> =item *
> Various list functions like print() and unlink().
>
> =item *
> The pattern matching operations C<m//>, C<s///>, and C<tr///> when used
> without an C<=~> operator.
>
> =item *
> The default iterator variable in a C<foreach> loop if no other
> variable is supplied.
>
> =item *
> The implicit iterator variable in the grep() and map() functions.
>
> =item *
> The default place to put an input record when a C<E<lt>FHE<gt>>
> operation's result is tested by itself as the sole criterion of a C<while>
> test. Note that outside of a C<while> test, this will not happen.
>
> =back
>
449d479
<