Errata for Programming Perl

The first sentence in the last paragraph references the wrong line number from the example program on page 19. It references line 15 when it should reference line 19.

Note from the Author or Editor: Change as noted

End of Paragraph #3
================

next LINE if $line =~ /^#/;

Discussion
=========

The above paragraph text refers to an outdated code example (from the 3rd edition of this book). The text should be updated to reflect the latest code example on page 39.

Note from the Author or Editor: Change the text to read:

So now you can probably figure out that when we said:

last LINE if $line =~ /^>/;

we meant “Go to the last iteration of the LINE loop if this line happens to begin with a > character.”

The backtick example snippet at the top of the page says “perldoc $module”, but the text two paragraphs below still says “The $user in our finger example above...”, which refers to the example snippet given in the third edition.

Note from the Author or Editor: Change as noted. Should read: “The $module in our perldoc example above...”

should be

“File ages for -M, -A, and -C are returned in days (including fractional days) since modification/last access/inode change until the script started running.”

Note from the Author or Editor: Change “File ages for -M, -A, and -C are returned in days (including fractional days) since the script started running” to read “File ages for -M, -A, and -C are returned in days (including fractional days) respectively between the last file modification, access, or inode change time and when the script started running.”

should be

“The “Like” column is not always an exact rendition.”

Note from the Author or Editor: Change as noted. [status=fixed in the source]

should be

“For simple strings or numbers, it becomes equivalent to this:”

Note from the Author or Editor: Change as noted. [status=fixed in the source]

should be

“True if exactly one of $a or $b is true, false otherwise”

Note from the Author or Editor: Change as noted.

should be

“it can be safely embedded within other expressions and function calls”

Note from the Author or Editor: Change as noted.

The code examples each read a line from standard input. Because there is a trailing newline at the end of the input string, the output of the warn statement is split into 2 lines. Perhaps the code can be modified by chomping the input string so that the warn statement outputs a single line.

Note from the Author or Editor: On page 134, above both lines that begin with “warn "unknown RGB...”, insert a new line at the same indentation level consisting entirely of

chomp;

should be

“given(EXPR) assigns the value”

Note from the Author or Editor: Change as noted.

The sentence reads, “But if EXPR2 does not get to use smartmatching, then the second argument will not get to either.” I believe it should say EXPR1, not EXPR2.

Note from the Author or Editor: Change as noted. Note that this sentence is in the 2nd paragraph, not the 3rd per the submitted location.

Some < and <= comparisons are missing a whitespace character.

Note from the Author or Editor: Change all those to have a space right before the less-than symbol.

should be

“because 255 might not be U+00FF LATIN SMALL LETTER Y WITH DIAERESIS (ÿ) in the current locale”

Note from the Author or Editor: Change as noted.

The sentence containing “the six translation escapes” should instead read “the seven translation escapes”.

“Table 5-3” should be “Table 5-9” in the following sentence?

Note from the Author or Editor: Change as noted

Unintended space following “\” in these table entries:

and following “\c” in this table entry:

Note from the Author or Editor: Changed as noted.

s/give/given/

Note from the Author or Editor: Change as noted.

