s/MacOS/Mac OS/g; # (when the name of the os, not when $^O) Pudge

p4raw-id: //depot/perl@17055

diff --git a/pod/perl561delta.pod b/pod/perl561delta.pod
index ddc2509..fa36ebc 100644 (file)
--- a/pod/perl561delta.pod
+++ b/pod/perl561delta.pod
@@ -343,9 +343,10 @@ C<Configure -S> can be run non-interactively.
 
 =head2 Documentation
 
-README.aix, README.solaris and README.macos have been added.  README.posix-bc
-has been renamed to README.bs2000.  These are installed as L<perlaix>,
-L<perlsolaris>, L<perlmacos>, and L<perlbs2000> respectively.
+README.aix, README.solaris and README.macos have been added.
+README.posix-bc has been renamed to README.bs2000.  These are
+installed as L<perlaix>, L<perlsolaris>, L<perlmacos>, and
+L<perlbs2000> respectively.
 
 The following pod documents are brand new:
 
@@ -502,7 +503,7 @@ You will need a thread library package installed.  See README.hpux.
 
 Long doubles should now work under Linux.
 
-MacOS Classic is now supported in the mainstream source package.
+Mac OS Classic is now supported in the mainstream source package.
 See README.macos.
 
 Support for MPE/iX has been updated.  See README.mpeix.

diff --git a/pod/perl570delta.pod b/pod/perl570delta.pod
index 0d28754..3d4e5e2 100644 (file)
--- a/pod/perl570delta.pod
+++ b/pod/perl570delta.pod
@@ -589,12 +589,12 @@ Long doubles should now work (see INSTALL).
 
 =item *
 
-MacOS Classic
+Mac OS Classic
 
-Compilation of the standard Perl distribution in MacOS Classic should
-now work if you have the Metrowerks development environment and
-the missing Mac-specific toolkit bits.  Contact the macperl mailing
-list for details.
+Compilation of the standard Perl distribution in Mac OS Classic should
+now work if you have the Metrowerks development environment and the
+missing Mac-specific toolkit bits.  Contact the macperl mailing list
+for details.
 
 =item *
 

diff --git a/pod/perl571delta.pod b/pod/perl571delta.pod
index cfaa614..431c359 100644 (file)
--- a/pod/perl571delta.pod
+++ b/pod/perl571delta.pod
@@ -669,7 +669,7 @@ need a thread library package installed. See README.hpux.
 
 =item *
 
