From: Perl 5 Porters Date: Mon, 11 Mar 1996 07:12:18 +0000 (+0000) Subject: Fix miscellaneous typos X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=d28ebecde48fa14623be7a09bf607426f095b6c1;p=p5sagit%2Fp5-mst-13.2.git Fix miscellaneous typos --- diff --git a/pod/perldata.pod b/pod/perldata.pod index 90ac535..4b6e433 100644 --- a/pod/perldata.pod +++ b/pod/perldata.pod @@ -121,7 +121,7 @@ Scalars aren't necessarily one thing or another. There's no place to declare a scalar variable to be of type "string", or of type "number", or type "filehandle", or anything else. Perl is a contextually polymorphic language whose scalars can be strings, numbers, or references (which -includes objects). While strings and numbers are considered the pretty +includes objects). While strings and numbers are considered pretty much same thing for nearly all purposes, references are strongly-typed uncastable pointers with built-in reference-counting and destructor invocation. @@ -189,7 +189,7 @@ So in general you can just assume that scalar(@whatever) == $#whatever + 1; -Some programmer choose to use an explcit conversion so nothing's +Some programmers choose to use an explicit conversion so nothing's left to doubt: $element_count = scalar(@whatever); @@ -311,9 +311,8 @@ quotes you use determines the treatment of the text, just as in regular quoting. An unquoted identifier works like double quotes. There must be no space between the CE> and the identifier. (If you put a space it will be treated as a null identifier, which is valid, and matches the -first blank line--see the Merry Christmas example below.) The terminating -string must appear by itself (unquoted and with no surrounding -whitespace) on the terminating line. +first blank line.) The terminating string must appear by itself +(unquoted and with no surrounding whitespace) on the terminating line. print <Class::func() where using @ISA=qw(... Class ...) and -$r->func() would work (see perlbot man page for more details). +Avoid $r-EClass::func() where using @ISA=qw(... Class ...) and +$r-Efunc() would work (see perlbot man page for more details). Use autosplit so little used or newly added functions won't be a burden to programs which don't use them. Add test functions to @@ -798,7 +798,7 @@ or nature of a variable. For example: $no_caps_here function scope my() or local() variables Function and method names seem to work best as all lowercase. -E.g., $obj->as_string(). +E.g., $obj-Eas_string(). You can use a leading underscore to indicate that a variable or function should not be used outside the package that defined it. @@ -814,7 +814,7 @@ export try to use @EXPORT_OK in preference to @EXPORT and avoid short or common names to reduce the risk of name clashes. Generally anything not exported is still accessible from outside the -module using the ModuleName::item_name (or $blessed_ref->method) +module using the ModuleName::item_name (or $blessed_ref-Emethod) syntax. By convention you can use a leading underscore on names to informally indicate that they are 'internal' and not for public use. diff --git a/pod/perlobj.pod b/pod/perlobj.pod index 59c6f12..81c6c96 100644 --- a/pod/perlobj.pod +++ b/pod/perlobj.pod @@ -76,8 +76,8 @@ so that your constructors may be inherited: return $self; } -Or if you expect people to call not just Cnew()> but also -C<$obj->new()>, then use something like this. The initialize() +Or if you expect people to call not just Cnew()> but also +C<$obj-Enew()>, then use something like this. The initialize() method used will be of whatever $class we blessed the object into: @@ -203,7 +203,7 @@ indirect object slot: display {find Critter "Fred"} 'Height', 'Weight'; -For C++ fans, there's also a syntax using -> notation that does exactly +For C++ fans, there's also a syntax using -E notation that does exactly the same thing. The parentheses are required if there are any arguments. $fred = Critter->find("Fred"); @@ -287,7 +287,7 @@ automatically when the current object is freed. An indirect object is limited to a name, a scalar variable, or a block, because it would have to do too much lookahead otherwise, just like any -other postfix dereference in the language. The left side of -> is not so +other postfix dereference in the language. The left side of -E is not so limited, because it's an infix operator, not a postfix operator. That means that below, A and B are equivalent to each other, and C and D diff --git a/pod/perlop.pod b/pod/perlop.pod index 810cff3..483a686 100644 --- a/pod/perlop.pod +++ b/pod/perlop.pod @@ -384,7 +384,7 @@ As a list operator: @foo = @foo[$#foo-4 .. $#foo]; # slice last 5 items The range operator (in a list context) makes use of the magical -autoincrement algorithm if the operaands are strings. You +autoincrement algorithm if the operands are strings. You can say @alphabet = ('A' .. 'Z'); @@ -960,10 +960,10 @@ list consisting of all the input lines is returned, one line per list element. It's easy to make a I data space this way, so use with care. -The null filehandle <> is special and can be used to emulate the -behavior of B and B. Input from <> comes either from +The null filehandle EE is special and can be used to emulate the +behavior of B and B. Input from EE comes either from standard input, or from each file listed on the command line. Here's -how it works: the first time <> is evaluated, the @ARGV array is +how it works: the first time EE is evaluated, the @ARGV array is checked, and if it is null, C<$ARGV[0]> is set to "-", which when opened gives you standard input. The @ARGV array is then processed as a list of filenames. The loop @@ -984,11 +984,11 @@ is equivalent to the following Perl-like pseudo code: except that it isn't so cumbersome to say, and will actually work. It really does shift array @ARGV and put the current filename into variable -$ARGV. It also uses filehandle I internally--<> is just a synonym +$ARGV. It also uses filehandle I internally--EE is just a synonym for , which is magical. (The pseudo code above doesn't work because it treats as non-magical.) -You can modify @ARGV before the first <> as long as the array ends up +You can modify @ARGV before the first EE as long as the array ends up containing the list of filenames you really want. Line numbers (C<$.>) continue as if the input were one big happy file. (But see example under eof() for how to reset line numbers on each file.) @@ -1008,7 +1008,7 @@ Getopts modules or put a loop on the front like this: ... # code for each line } -The <> symbol will return FALSE only once. If you call it again after +The EE symbol will return FALSE only once. If you call it again after this it will assume you are processing another @ARGV list, and if you haven't set @ARGV, will input from STDIN. @@ -1027,7 +1027,7 @@ $ interpretation is done first, but you can't say C$fooE> because that's an indirect filehandle as explained in the previous paragraph. In older version of Perl, programmers would insert curly brackets to force interpretation as a filename glob: C${foo}E>. -These days, it's consdired cleaner to call the internal function directly +These days, it's considered cleaner to call the internal function directly as C, which is probably the right way to have done it in the first place.) Example: