Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
a few typo fixes
Message-Id: <200111120515.fAC5FIc74795@ventrue.corp.yahoo.com>

Patching README.foo instead of pod/perlfoo.pod,
not patching Math::BigInt (Tels will take care of that),
dropping broken hv.c and sv.h patches, patching libnetcfg.PL
and perldoc.PL instead of libnetcfg and perldoc, patching
ext/Digest/MD5/t/files.t since MD5.pm was changed.

p4raw-id: //depot/perl@12954
  • Loading branch information
Jeffrey Friedl authored and jhi committed Nov 12, 2001
1 parent bf0fa0b commit d1be940
Show file tree
Hide file tree
Showing 109 changed files with 252 additions and 252 deletions.
2 changes: 1 addition & 1 deletion Porting/pumpkin.pod
Expand Up @@ -1136,7 +1136,7 @@ but not so much that it posed any serious problems.

=item Metaconfig worked for me

My system at the time was Interactive 2.2, a SVR3.2/386 derivative that
My system at the time was Interactive 2.2, an SVR3.2/386 derivative that
also had some POSIX support. Metaconfig-generated Configure scripts
worked fine for me on that system. On the other hand, autoconf-generated
scripts usually didn't. (They did come quite close, though, in some
Expand Down
2 changes: 1 addition & 1 deletion README.amiga
Expand Up @@ -82,7 +82,7 @@ same way as on any other platform, by
perl foo arg1 arg2 arg3

If you want to specify perl options C<-my_opts> to the perl itself (as
opposed to to your program), use
opposed to your program), use

perl -my_opts foo arg1 arg2 arg3

Expand Down
4 changes: 2 additions & 2 deletions README.bs2000
@@ -1,5 +1,5 @@
This document is written in pod format hence there are punctuation
characters in in odd places. Do not worry, you've apparently got the
characters in odd places. Do not worry, you've apparently got the
ASCII->EBCDIC translation worked out correctly. You can read more
about pod in pod/perlpod.pod or the short summary in the INSTALL file.

Expand Down Expand Up @@ -151,7 +151,7 @@ C</START-PROG FROM-FILE=*MODULE(PERL,PERL),PROG-MODE=*ANY,RUN-MODE=*ADV>
First you get the BS2000 commandline prompt ('*'). Here you may enter
your parameters, e.g. C<-e 'print "Hello World!\\n";'> (note the
double backslash!) or C<-w> and the name of your Perl script.
Filenames starting with C</> are searched in in the Posix filesystem,
Filenames starting with C</> are searched in the Posix filesystem,
others are searched in the BS2000 filesystem. You may even use
wildcards if you put a C<%> in front of your filename (e.g. C<-w
checkfiles.pl %*.c>). Read your C/C++ manual for additional
Expand Down
2 changes: 1 addition & 1 deletion README.ce
Expand Up @@ -41,7 +41,7 @@ Before you start, you need to build celib.dll and w32console.
See instructions in these packages for building.

In the wince directory, type "nmake -f makefile.ce". This should
build perl.exe and and perl.dll. For building extension dlls,
build perl.exe and perl.dll. For building extension dlls,
type "nmake -f makefile.ce dlls"

When building ext dlls, you get lots of macro redefinition
Expand Down
4 changes: 2 additions & 2 deletions README.epoc
Expand Up @@ -12,7 +12,7 @@ Perl 5 README file for the EPOC operating system.

=head1 INTRODUCTION

EPOC is a OS for palmtops and mobile phones. For more informations look at:
EPOC is an OS for palmtops and mobile phones. For more informations look at:
http://www.symbian.com/

This is a port of perl to EPOC. It runs on ER5 machines: Psion 5mx,
Expand Down Expand Up @@ -58,7 +58,7 @@ debugger. If you are leaving perl, you get into the system screen. You
have to switch back manually to ESHELL. When perl is running, you will
see a task with the name STDOUT in the task list.

If you have a ER3 machine (i.e. a PSION 5), you may have to supply the
If you have an ER3 machine (i.e. a PSION 5), you may have to supply the
full path to the perl executable C:\system\programs\perl.exe.

