From: Tom Christiansen Date: Tue, 5 Jan 2010 03:32:51 +0000 (-0700) Subject: PATCH: minor typo cleanup of pod/ directory X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=e10204135b763e864169cd1f19037fc2f8c37385;p=p5sagit%2Fp5-mst-13.2.git PATCH: minor typo cleanup of pod/ directory These are all in the pod/ directory, and only the first is a code fix. There was also a single lingering ISO 8859-1 encoding that missed the UTF-8 upconvert. The rest are cleanups for typos, some of which seem to have been around for a rather long time: spelling errors, incorrect possessives, and extra, missing, or duplicated words. If you actually read through, I bet you'll realize what sparked this. :) --tom Signed-off-by: Abigail --- diff --git a/pod/buildtoc b/pod/buildtoc index 83eb447..4dd4271 100755 --- a/pod/buildtoc +++ b/pod/buildtoc @@ -763,7 +763,7 @@ while (my ($target, $name) = each %Targets) { rename $name, "$name.old" or die "$0: Can't rename $name to $name.old: $!"; open THING, ">$name" or die "$0: Can't open $name for writing: $!"; print THING $new or die "$0: print to $name failed: $!"; - close THING or die die "$0: close $name failed: $!"; + close THING or die "$0: close $name failed: $!"; } warn "$0: was not instructed to build anything\n" unless $built; diff --git a/pod/perl5100delta.pod b/pod/perl5100delta.pod index fe9f02e..263f158 100644 --- a/pod/perl5100delta.pod +++ b/pod/perl5100delta.pod @@ -440,7 +440,7 @@ with it. (Larry Wall, Nicholas Clark) =head2 kill() on Windows On Windows platforms, C now kills a process tree. -(On UNIX, this delivers the signal to all processes in the same process +(On Unix, this delivers the signal to all processes in the same process group.) =head1 Incompatible Changes @@ -1468,7 +1468,7 @@ to reflect this.) =head2 Elimination of SVt_PVBM -Related to this, the internal type C has been been removed. This +Related to this, the internal type C has been removed. This dedicated type of C was used by the C operator and parts of the regexp engine to facilitate fast Boyer-Moore matches. Its use internally has been replaced by Cs of type C. diff --git a/pod/perl5101delta.pod b/pod/perl5101delta.pod index f7b9ec1..c6cdef9 100644 --- a/pod/perl5101delta.pod +++ b/pod/perl5101delta.pod @@ -1149,7 +1149,7 @@ file. This eliminates a potential race condition [RT #60904]. =item * -On some UNIX systems, the value in C<$?> would not have the top bit set +On some Unix systems, the value in C<$?> would not have the top bit set (C<$? & 128>) even if the child core dumped. =item * diff --git a/pod/perl5110delta.pod b/pod/perl5110delta.pod index c49c559..1b722ed 100644 --- a/pod/perl5110delta.pod +++ b/pod/perl5110delta.pod @@ -858,7 +858,7 @@ file. This eliminates a potential race condition [RT #60904]. =item * -On some UNIX systems, the value in C<$?> would not have the top bit set +On some Unix systems, the value in C<$?> would not have the top bit set (C<$? & 128>) even if the child core dumped. =item * diff --git a/pod/perl5113delta.pod b/pod/perl5113delta.pod index 55fe29d..77918e2 100644 --- a/pod/perl5113delta.pod +++ b/pod/perl5113delta.pod @@ -425,7 +425,7 @@ Numerous bugfixes catch small issues caused by the recently-added Lexer API. =item * -Smart match against C<@_> sometimes gave false negatives negatives. [perl #71078] +Smart match against C<@_> sometimes gave false negatives. [perl #71078] =item * diff --git a/pod/perl570delta.pod b/pod/perl570delta.pod index 20abcd6..dcc2f0f 100644 --- a/pod/perl570delta.pod +++ b/pod/perl570delta.pod @@ -242,7 +242,7 @@ perl.org, not perl.com. =item * The perlcc utility has been rewritten and its user interface (that is, -command line) is much more like that of the UNIX C compiler, cc. +command line) is much more like that of the Unix C compiler, cc. =item * diff --git a/pod/perl571delta.pod b/pod/perl571delta.pod index 56eb74f..d25bee0 100644 --- a/pod/perl571delta.pod +++ b/pod/perl571delta.pod @@ -88,7 +88,7 @@ The built-in layers are: unix (low level read/write), stdio (as in previous Perls), perlio (re-implementation of stdio buffering in a portable manner), crlf (does CRLF <=> "\n" translation as on Win32, but available on any platform). A mmap layer may be available if -platform supports it (mostly UNIXes). +platform supports it (mostly Unixes). Layers to be applied by default may be specified via the 'open' pragma. @@ -130,7 +130,7 @@ That is a literal undef, not an undefined value. =item * -The list form of C is now implemented for pipes (at least on UNIX): +The list form of C is now implemented for pipes (at least on Unix): open($fh,"-|", 'cat', '/etc/motd') diff --git a/pod/perl572delta.pod b/pod/perl572delta.pod index fc5c392..21585ed 100644 --- a/pod/perl572delta.pod +++ b/pod/perl572delta.pod @@ -409,7 +409,7 @@ NetWare from Novell is now supported. See L. =item * -The Amdahl UTS UNIX mainframe platform is now supported. +The Amdahl UTS Unix mainframe platform is now supported. =back diff --git a/pod/perl573delta.pod b/pod/perl573delta.pod index 42ed261..00e73fe 100644 --- a/pod/perl573delta.pod +++ b/pod/perl573delta.pod @@ -20,7 +20,7 @@ The numbers refer to the Perl repository change numbers; see L (or L in Perl 5.8.1). In addition to these changes, lots of work took place in integrating threads, PerlIO, and Unicode; general code cleanup; and last but not least porting to -non-UNIX lands such as Win32, VMS, Cygwin, DJGPP, VOS, MacOS Classic, +non-Unix lands such as Win32, VMS, Cygwin, DJGPP, VOS, MacOS Classic, and EBCDIC. =over 4 diff --git a/pod/perl581delta.pod b/pod/perl581delta.pod index ecefbf7..cd88c73 100644 --- a/pod/perl581delta.pod +++ b/pod/perl581delta.pod @@ -506,9 +506,9 @@ perlreref has been added: it is a regular expressions quick reference. =head1 Installation and Configuration Improvements -The UNIX standard Perl location, F, is no longer +The Unix standard Perl location, F, is no longer overwritten by default if it exists. This change was very prudent -because so many UNIX vendors already provide a F, +because so many Unix vendors already provide a F, but simultaneously many system utilities may depend on that exact version of Perl, so better not to overwrite it. diff --git a/pod/perl588delta.pod b/pod/perl588delta.pod index 16082b5..a3d1df3 100644 --- a/pod/perl588delta.pod +++ b/pod/perl588delta.pod @@ -1472,7 +1472,7 @@ Trailing spaces are now trimmed from C<$!> and C<$^E>. =item * -Operations that require perl to read a process' list of groups, such as reads +Operations that require perl to read a process's list of groups, such as reads of C<$(> and C<$)>, now dynamically allocate memory rather than using a fixed sized array. The fixed size array could cause C stack exhaustion on systems configured to use large numbers of groups. diff --git a/pod/perl589delta.pod b/pod/perl589delta.pod index d4bafa1..2070cc3 100644 --- a/pod/perl589delta.pod +++ b/pod/perl589delta.pod @@ -1166,7 +1166,7 @@ between C<""> and C<< EE >> quoting in C<#include> statements. =item * -now generates correct correct code for C<#if defined A || defined B> +now generates correct code for C<#if defined A || defined B> [RT #39130] =back @@ -1834,7 +1834,7 @@ The reference count of C file descriptors is now correctly handled. =item * -On VMS, escaped dots will be preserved when converted to UNIX syntax. +On VMS, escaped dots will be preserved when converted to Unix syntax. =item * @@ -2096,7 +2096,7 @@ Calls all tests in F after first tying C<@INC>. =item t/op/incfilter.t -Tests for for source filters returned from code references in C<@INC>. +Tests for source filters returned from code references in C<@INC>. =item t/op/kill0.t diff --git a/pod/perl58delta.pod b/pod/perl58delta.pod index a3a0d8a..f3a8679 100644 --- a/pod/perl58delta.pod +++ b/pod/perl58delta.pod @@ -179,7 +179,7 @@ to be aliases for d/f, but you never knew that.) The list of filenames from glob() (or <...>) is now by default sorted alphabetically to be csh-compliant (which is what happened before -in most UNIX platforms). (bsd_glob() does still sort platform +in most Unix platforms). (bsd_glob() does still sort platform natively, ASCII or EBCDIC, unless GLOB_ALPHASORT is specified.) [561] =head2 Deprecations @@ -381,7 +381,7 @@ The built-in layers are: unix (low level read/write), stdio (as in previous Perls), perlio (re-implementation of stdio buffering in a portable manner), crlf (does CRLF <=> "\n" translation as on Win32, but available on any platform). A mmap layer may be available if -platform supports it (mostly UNIXes). +platform supports it (mostly Unixes). Layers to be applied by default may be specified via the 'open' pragma. @@ -1505,7 +1505,7 @@ perl.org, not perl.com. =item * C has been rewritten and its user interface (that is, -command line) is much more like that of the UNIX C compiler, cc. +command line) is much more like that of the Unix C compiler, cc. (The perlbc tools has been removed. Use C instead.) B [561] @@ -1531,7 +1531,7 @@ C now produces XHTML 1.0. =item * C now understands POD written using different line endings -(PC-like CRLF versus UNIX-like LF versus MacClassic-like CR). +(PC-like CRLF versus Unix-like LF versus MacClassic-like CR). =item * @@ -2083,7 +2083,7 @@ available. See L. [561+] =item * -The Amdahl UTS UNIX mainframe platform is now supported. [561] +The Amdahl UTS Unix mainframe platform is now supported. [561] =item * diff --git a/pod/perl590delta.pod b/pod/perl590delta.pod index db6f599..a19bf7a 100644 --- a/pod/perl590delta.pod +++ b/pod/perl590delta.pod @@ -487,9 +487,9 @@ perlreref has been added: it is a regular expressions quick reference. =head1 Installation and Configuration Improvements -The UNIX standard Perl location, F, is no longer +The Unix standard Perl location, F, is no longer overwritten by default if it exists. This change was very prudent -because so many UNIX vendors already provide a F, +because so many Unix vendors already provide a F, but simultaneously many system utilities may depend on that exact version of Perl, so better not to overwrite it. diff --git a/pod/perl593delta.pod b/pod/perl593delta.pod index d67a5a5..6c8587a 100644 --- a/pod/perl593delta.pod +++ b/pod/perl593delta.pod @@ -390,7 +390,7 @@ Trailing spaces are now trimmed from C<$!> and C<$^E>. =item * -Operations that require perl to read a process' list of groups, such as reads +Operations that require perl to read a process's list of groups, such as reads of C<$(> and C<$)>, now dynamically allocate memory rather than using a fixed sized array. The fixed size array could cause C stack exhaustion on systems configured to use large numbers of groups. diff --git a/pod/perlembed.pod b/pod/perlembed.pod index 36da54f..5ecaed0 100644 --- a/pod/perlembed.pod +++ b/pod/perlembed.pod @@ -1100,7 +1100,7 @@ Finally, select Build -> Build interp.exe and you're ready to go. =head1 Hiding Perl_ -If you completely hide the short forms forms of the Perl public API, +If you completely hide the short forms of the Perl public API, add -DPERL_NO_SHORT_NAMES to the compilation flags. This means that for example instead of writing diff --git a/pod/perlfaq.pod b/pod/perlfaq.pod index 96623ad..4f805ec 100644 --- a/pod/perlfaq.pod +++ b/pod/perlfaq.pod @@ -12,7 +12,7 @@ into nine major sections outlined in this document. The perlfaq comes with the standard Perl distribution, so if you have Perl you should have the perlfaq. You should also have the C tool -that let's you read the L: +that lets you read the L: $ perldoc perlfaq @@ -67,7 +67,7 @@ it, try the resources in L. Tom Christiansen wrote the original perlfaq then expanded it with the help of Nat Torkington. The perlfaq-workers maintain current document -and the dezinens of comp.lang.perl.misc regularly review and update the +and the denizens of comp.lang.perl.misc regularly review and update the FAQ. Several people have contributed answers, corrections, and comments, and the perlfaq notes those contributions wherever appropriate. @@ -76,7 +76,7 @@ and the perlfaq notes those contributions wherever appropriate. Copyright (c) 1997-2009 Tom Christiansen, Nathan Torkington, and other authors as noted. All rights reserved. -Tom Christainsen wrote the original version of this document. +Tom Christiansen wrote the original version of this document. brian d foy C<< >> wrote this version. See the individual perlfaq documents for additional copyright information. @@ -1440,4 +1440,3 @@ How can I do RPC in Perl? =back - diff --git a/pod/perlfaq2.pod b/pod/perlfaq2.pod index d558172..4aa420a 100644 --- a/pod/perlfaq2.pod +++ b/pod/perlfaq2.pod @@ -217,7 +217,7 @@ including setting the Followup-To header line to NOT include alt.sources; see their FAQ ( http://www.faqs.org/faqs/alt-sources-intro/ ) for details. If you're just looking for software, first use Google -( http://www.google.com ), Google's usenet search interface +( http://www.google.com ), Google's USENET search interface ( http://groups.google.com ), and CPAN Search ( http://search.cpan.org ). This is faster and more productive than just posting a request. diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod index 6b2a046..7be2379 100644 --- a/pod/perlfaq3.pod +++ b/pod/perlfaq3.pod @@ -275,7 +275,7 @@ You might also try pltags: http://www.mscha.com/pltags.zip Perl programs are just plain text, so any editor will do. -If you're on Unix, you already have an IDE--Unix itself. The UNIX +If you're on Unix, you already have an IDE--Unix itself. The Unix philosophy is the philosophy of several small tools that each do one thing and do it well. It's like a carpenter's toolbox. @@ -425,7 +425,7 @@ For vi lovers in general, Windows or elsewhere: nvi ( http://www.bostic.com/vi/ , available from CPAN in src/misc/) is yet another vi clone, unfortunately not available for Windows, but in -UNIX platforms you might be interested in trying it out, firstly because +Unix platforms you might be interested in trying it out, firstly because strictly speaking it is not a vi clone, it is the real vi, or the new incarnation of it, and secondly because you can embed Perl inside it to use Perl as the scripting language. nvi is not alone in this, @@ -489,7 +489,7 @@ MKS and U/WIN are commercial (U/WIN is free for educational and research purposes), Cygwin is covered by the GNU General Public License (but that shouldn't matter for Perl use). The Cygwin, MKS, and U/WIN all contain (in addition to the shells) a comprehensive set -of standard UNIX toolkit utilities. +of standard Unix toolkit utilities. If you're transferring text files between Unix and Windows using FTP be sure to transfer them in ASCII mode so the ends of lines are @@ -912,7 +912,7 @@ executables for HP-UX, Linux, Solaris and Windows." Perl2Exe ( http://www.indigostar.com/perl2exe.htm ) is a command line program for converting perl scripts to executable files. It targets both -Windows and unix platforms. +Windows and Unix platforms. =head2 How can I get C<#!perl> to work on [MS-DOS,NT,...]? @@ -1080,7 +1080,7 @@ or The C module, better known simply as "MakeMaker", turns a Perl script, typically called C, into a Makefile. -The unix tool C uses this file to manage dependencies and actions +The Unix tool C uses this file to manage dependencies and actions to process and install a Perl distribution. =head1 REVISION diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod index 8d5e2e6..5549634 100644 --- a/pod/perlfaq4.pod +++ b/pod/perlfaq4.pod @@ -62,7 +62,7 @@ are in base 10: print $string + 44; # prints 688, certainly not octal! This problem usually involves one of the Perl built-ins that has the -same name a unix command that uses octal numbers as arguments on the +same name a Unix command that uses octal numbers as arguments on the command line. In this example, C on the command line knows that its first argument is octal because that's what it does: @@ -537,7 +537,7 @@ doesn't matter and you end up with the previous date. (contributed by brian d foy) -Perl itself never had a Y2K problem, although that nevers stopped people +Perl itself never had a Y2K problem, although that never stopped people from creating Y2K problems on their own. See the documentation for C for its proper use. diff --git a/pod/perlfaq7.pod b/pod/perlfaq7.pod index bc2f4f6..a74ff1f 100644 --- a/pod/perlfaq7.pod +++ b/pod/perlfaq7.pod @@ -656,7 +656,7 @@ see L. Calling a subroutine as C<&foo> with no trailing parentheses ignores the prototype of C and passes it the current value of the argument list, C<@_>. Here's an example; the C subroutine calls C<&foo>, -which prints what its arguments list: +which prints its argument list: sub bar { &foo } diff --git a/pod/perlfaq8.pod b/pod/perlfaq8.pod index adda585..0fd322e 100644 --- a/pod/perlfaq8.pod +++ b/pod/perlfaq8.pod @@ -103,7 +103,7 @@ It even includes limited support for Windows. However, using the code requires that you have a working C compiler and can use it to build and install a CPAN module. Here's a solution -using the standard C module, which is already on your systems +using the standard C module, which is already on your system (assuming your system supports POSIX). use HotKey; @@ -389,7 +389,7 @@ C, C, C, C, C, C, and C. There are many other modules you might use, so check those namespaces for other options too. -If you are on a unix-like system, you might be able to get away with a +If you are on a Unix-like system, you might be able to get away with a system call where you put an C<&> on the end of the command: system("cmd &") @@ -494,7 +494,7 @@ the VMS equivalent is C. However, if all you want to do is change your time zone, you can probably get away with setting an environment variable: - $ENV{TZ} = "MST7MDT"; # unixish + $ENV{TZ} = "MST7MDT"; # Unixish $ENV{'SYS$TIMEZONE_DIFFERENTIAL'}="-5" # vms system "trn comp.lang.perl.misc"; @@ -864,7 +864,7 @@ stuck, because Windows does not have an argc/argv-style API. =head2 Why can't my script read from STDIN after I gave it EOF (^D on Unix, ^Z on MS-DOS)? This happens only if your perl is compiled to use stdio instead of -perlio, which is the default. Some (maybe all?) stdio's set error and +perlio, which is the default. Some (maybe all?) stdios set error and eof flags that you may need to clear. The C module defines C that you can use. That is the technically correct way to do it. Here are some less reliable workarounds: diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 114d4da..a40fbc3 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -1022,7 +1022,7 @@ Traditionally the result is a string of 13 bytes: two first bytes of the salt, followed by 11 bytes from the set C<[./0-9A-Za-z]>, and only the first eight bytes of PLAINTEXT mattered. But alternative hashing schemes (like MD5), higher level security schemes (like C2), -and implementations on non-UNIX platforms may produce different +and implementations on non-Unix platforms may produce different strings. When choosing a new salt create a random two character string whose @@ -3194,7 +3194,7 @@ C<< '+<' >> is almost always preferred for read/write updates--the C<< either read-write mode for updating textfiles, since they have variable length records. See the B<-i> switch in L for a better approach. The file is created with permissions of C<0666> -modified by the process' C value. +modified by the process's C value. These various prefixes correspond to the fopen(3) modes of C<'r'>, C<'r+'>, C<'w'>, C<'w+'>, C<'a'>, and C<'a+'>. @@ -3405,7 +3405,7 @@ the same file descriptor. Note that if you are using Perls older than 5.8.0, Perl will be using the standard C libraries' fdopen() to implement the "=" functionality. -On many UNIX systems fdopen() fails when file descriptors exceed a +On many Unix systems fdopen() fails when file descriptors exceed a certain value, typically 255. For Perls 5.8.0 and later, PerlIO is most often the default. @@ -3440,7 +3440,7 @@ The following triples are more or less equivalent: The last example in each block shows the pipe as "list form", which is not yet supported on all platforms. A good rule of thumb is that if your platform has true C (in other words, if your platform is -UNIX) you can use the list form. +Unix) you can use the list form. See L for more examples of this. @@ -4165,7 +4165,7 @@ C<$::sail> is equivalent to C<$main::sail> (as well as to C<$main'sail>, still seen in older code). If VERSION is provided, C also sets the C<$VERSION> variable in the -given namespace. VERSION must be be a numeric literal or v-string; it is +given namespace. VERSION must be a numeric literal or v-string; it is parsed exactly the same way as a VERSION argument to C. C<$VERSION> should only be set once per package. @@ -4280,7 +4280,7 @@ function has no prototype). FUNCTION is a reference to, or the name of, the function whose prototype you want to retrieve. If FUNCTION is a string starting with C, the rest is taken as a -name for Perl builtin. If the builtin is not I (such as +name for a Perl builtin. If the builtin is not I (such as C) or if its arguments cannot be adequately expressed by a prototype (such as C), prototype() returns C, because the builtin does not really behave like a Perl function. Otherwise, the string @@ -4902,7 +4902,7 @@ Deletes the directory specified by FILENAME if that directory is empty. If it succeeds it returns true, otherwise it returns false and sets C<$!> (errno). If FILENAME is omitted, uses C<$_>. -To remove a directory tree recursively (C on unix) look at +To remove a directory tree recursively (C on Unix) look at the C function of the L module. =item s/// @@ -6488,7 +6488,7 @@ Better to omit it. See the perlfunc(1) entry on C for more on this. Note that C depends on the fdopen() C library function. -On many UNIX systems, fdopen() is known to fail when file descriptors +On many Unix systems, fdopen() is known to fail when file descriptors exceed a certain value, typically 255. If you need more file descriptors than that, consider rebuilding Perl to use the C library, or perhaps using the POSIX::open() function. diff --git a/pod/perlhack.pod b/pod/perlhack.pod index a964fa8..fb9bdb8 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -397,7 +397,7 @@ Configure, build and installation process, as well as the overall portability of the core code rests with the Configure pumpkin - others help out with individual operating systems. -The three files that fall under his/her resposibility are Configure, +The three files that fall under his/her responsibility are Configure, config_h.SH, and Porting/Glossary (and a whole bunch of small related files that are less important here). The Configure pumpkin decides how patches to these are dealt with. Currently, the Configure pumpkin will @@ -2598,7 +2598,7 @@ not perfect, because the below is a compile-time check): #endif How does the HAS_QUUX become defined where it needs to be? Well, if -Foonix happens to be UNIXy enough to be able to run the Configure +Foonix happens to be Unixy enough to be able to run the Configure script, and Configure has been taught about detecting and testing quux(), the HAS_QUUX will be correctly defined. In other platforms, the corresponding configuration step will hopefully do the same. @@ -2699,7 +2699,7 @@ and for Bourne-type shells: PERL_DESTRUCT_LEVEL=2 export PERL_DESTRUCT_LEVEL -or in UNIXy environments you can also use the C command: +or in Unixy environments you can also use the C command: env PERL_DESTRUCT_LEVEL=2 valgrind ./perl -Ilib ... @@ -3010,7 +3010,7 @@ results. =head2 Gprof Profiling -gprof is a profiling tool available in many UNIX platforms, +gprof is a profiling tool available in many Unix platforms, it uses F. You can build a profiled version of perl called "perl.gprof" by diff --git a/pod/perliol.pod b/pod/perliol.pod index a560d97..e814847 100644 --- a/pod/perliol.pod +++ b/pod/perliol.pod @@ -70,10 +70,10 @@ handling binary data. The "pushed" layers are processed in left-to-right order. sysopen() operates (unsurprisingly) at a lower level in the stack than -open(). For example in UNIX or UNIX-like systems sysopen() operates +open(). For example in Unix or Unix-like systems sysopen() operates directly at the level of file descriptors: in the terms of PerlIO layers, it uses only the "unix" layer, which is a rather thin wrapper -on top of the UNIX file descriptors. +on top of the Unix file descriptors. =head2 Layers vs Disciplines @@ -837,7 +837,7 @@ The following table summarizes the behaviour: Unread PerlIOBase_unread Write FAILURE - FAILURE Set errno (to EINVAL in UNIXish, to LIB$_INVARG in VMS) and + FAILURE Set errno (to EINVAL in Unixish, to LIB$_INVARG in VMS) and return -1 (for numeric return values) or NULL (for pointers) INHERITED Inherited from the layer below SUCCESS Return 0 (for numeric return values) or a pointer diff --git a/pod/perlipc.pod b/pod/perlipc.pod index 6424615..962d106 100644 --- a/pod/perlipc.pod +++ b/pod/perlipc.pod @@ -718,7 +718,7 @@ the pipe and expecting an EOF will never receive it, and therefore never exit. A single process closing a pipe is not enough to close it; the last process with the pipe open must close it for it to read EOF. -There are some features built-in to unix to help prevent this most of +Certain built-in Unix features help prevent this most of the time. For instance, filehandles have a 'close on exec' flag (set I with Perl using the C<$^F> L), so that any filehandles which you didn't explicitly route to the STDIN, STDOUT or diff --git a/pod/perllocale.pod b/pod/perllocale.pod index 918abfc..0dbabe7 100644 --- a/pod/perllocale.pod +++ b/pod/perllocale.pod @@ -434,7 +434,7 @@ parameters as integers correctly formatted in the current locale: =head2 I18N::Langinfo Another interface for querying locale-dependent information is the -I18N::Langinfo::langinfo() function, available at least in UNIX-like +I18N::Langinfo::langinfo() function, available at least in Unix-like systems and VMS. The following example will import the langinfo() function itself and @@ -861,7 +861,7 @@ set, it overrides all the rest of the locale environment variables. B: C is a GNU extension, it affects you only if you are using the GNU libc. This is the case if you are using e.g. Linux. -If you are using "commercial" UNIXes you are most probably I +If you are using "commercial" Unixes you are most probably I using GNU libc and you can ignore C. However, in the case you are using C: it affects the diff --git a/pod/perlnewmod.pod b/pod/perlnewmod.pod index d8bd400..7555f97 100644 --- a/pod/perlnewmod.pod +++ b/pod/perlnewmod.pod @@ -276,5 +276,5 @@ Updated by Kirrily "Skud" Robert, C L, L, L, L, L, L, L, L, L, L L, L, L -http://www.cpan.org/ , Ken Williams' tutorial on building your own +http://www.cpan.org/ , Ken Williams's tutorial on building your own module at http://mathforum.org/~ken/perl_modules.html diff --git a/pod/perlopentut.pod b/pod/perlopentut.pod index 9139ebc..ea4b307 100644 --- a/pod/perlopentut.pod +++ b/pod/perlopentut.pod @@ -449,7 +449,7 @@ be 0777, and for anything else, 0666. Why so permissive? Well, it isn't really. The MASK will be modified by your process's current C. A umask is a number representing I permissions bits; that is, bits that will not be turned on -in the created files' permissions field. +in the created file's permissions field. For example, if your C were 027, then the 020 part would disable the group from writing, and the 007 part would disable others diff --git a/pod/perlperf.pod b/pod/perlperf.pod index 9384d53..a934271 100644 --- a/pod/perlperf.pod +++ b/pod/perlperf.pod @@ -31,7 +31,7 @@ optimization process. Firstly, you need to establish a baseline time for the existing code, which timing needs to be reliable and repeatable. You'll probably want to use the C or C modules, or something similar, for this step, -or perhaps the unix system C