There’s whitespace between “(” and “:full”, which seems unintentional.

Note from the Author or Editor: Change as noted.

The phrase at the start of the second line of the second paragraph that reads “Unicode names sequence” should instead read “Unicode named sequence”.

should be

“That means a codepoint like U+03A9, GREEK CAPITAL LETTER OMEGA, is always a \w character.”

Note from the Author or Editor: Change as noted.

should read

“Joining punctuation like an underscore”

The entries under the last column, labelled Name, should be set in small capitals.

s/second/first/

Note from the Author or Editor: Change as noted.

The phrase in the table reading “occurring continuous ranges” should read “occurring in continuous ranges”.

s/s'/'s/

Note from the Author or Editor: Change as noted.

The first colon looks lonely. s/:/::/

Note from the Author or Editor: Change as noted.

should be

“Now access your named captures through those variables, just as you did with %+ and %-, but using your own names.”

Note from the Author or Editor: Change as noted.

Delete the two words “other modifiers”, because “modifiers” occurs after the list.

Change “six translation escapes” to “seven translation escapes”.

Change “Table 5-3” to “Table 5-9”.

Note from the Author or Editor: Change as noted.

s/longer/long/ (or some other wording)

Note from the Author or Editor: Change “more than 10k longer” to “over 10k in length”.

I think the following refers to Table 5-9 instead of 5-3:

Note from the Author or Editor: Change as noted

Superfluous space before PATTERN. The header doesn’t have a space there, and neither do the similar sentences about (?=PATTERN) and (?!PATTERN).

Same thing on page 249, 4th paragraph:

Note from the Author or Editor: Change as noted.

Change “for left to right” to “from left to right”.

Note from the Author or Editor: Change as noted.

Superfluous space before PATTERN.

(I searched for ' PATTERN)' in the PDF and didn’t find any more.)

Note from the Author or Editor: Change as noted.

Here’s a list of straight quotes that should be curly quotes. I don’t feel like flooding the errata list with separate submissions.

Note from the Author or Editor: Change all the non-literals as noted.

The '#' on the following line:

say "REGEX is $re\n";             # debugging output

is not aligned with the others, and the \n should be dropped.

(Compared to the 3rd edition, “print” has been changed to “say”, but the \n and vertical alignment weren’t updated to match.)

Note from the Author or Editor: Change the say back to a print.

Assuming Perl v5.14, change “REGEX is (?i-xsm:” to “REGEX is (?^ui:”.

Note from the Author or Editor: Change as noted.

The phrase “pieces you that you’ve” looks incorrect in the following sentence (remove “you”?):

Note from the Author or Editor: “pieces you that you’ve” should have the first “you” removed.

This sentence probably intends to refer to chapter 7:

Note from the Author or Editor: Change as noted

The phrase “maintains a high level Perl compatibility” is missing the word “of” and so should read “maintains a high level of Perl compatibility”.

Change “See 19.” to “See Chapter 17.”

In the following sentence, I think “seen” should be “see”:

Note from the Author or Editor: “you’ll even seen” should read “you’ll even see”.

I cannot find a method by the name of “Filter_Value” in the DBM_Filter module documentation. I presume that the method “Filter_Value_Push” was meant to be used instead. Therefore the following change should be made:

should be

$dbobj->Filter_Value_Push("utf8");

Note from the Author or Editor: Change as noted

Change “two string” to “two strings”.

Note from the Author or Editor: Change as noted

should be

“That is, a single user-visible character (a grapheme) can require more than a single codepoint to represent it.”

Note from the Author or Editor: Change as noted

Change “LATIN LETTER SMALL O” to “LATIN SMALL LETTER O”.

Note from the Author or Editor: Change as noted

In the following sentence, I think it should read, “This may be what you want ...”:

Note from the Author or Editor: “This may be want you want” should read “This may be what you want”.

Change “LATIN LETTER SMALL E WITH ACUTE” to “LATIN SMALL LETTER E WITH ACUTE”.

Note from the Author or Editor: Change as noted

Change “LATIN LETTER SMALL E” to “LATIN SMALL LETTER E”.

Note from the Author or Editor: Change as noted

There should be a comma between “combining characters” and “variation selectors”.

“to know about more” should read “to know more about”.

Change “\x{COMBINING TILDE}” to “\N{COMBINING TILDE}”.

Note from the Author or Editor: Change as noted

Change “strings comparisons” to “string comparisons”.

Note from the Author or Editor: Change as noted

Change “East_Asian_Width=Full” to “East_Asian_Width=Fullwidth”.

Note from the Author or Editor: Change per description.

should be

“Rider” and “Riding” should go together

Note from the Author or Editor: Change as noted

Change “differ” to “are the same” in the phrase

Note from the Author or Editor: Change as noted.

Change “forwards compatibility” to “forward compatibility”.

Note from the Author or Editor: Change as noted

The following refers to Table 5-6, and I think it might be Table 5-12 instead (not sure):

Note from the Author or Editor: It should refer to table 5-11, not to 5-6.

Page 311 has the following sentence:

The preceding page (310) has this sentence:

The ‘“&”’ on page 311 looks different from the ‘“&"’ on page 310.

Note from the Author or Editor: The ampersand should be a literal in “to remember not to use “&” for the first”.

In the following table entries “mysin” ne “mysyn”:

Note from the Author or Editor: Both instances of “mysyn” should read “mysin”.

In the following sentence, I think it meant to say, “an indirect filehandle”:

Note from the Author or Editor: Change as noted.

The first “typeglob” should be in plural, too.

Note from the Author or Editor: Change as noted.

s/"with/" with/

Note from the Author or Editor: Change as noted.

In the following example, there is a semicolon (;) in front of “@_” that I don’t think was intended:

@colors = qw(red blue green yellow orange purple violet);
for my $name (@colors) {
    no strict "refs"; # Allow symbolic references
    *$name = *{uc $name} = sub { "<FONT COLOR='$name'>;@_</FONT>" };
}

Note from the Author or Editor: Change as noted.

It’s “say” now.

Note from the Author or Editor: Change as noted.

That should end with “in their import lists”.

Note from the Author or Editor: Change as noted.

The following sentence appears to be missing something (perhaps a word like “building” or “creating” or “defining” or ...?):

Note from the Author or Editor: Change “ways for a module” to “flavors of modules”.

“CPAN:DistnameInfo” needs another colon.

Note from the Author or Editor: Change as noted.

I think you meant, “Notice the lack of a comma ...”:

Note from the Author or Editor: Change as noted.

The text

should read

“has a similar problem”

The spurious “>” after Bombadil should be deleted.

There is a spurious paragraph break after “the result with make”.

Not technically wrong, but "\015\12" usually appears as "\015\012":

Note from the Author or Editor: Change "\015\12" to "\015\012", as noted

Should be:

“Any value 0400 or above makes Perl slurp in whole files at once, but, by convention, the value 0777 is normally used for this.”

Note from the Author or Editor: Change as noted

There are two instances of curly quotes following -M that should be straight quotes.

Instead of

it should read “Other layers that would affect”.

Note from the Author or Editor: Change as noted

I think you meant “is a sophisticated tool” or “is a sophisticated set of tools”:

Note from the Author or Editor: Change “tools” to “tool”

Did you mean “Encodings” because of “They”?

Note from the Author or Editor: I’d rewrite this as “You cannot guess an encoding; you have to specify it.”

I can’t seem to find File::Mmap, e.g.,

https://metacpan.org/search?q=file%3A%3Ammap
http://search.cpan.org/search?query=file%3A%3Ammap

Note from the Author or Editor: Change “File::Mmap” to “File::Map”

1) Granted that it depends on the pod translator, I still expected “touch -t” to appear in bold in this example.
2) Here and in many other places, both in the text and in examples, the hyphen appears as “–”. Granted “–” looks like an ascii hyphen, but if it’s supposed to be one, then it should be one. IMO. :–)