If you need to set the current directory of perl, please use the
Expand Down
2 changes: 1 addition & 1 deletion README.hpux
Expand Up @@ -127,7 +127,7 @@ chip type used. (Start browsing at the bottom to prevent confusion ;-)
An executable compiled on a PA-RISC 2.0 platform will not execute on a
PA-RISC 1.1 platform, even if they are running the same version of
HP-UX. If you are building Perl on a PA-RISC 2.0 platform and want that
Perl to to also run on a PA-RISC 1.1, the compiler flags +DAportable and
Perl to also run on a PA-RISC 1.1, the compiler flags +DAportable and
+DS32 should be used.

It is no longer possible to compile PA-RISC 1.0 executables on either
Expand Down
8 changes: 4 additions & 4 deletions README.os2
Expand Up @@ -262,7 +262,7 @@ same way as on any other platform, by
perl foo.pl arg1 arg2 arg3

If you want to specify perl options C<-my_opts> to the perl itself (as
opposed to to your program), use
opposed to your program), use

perl -my_opts foo.pl arg1 arg2 arg3

Expand Down Expand Up @@ -386,7 +386,7 @@ there is an executable file F<blah.exe> I<anywhere> on C<PATH>.

Note also that executable files on OS/2 can have an arbitrary extension,
but F<.exe> will be automatically appended if no dot is present in the name.
The workaround as as simple as that: since F<blah.> and F<blah> denote the
The workaround is as simple as that: since F<blah.> and F<blah> denote the
same file, to start an executable residing in file F<n:/bin/blah> (no
extension) give an argument C<n:/bin/blah.> (dot appended) to system().

Expand Down Expand Up @@ -1185,7 +1185,7 @@ C<BEGIN_LIBPATH>.

Returns C<undef> if it was not called yet, otherwise bit 1 is
set if on the previous call do_harderror was enabled, bit
2 is set if if on previous call do_exception was enabled.
2 is set if on previous call do_exception was enabled.

This function enables/disables error popups associated with
hardware errors (Disk not ready etc.) and software exceptions.
Expand Down Expand Up @@ -1639,7 +1639,7 @@ of the F<.EXE> file are loaded is decided at compile-time, thus all the
processes have these sections loaded at same addresses, and no fixup
of internal links inside the F<.EXE> is needed.

Since DLLs may be loaded at run time, to have the same mechanism for for DLLs
Since DLLs may be loaded at run time, to have the same mechanism for DLLs
one needs to have the address range of I<any of the loaded> DLLs in the
system to be available I<in all the processes> which did not load a particular
DLL yet. This is why the DLLs are mapped to the shared memory region.
Expand Down
2 changes: 1 addition & 1 deletion README.vmesa
Expand Up @@ -82,7 +82,7 @@ statements in the preprocessor output (.i) file.
=head2 Testing Anomalies of Perl on VM/ESA

The `make test` step runs a Perl Verification Procedure, usually before
installation. As the 5.6.1 kit was was being assembled
installation. As the 5.6.1 kit was being assembled
the following "failures" were known to appear on some machines
during `make test` (mostly due to ASCII vs. EBCDIC conflicts),
your results may differ:
Expand Down
2 changes: 1 addition & 1 deletion README.vos
Expand Up @@ -49,7 +49,7 @@ following additional items.
The VOS Standard C Compiler (or the VOS Standard C
Cross-Compiler) and the VOS C Runtime. If you are using
the generally-available version of POSIX support, you may
instead use the the VOS GNU C/C++ Compiler. These are
instead use the VOS GNU C/C++ Compiler. These are
standard Stratus products.

=item 2
Expand Down
2 changes: 1 addition & 1 deletion README.win32
Expand Up @@ -84,7 +84,7 @@ case letters, they will be compiled into appropriate .obj-files named
with all lowercase letters, and every time dmake is invoked
to bring files up to date, it will try to recompile such files again.
For example, Tk distribution has a lot of such files, resulting in
needless recompiles everytime dmake is invoked. To avoid this, you
needless recompiles every time dmake is invoked. To avoid this, you
may use the script "sync_ext.pl" after a successful build. It is
available in the win32 subdirectory of the Perl source distribution.