-MacOS Classic (MacPerl has of course been available since
+Mac OS Classic (MacPerl has of course been available since
 perl 5.004 but now the source code bases of standard Perl
 and MacPerl have been synchronised)
 

diff --git a/pod/perl572delta.pod b/pod/perl572delta.pod
index 584fb1e..e7d4ce3 100644 (file)
--- a/pod/perl572delta.pod
+++ b/pod/perl572delta.pod
@@ -394,13 +394,13 @@ DYNIX/ptx platform (a.k.a. dynixptx) is supported at or near osvers 4.5.2.
 
 =item *
 
-Several MacOS (Classic) portability patches have been applied.  We
+Several Mac OS (Classic) portability patches have been applied.  We
 hope to get a fully working port by 5.8.0.  (The remaining problems
 relate to the changed IO model of Perl.)  See L<perlmacos>.
 
 =item *
 
-MacOS X (or Darwin) should now be able to build Perl even on HFS+
+Mac OS X (or Darwin) should now be able to build Perl even on HFS+
 filesystems.  (The case-insensitivity confused the Perl build process.)
 
 =item *

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 5df4dd5..bdea91e 100644 (file)
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -1836,13 +1836,13 @@ need a thread library package installed. See README.hpux.
 
 =item *
 
-MacOS Classic (MacPerl has of course been available since
+Mac OS Classic (MacPerl has of course been available since
 perl 5.004 but now the source code bases of standard Perl
 and MacPerl have been synchronised)
 
 =item *
 
-MacOS X (or Darwin) should now be able to build Perl even on HFS+
+Mac OS X (or Darwin) should now be able to build Perl even on HFS+
 filesystems.  (The case-insensitivity used to confuse the Perl build
 process.)
 
@@ -2369,12 +2369,12 @@ getsockname().
 
 =item *
 
-MacOS Classic
+Mac OS Classic
 
-Compilation of the standard Perl distribution in MacOS Classic should
-now work if you have the Metrowerks development environment and
-the missing Mac-specific toolkit bits.  Contact the macperl mailing
-list for details.
+Compilation of the standard Perl distribution in Mac OS Classic should
+now work if you have the Metrowerks development environment and the
+missing Mac-specific toolkit bits.  Contact the macperl mailing list
+for details.
 
 =item *
 

diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod
index 0db19d7..85f7968 100644 (file)
--- a/pod/perlfaq3.pod
+++ b/pod/perlfaq3.pod
@@ -247,10 +247,10 @@ specifically for programming, such as Textpad
 ( http://www.textpad.com/ ) and UltraEdit
 ( http://www.ultraedit.com/ ), among others.
 
-If you are using MacOS, the same concerns apply.  MacPerl
+If you are using Mac OS, the same concerns apply.  MacPerl
 (for Classic environments) comes with a simple editor.
 Popular external editors are BBEdit ( http://www.bbedit.com/ )
-or Alpha ( http://www.kelehers.org/alpha/ ). MacOS X users can
+or Alpha ( http://www.kelehers.org/alpha/ ). Mac OS X users can
 use Unix editors as well.
 
 =over 4

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 2708571..c1efce7 100644 (file)
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -2787,7 +2787,7 @@ If you're running Perl on a system that distinguishes between text
 files and binary files, then you should check out L</binmode> for tips
 for dealing with this.  The key distinction between systems that need
 C<binmode> and those that don't is their text file formats.  Systems
-like Unix, MacOS, and Plan9, which delimit lines with a single
+like Unix, Mac OS, and Plan 9, which delimit lines with a single
 character, and which encode that character in C as C<"\n">, do not
 need C<binmode>.  The rest need it.
 
@@ -5613,7 +5613,7 @@ package.
 =item time
 
 Returns the number of non-leap seconds since whatever time the system
-considers to be the epoch (that's 00:00:00, January 1, 1904 for MacOS,
+considers to be the epoch (that's 00:00:00, January 1, 1904 for Mac OS,
 and 00:00:00 UTC, January 1, 1970 for most other systems).
 Suitable for feeding to C<gmtime> and C<localtime>.
 

diff --git a/pod/perlintro.pod b/pod/perlintro.pod
index 5fc9b66..7429dfb 100644 (file)
--- a/pod/perlintro.pod
+++ b/pod/perlintro.pod
@@ -55,7 +55,7 @@ Alternatively, put this as the first line of your script:
 to be executable first, so C<chmod 755 script.pl> (under Unix).
 
 For more information, including instructions for other platforms such as
-Windows and MacOS, read L<perlrun>.
+Windows and Mac OS, read L<perlrun>.
 
 =head2 Basic syntax overview
 

diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod
index 145309c..ab20799 100644 (file)
--- a/pod/perlpodspec.pod
+++ b/pod/perlpodspec.pod
@@ -883,9 +883,9 @@ character) to the escape sequences or codes necessary for conveying
 such sequences in the target output format.  A converter to *roff
 would, for example know that "\xE9" (whether conveyed literally, or via
 a EE<lt>...> sequence) is to be conveyed as "e\\*'".
-Similarly, a program rendering Pod in a MacOS application window, would
+Similarly, a program rendering Pod in a Mac OS application window, would
 presumably need to know that "\xE9" maps to codepoint 142 in MacRoman
-encoding that (at time of writing) is native for MacOS.  Such
+encoding that (at time of writing) is native for Mac OS.  Such
 Unicode2whatever mappings are presumably already widely available for
 common output formats.  (Such mappings may be incomplete!  Implementers
 are not expected to bend over backwards in an attempt to render

diff --git a/pod/perlport.pod b/pod/perlport.pod
index 3c281f0..fbf81d0 100644 (file)
--- a/pod/perlport.pod
+++ b/pod/perlport.pod
@@ -104,7 +104,7 @@ newlines:
         #...
     }
 
-You can get away with this on Unix and MacOS (they have a single
+You can get away with this on Unix and Mac OS (they have a single
 character end-of-line), but the same program will break under DOSish
 perls because you're only chop()ing half the end-of-line.  Instead,
 chomp() should be used to trim newlines.  The Dunce::Files module can
@@ -373,7 +373,7 @@ Three-arg open can also help protect against this translation in cases
 where it is undesirable.
 
 Don't use C<:> as a part of a filename since many systems use that for
-their own semantics (MacOS Classic for separating pathname components,
+their own semantics (Mac OS Classic for separating pathname components,
 many networking schemes and utilities for separating the nodename and
 the pathname, and so on).  For the same reasons, avoid C<@>, C<;> and
 C<|>.
@@ -2080,8 +2080,8 @@ available at http://www.cpan.org/src/index.html
         HP-UX
         IRIX
         Linux
-        MacOS Classic
-        MacOS X         (Darwin)
+        Mac OS Classic
+        Mac OS X         (Darwin)
         MPE/iX
         NetBSD
         NetWare

diff --git a/pod/perltoot.pod b/pod/perltoot.pod
index e6aa3de..68ce8d4 100644 (file)
--- a/pod/perltoot.pod
+++ b/pod/perltoot.pod
@@ -65,7 +65,7 @@ For example, let's make a simple Person class module.  It gets stored in
 the file Person.pm.  If it were called a Happy::Person class, it would
 be stored in the file Happy/Person.pm, and its package would become
 Happy::Person instead of just Person.  (On a personal computer not
-running Unix or Plan 9, but something like MacOS or VMS, the directory
+running Unix or Plan 9, but something like Mac OS or VMS, the directory
 separator may be different, but the principle is the same.)  Do not assume
 any formal relationship between modules based on their directory names.
 This is merely a grouping convenience, and has no effect on inheritance,