Note from the Author or Editor: The “touch” and the “–t” should be rendered in bold, but are currently italic.

This link goes to this address:

http://www.stackoverflow.com/

Note from the Author or Editor: Change “con” to “com” in the domain name.

Missing “$”:

Note from the Author or Editor: Change as noted.

I may be making a stretch, but I don’t think you meant, “each variable description in Table 25-1”, because there aren’t any variable descriptions in that table:

Note from the Author or Editor: Delete “in Table 25.1”

This variable description is lacking an annotation, e.g., “[DYN]”:

Note from the Author or Editor: Prefix paragraph with “[DYN, RO]”.

This variable description looks odd, as though there are two different versions of the description (each beginning with an “[ALL]”):

Note from the Author or Editor: Delete the second of the two paragraphs beginning with [ALL].

This variable description is lacking an annotation, e.g., “[DYN,RO]”:

Note from the Author or Editor: Change as noted.

... q/, and nonzero binary with “0b”/ ... ?

Note from the Author or Editor: Add “nonzero binary with “0b”” after “nonzero hex with “0x”” in the fifth row in the table.

From the department of redundancy department:

Note from the Author or Editor: Remove “, too”

I can’t seem to find a verb:

Note from the Author or Editor: Change to “The < and > indicate the endianness for the specifiers d, ...”

More additional extra redundancy:

Note from the Author or Editor: Remove the “, too”

Are those last two paragraph repeats of the first two?

Note from the Author or Editor: Delete the last two paragraphs of the fork section: they’re duplicates.

Did you mean “The Socket module has a ...”:

Note from the Author or Editor: Change as noted

Did you mean “# 0 1 2”:

#  1      2         3
($name, $aliases, $protocol_number) = getprotobynumber(6);

Note from the Author or Editor: Change as noted

#  1      2         3
($name, $aliases, $protocol_number) = getprotoent();

Note from the Author or Editor: It should be # 0 1 2 in both cases on this page

You mention ‘use feature "fc"’ in the ‘lc’ section (and the one for ‘uc’), but not in the one for ‘fc’:

Note from the Author or Editor: Change the fc function on page 860 from reading simply “New to v5.16” to reading “New to v5.16 where it is enabled with use feature "fc",”

Did you mean something like this:

$thisday = qw(Sun Mon Tue Wed Thu Fri Sat)[(localtime)[6]];

Don’t get me wrong; I’m not the code police. It’s just that it’s been so long since I programmed with bare words, this looked like a syntax error:

Note from the Author or Editor: Quote each word in the list for strict complacence.

The “use” in “use IPC::SysV” is different than where that phrase is used elsewhere (e.g., further down that page):

Note from the Author or Editor: Set the “use” as a literal, like the other one.

I think you mean “$dec_perms” instead of “$perms”:

$dec_perms = (stat("filename"))[2] & 07777;
$oct_perm_str = sprintf "%o", $perms;

Note from the Author or Editor: Change $perms to $dec_perms

should maybe be something like:

“To find the codepoint for a character that gives its name as a string, use the charnames::vianame function from the charnames pragma.”

Note from the Author or Editor: It should read: “given its name as a string”, and “functions” should be changed to “function”.

The text states that the ‘say’ keyword:

This is an incorrect citation; this section is not relevant to enabling the “say” feature and does not refer to it at all.

The correct citation would be to the section on the feature pragma on page 1017.

Note from the Author or Editor: Change as noted

The sentence says, “print” but the example says, “say”:

Note from the Author or Editor: Change to “Since a say function is a LIST operator”

Did you mean “effects”? (Please don’t hit me.)

Note from the Author or Editor: Change “affects” back to “effects” per Camel3.

s/\.systems/systems/;

Note from the Author or Editor: The period at the front of the line should be its end.

The index references a unknown comparison operator: “cpm”. Should have been “cmp”.

Note from the Author or Editor: Change as noted

Change:

cdebugger ommand

to

debugger command.

Also, change

underPrint

to

undefPrint

Note from the Author or Editor: Change as noted