Expand Down
2 changes: 1 addition & 1 deletion XSUB.h
Expand Up @@ -130,7 +130,7 @@ handled by C<xsubpp>.
Return an integer from an XSUB immediately. Uses C<XST_mIV>.
=for apidoc Am|void|XSRETURN_NV|NV nv
Return an double from an XSUB immediately. Uses C<XST_mNV>.
Return a double from an XSUB immediately. Uses C<XST_mNV>.
=for apidoc Am|void|XSRETURN_PV|char* str
Return a copy of a string from an XSUB immediately. Uses C<XST_mPV>.
Expand Down
2 changes: 1 addition & 1 deletion dosish.h
Expand Up @@ -90,7 +90,7 @@
* as the first line of a Perl program designed to be executed directly
* by name, instead of the standard Unix #!. If ALTERNATE_SHEBANG
* begins with a character other then #, then Perl will only treat
* it as a command line if if finds the string "perl" in the first
* it as a command line if it finds the string "perl" in the first
* word; otherwise it's treated as the first line of code in the script.
* (IOW, Perl won't hand off to another interpreter via an alternate
* shebang sequence that might be legal Perl code.)
Expand Down
2 changes: 1 addition & 1 deletion ext/B/B.pm
Expand Up @@ -867,7 +867,7 @@ print_subs() is a B::GV method you have declared.
Takes any Perl variable and turns it into an object in the
appropriate B::OP-derived or B::SV-derived class. Apart from functions
such as C<main_root>, this is the primary way to get an initial
"handle" on a internal perl data structure which can then be followed
"handle" on an internal perl data structure which can then be followed
with the other access methods.
=item ppname(OPNUM)
Expand Down
2 changes: 1 addition & 1 deletion ext/B/B/Deparse.pm
Expand Up @@ -2957,7 +2957,7 @@ sub pp_entersub {
}
} else {
# glob() invocations can be translated into calls of
# CORE::GLOBAL::glob with an second parameter, a number.
# CORE::GLOBAL::glob with a second parameter, a number.
# Reverse this.
if ($kid eq "CORE::GLOBAL::glob") {
$kid = "glob";
Expand Down
2 changes: 1 addition & 1 deletion ext/Data/Dumper/Dumper.pm
Expand Up @@ -747,7 +747,7 @@ references are not dumped; instead, their names are inserted wherever they
are encountered subsequently. This is useful especially for properly
dumping subroutine references.
Expects a anonymous hash of name => value pairs. Same rules apply for names
Expects an anonymous hash of name => value pairs. Same rules apply for names
as in C<new>. If no argument is supplied, will return the "seen" list of
name => value pairs, in a list context. Otherwise, returns the object
itself.
Expand Down
2 changes: 1 addition & 1 deletion ext/Digest/MD5/MD5.pm
Expand Up @@ -113,7 +113,7 @@ The constructor returns a new C<Digest::MD5> object which encapsulate
the state of the MD5 message-digest algorithm. You can add data to
the object and finally ask for the digest.
If called as a instance method (i.e. $md5->new) it will just reset the
If called as an instance method (i.e. $md5->new) it will just reset the
state the object to the state of a newly created object. No new
object is created in this case.
Expand Down
2 changes: 1 addition & 1 deletion ext/Digest/MD5/t/files.t
Expand Up @@ -20,7 +20,7 @@ $EXPECT = <<EOT;
EOT
} else { # ASCII
$EXPECT = <<EOT;
bf8c3c72d071d1c0303fc9e311820708 ext/Digest/MD5/MD5.pm
665ddc08b12d6b1bf85ac6dc5aae68b3 ext/Digest/MD5/MD5.pm
95444a9c6ad17e443e4606c6c7fd9e28 ext/Digest/MD5/MD5.xs
EOT
}
Expand Down
2 changes: 1 addition & 1 deletion ext/DynaLoader/dl_dyld.xs
Expand Up @@ -76,7 +76,7 @@ static void TranslateError
{
"%s(%d): Object Image Load Failure\n",
"%s(%d): Object Image Load Success\n",
"%s(%d): Not an recognisable object file\n",
"%s(%d): Not a recognisable object file\n",
"%s(%d): No valid architecture\n",
"%s(%d): Object image has an invalid format\n",
"%s(%d): Invalid access (permissions?)\n",
Expand Down
2 changes: 1 addition & 1 deletion ext/DynaLoader/dl_next.xs
Expand Up @@ -85,7 +85,7 @@ static void TranslateError
{
"%s(%d): Object Image Load Failure\n",
"%s(%d): Object Image Load Success\n",
"%s(%d): Not an recognisable object file\n",
"%s(%d): Not a recognisable object file\n",
"%s(%d): No valid architecture\n",
"%s(%d): Object image has an invalid format\n",
"%s(%d): Invalid access (permissions?)\n",
Expand Down
2 changes: 1 addition & 1 deletion ext/Encode/Encode.pm
Expand Up @@ -597,7 +597,7 @@ the encoding by picking the first in the following sequence:
=item * The name in the IANA registry.
=item * The name used by the the organization that defined it.
=item * The name used by the organization that defined it.
=back
Expand Down
2 changes: 1 addition & 1 deletion ext/IO/lib/IO/Dir.pm
Expand Up @@ -201,7 +201,7 @@ for details of these functions.
=back
C<IO::Dir> also provides a interface to reading directories via a tied
C<IO::Dir> also provides an interface to reading directories via a tied
HASH. The tied HASH extends the interface beyond just the directory
reading routines by the use of C<lstat>, from the C<File::stat> package,
C<unlink>, C<rmdir> and C<utime>.
Expand Down
4 changes: 2 additions & 2 deletions ext/IO/lib/IO/File.pm
Expand Up @@ -51,7 +51,7 @@ these classes with methods that are specific to file handles.
=item new ( FILENAME [,MODE [,PERMS]] )
Creates a C<IO::File>. If it receives any parameters, they are passed to
Creates an C<IO::File>. If it receives any parameters, they are passed to
the method C<open>; if the open fails, the object is destroyed. Otherwise,
it is returned to the caller.
Expand All @@ -78,7 +78,7 @@ whitespace or other special characters, and the second parameter is
the open mode, optionally followed by a file permission value.
If C<IO::File::open> receives a Perl mode string ("E<gt>", "+E<lt>", etc.)
or a ANSI C fopen() mode string ("w", "r+", etc.), it uses the basic
or an ANSI C fopen() mode string ("w", "r+", etc.), it uses the basic
Perl C<open> operator (but protects any special characters).
If C<IO::File::open> is given a numeric mode, it passes that mode
Expand Down
6 changes: 3 additions & 3 deletions ext/IO/lib/IO/Handle.pm
Expand Up @@ -48,7 +48,7 @@ Creates a new C<IO::Handle> object.
=item new_from_fd ( FD, MODE )
Creates a C<IO::Handle> like C<new> does.
Creates an C<IO::Handle> like C<new> does.
It requires two parameters, which are passed to the method C<fdopen>;
if the fdopen fails, the object is destroyed. Otherwise, it is returned
to the caller.
Expand Down Expand Up @@ -105,7 +105,7 @@ Furthermore, for doing normal I/O you might need these:
=item $io->fdopen ( FD, MODE )
C<fdopen> is like an ordinary C<open> except that its first parameter
is not a filename but rather a file handle name, a IO::Handle object,
is not a filename but rather a file handle name, an IO::Handle object,
or a file descriptor number.
=item $io->opened
Expand Down Expand Up @@ -220,7 +220,7 @@ the taint-clean flag failed. (eg invalid handle)
=head1 NOTE
A C<IO::Handle> object is a reference to a symbol/GLOB reference (see
An C<IO::Handle> object is a reference to a symbol/GLOB reference (see
the C<Symbol> package). Some modules that
inherit from C<IO::Handle> may want to keep object related variables
in the hash table part of the GLOB. In an attempt to prevent modules
Expand Down
2 changes: 1 addition & 1 deletion ext/IO/lib/IO/Pipe.pm
Expand Up @@ -198,7 +198,7 @@ processes.
=item new ( [READER, WRITER] )
Creates a C<IO::Pipe>, which is a reference to a newly created symbol
Creates an C<IO::Pipe>, which is a reference to a newly created symbol
(see the C<Symbol> package). C<IO::Pipe::new> optionally takes two
arguments, which should be objects blessed into C<IO::Handle>, or a
subclass thereof. These two objects will be used for the system call
Expand Down
2 changes: 1 addition & 1 deletion ext/IO/lib/IO/Select.pm
Expand Up @@ -281,7 +281,7 @@ cache which is indexed by the C<fileno> of the handle, so if more than one
handle with the same C<fileno> is specified then only the last one is cached.
Each handle can be an C<IO::Handle> object, an integer or an array
reference where the first element is a C<IO::Handle> or an integer.
reference where the first element is an C<IO::Handle> or an integer.
=item remove ( HANDLES )
Expand Down
2 changes: 1 addition & 1 deletion ext/IO/lib/IO/Socket.pm
Expand Up @@ -432,7 +432,7 @@ is returned.
=item sockdomain
Returns the numerical number for the socket domain type. For example, for
a AF_INET socket the value of &AF_INET will be returned.
an AF_INET socket the value of &AF_INET will be returned.
=item sockopt(OPT [, VAL])
Expand Down
12 changes: 6 additions & 6 deletions ext/Storable/Storable.xs
Expand Up @@ -191,8 +191,8 @@ typedef double NV; /* Older perls lack the NV type */
*/
#define SX_ITEM 'i' /* An array item introducer */
#define SX_IT_UNDEF 'I' /* Undefined array item */
#define SX_KEY 'k' /* An hash key introducer */
#define SX_VALUE 'v' /* An hash value introducer */
#define SX_KEY 'k' /* A hash key introducer */
#define SX_VALUE 'v' /* A hash value introducer */
#define SX_VL_UNDEF 'V' /* Undefined hash value */

/*
Expand Down Expand Up @@ -238,7 +238,7 @@ struct extendable {

/*
* At store time:
* An hash table records the objects which have already been stored.
* A hash table records the objects which have already been stored.
* Those are referred to as SX_OBJECT in the file, and their "tag" (i.e.
* an arbitrary sequence number) is used to identify them.
*
Expand Down Expand Up @@ -1853,7 +1853,7 @@ sortcmp(const void *a, const void *b)
/*
* store_hash
*
* Store an hash table.
* Store a hash table.
*
* Layout is SX_HASH <size> followed by each key/value pair, in random order.
* Values are stored as <object>.
Expand Down Expand Up @@ -2796,7 +2796,7 @@ static int store(stcxt_t *cxt, SV *sv)
* stored, before recursing...
*
* In order to avoid creating new SvIVs to hold the tagnum we just
* cast the tagnum to a SV pointer and store that in the hash. This
* cast the tagnum to an SV pointer and store that in the hash. This
* means that we must clean up the hash manually afterwards, but gives
* us a 15% throughput increase.
*
Expand Down Expand Up @@ -3377,7 +3377,7 @@ static SV *retrieve_hook(stcxt_t *cxt, char *cname)
TRACEME(("class name: %s", class));

/*
* Decode user-frozen string length and read it in a SV.
* Decode user-frozen string length and read it in an SV.
*
* For efficiency reasons, we read data directly into the SV buffer.
* To understand that code, read retrieve_scalar()
Expand Down
4 changes: 2 additions & 2 deletions ext/XS/Typemap/Typemap.xs
Expand Up @@ -120,7 +120,7 @@ T_AVREF( av )
=item T_HVREF

From the perl level this is a reference to a perl hash.
From the C level this is a pointer to a HV.
From the C level this is a pointer to an HV.

=cut

Expand Down Expand Up @@ -201,7 +201,7 @@ T_UV( uv )
=item T_IV

A signed integer. This is cast to the required integer type when
passed to C and converted to a IV when passed back to Perl.
passed to C and converted to an IV when passed back to Perl.

=cut

Expand Down
2 changes: 1 addition & 1 deletion ext/threads/shared/shared.pm
Expand Up @@ -141,7 +141,7 @@ C<share>, C<lock>, C<unlock>, C<cond_wait>, C<cond_signal>, C<cond_broadcast>
=item share VARIABLE
C<share> takes a value and marks it as shared, you can share an scalar, array, hash
C<share> takes a value and marks it as shared, you can share a scalar, array, hash
scalar ref, array ref and hash ref, C<share> will return the shared value.
C<share> will traverse up references exactly I<one> level.
Expand Down

0 comments on commit d1be940

Please sign in to comment.