Errata

"We declare the $fh variable with state ..."

should be

"We declare the $fhs variable with state ..."

Note from the Author or Editor:
Change as noted, adding an 's' to the variable name.

This is the sentence:

"Our module will still go into CPAN, but it won?t be index and PAUSE will send us an email explaining what went wrong."

Change "index" to "indexed".

This is the part from the code examples:

is( Acme::GILLIGAN::Utils::sum( @weird_list), 129,
'The weird sum is 128' );

Change to:

is( Acme::GILLIGAN::Utils::sum( @weird_list), 129,
'The weird sum is 129' );

Note from the Author or Editor:
Change that 128 to a 129

This is the part of the sentence:

"add required_items_ok to @EXPORT"

Change to:

"add check_required_items_ok to @EXPORT"

This is the line:

stdout_is( \&print_hello, "Welcome Aboard\n" );

Change to:

stdout_is( \&print_hello, "Welcome Aboard!\n" );

Note from the Author or Editor:
Adds exclamation point

This is the part of the sentence:

"it outputs special ok messages so keep the test numbering right"

Change to:

"it outputs special ok messages to keep the test numbering right"

Note from the Author or Editor:
change "so" to "to"

These are the lines:

like( $at, qr/You must/, 'sound() dies with a message' );
like( $at, qr/You must/, 'speak() dies with a message' );

Change to:

like( $at, qr/You have/, 'sound() dies with a message' );
like( $at, qr/You have/, 'speak() dies with a message' );

Note from the Author or Editor:
These are two lines in different places in the first code block. Change "must" to "have"

Change "retreive" to "retrieve".

This is the sentence:

"When we do that, we don't need a default speak subroutine because we can use the role features to denote that all classes using this role need to define their own sound:"

Shouldn't "speak subroutine" really be "sound subroutine"?

Note from the Author or Editor:
Change "speak subroutine" to "sound subroutine"

Change "the tests appears" to "the tests appear".

This is the line:

## include animal classes from previous chapter...

Change "previous chapter" to "Chapter 15".

This is the code section:

is( sum( 4, -9, 37, 6 ), 38, '4-9+37+6 is six' );

Change to:

is( sum( 4, -9, 37, 6 ), 38, '4-9+37+6 is 38' );

Change "theExporter" to "the Exporter".

This is the part of the sentence:

"(e.g., File::Basename to the importing namespace (e.g., main)."

Change to:

"(e.g., File::Basename) to the importing namespace (e.g., main)."

This is the sentence:

"Now we're going to show how to get our own modules do that."

Change to:

"Now we're going to show how to get our own modules to do that."

Note from the Author or Editor:
Add a "to" in front of "do"

This is the sentence:

"Write a script that uses your module and prints the values for the date, month, and year."

In order to match the beginning of the exercise description, change "date" to "day". This change should also be reflected in the solutions on pages 346 and 347.

Note from the Author or Editor:
One page 247, exercise 1, change "named day" to "named date". Ignore the issues on the other pages.

This is the sentence:

"neigh is the return value, which ends up as the earlier $noise variable."

Change "as" to "in".

This is the line:

"Figure 4-9. The PeGS structure for the %gilligan_info hash"

It seems redundant to include the word "structure" since PeGS (i.e. "Perl Graphical Structure") already contains that word.

In fact, the way PeGS is referred to throughout the book is inconsistent. Sometimes we see the text "PeGS diagram", other times "PeGS structure", and then just "PeGS". Perhaps its use can be standardized to one of these.

Note from the Author or Editor:
Change "PeGS structure" to "PeGS"

Change "PeGs" to "PeGS".

Change "PeGs" to "PeGS".

Change "PeGs" to "PeGS".

Change "where they called wrong method" to "where they called the wrong method".

This is the code section:

if( ) { ... }
elsif() { ... }
else { ... }

unless()
elsif() { ... }
else { ... }

give( ... ) {
when { ... }
when { ... }
when { ... }
}

Change to:

if() { ... }
elsif() { ... }
else { ... }

unless() { ... }
elsif() { ... }
else { ... }

given() {
when() { ... }
when() { ... }
when() { ... }
default { ... }
}

Note from the Author or Editor:
Add "n" to make "give" "given", and add "default {...}" in that block.

This is the line:

like( $at, qr/You must/, 'sound() dies with a message' );

Change to:

like( $at, qr/You have/, 'sound() dies with a message' );

The above change should also be applied to the examples on pages 219, 220, 342, and 343.

Note from the Author or Editor:
Change as noted

This is the line:

t/boilerplate.t (Wstat: 0 Tests: 6 Failed: 0)

Change to:

t/boilerplate.t (Wstat: 0 Tests: 7 Failed: 0)

Note from the Author or Editor:
Change as noted

This is the line:

use Test::More tests => 6;

Change to:

use Test::More tests => 7;

The following sentence should be rewritten:

"We try it with works with its default variable, $_:"

Note from the Author or Editor:
Change to "We try it with its default variable, $_:", removing the "with works"

This is the line:

t/boilerplate.t (Wstat: 0 Tests: 6 Failed: 0)

Change to:

t/boilerplate.t (Wstat: 0 Tests: 7 Failed: 0)

Change "1..6" to "1..7".

This is the line:

% perl -Iblib/lib t/boilerplate.t

Change to:

% perl -Iblib/lib -T t/boilerplate.t

This is the code example:

% ./Build
% perl -Iblib/lib -T t/00-load.t
1..4
ok 1 - use Animal;
ok 2 - use Cow;
ok 3 - use Sheep;
ok 4 - use Horse;

Change to:

% ./Build
% perl -Iblib/lib -T t/00-load.t
1..5
ok 1 - use Animal;
ok 2 - use Cow;
ok 3 - use Sheep;
ok 4 - use Horse;
ok 5 - use Mouse;

Note from the Author or Editor:
Change as noted, adding that last line

Change "procedes" to "proceeds".

This is the line:

Person->speak("Hello, world!");

In order to match the exercise description and the sample output, change to:

Person->speak("Hello, World!");

This is the line:

% module-starter --module=Cow,Horse,Sheep --dist=.

Change to:

% module-starter --module=Cow,Horse,Sheep,Mouse --dist=.

Note from the Author or Editor:
Change as noted

This is the line:

% module-starter --module=Animal,Cow,Horse,Sheep

Change to:

% module-starter --module=Animal,Cow,Horse,Sheep,Mouse

Note from the Author or Editor:
Change as noted

This is the line:

use parent qw(Cow);

Change to:

use parent qw(Animal);

Note from the Author or Editor:
Change as noted

This is the line:

$class->Animal::speak(@_); # tell it where to start

Since this code example is supposed to represent the best practices so far, change to:

$class->SUPER::speak(@_); # tell it where to start

Note from the Author or Editor:
Change as noted

This is the code example:

package Cow;
use parent qw(Cow);
sub sound { 'neigh' }
1;

To be consistent with previous examples in the chapter, change 'neigh' to 'moooo'.

Note from the Author or Editor:
Change as noted

Change "We override a the method" to "We override the method".

This is the line:

% module-starter --module=Cow,Horse,Sheep

Since we are adding modules to an existing distribution, the --dist argument should be specified as follows:

% module-starter --module=Cow,Horse,Sheep --dist=.

Note from the Author or Editor:
Change as noted

This is the line:

% module-starter --module=Animal --name=Gilligan --email="gilligan@example.net"

Change "--name" to "--author". Since we are creating a distribution with Build.PL, the "--mb" switch should also be specified.

Note from the Author or Editor:
Change line to

% module-starter --module=Animal --author=Gilligan --email="gilligan@example.net" --mb

This is the line:

% module-starter --builder="ExtUtils::Makemaker" --name="Animal"

Change "--name" to "--module". Author and email should also be specified.

Note from the Author or Editor:
Change to

% module-starter --builder="ExtUtils::Makemaker" --module="Animal"

This is the line:

% module-starter --mb --name="Animal"

Change "--name" to "--module". Author and email should also be specified.

Note from the Author or Editor:
Change as noted

Change "the MANIFEST files helps" to "the MANIFEST file helps".

This is the sentence:

"The =headn directories specify a heading."

The word "directories" does not seem to fit in this sentence. I think the intended word was "directives".

Note from the Author or Editor:
Change "directories" to "directives"

Change "header" to "heading".

Change "The Module::Starter::AddModule can do the job" to "Module::Starter::AddModule can do the job".

Change "created" to "create".

Remove "which" from "but which we have to install it".

Change "files that contains" to "files that contain".

Change "all of the test" to "all of the tests".

Change "distribution" to "distributions".

This is the sentence:

"Most programs leave the package at the default main package."

Change "at" to "as".

Change "tracked" to "track".

This is the line:

dump_data_for_path( $_, $data->{$_}, $indent + 1 );

Change to:

dump_data_for_path( $_, $data->{$_}, $level + 1 );

Note from the Author or Editor:
Change $indent to $level

This is the line:

my $path = shift || 0;

Change to:

my $level = shift || 0;

This code example also generates the warning mentioned in the errata for page 154:

"Parentheses missing around "my" list at ./test.pl line 27."

One workaround is to put parentheses around the first lexical variable in the opendir statement:

opendir my ($dh), $path;

Note from the Author or Editor:
Change as noted

This code example generates the following warning:

"Parentheses missing around "my" list at ./test.pl line 27."

The line of code responsible for the warning is:

opendir my $dh, $path;

One workaround is to put parentheses around the first lexical variable:

opendir my ($dh), $path;

Note from the Author or Editor:
Change as noted to avoid the warning

Change "Somes" to "Some".

Note from the Author or Editor:
Change as noted

This is the line:

while( <DATA> ) {

To be consistent with the previous examples, change to:

while( <> ) {

Note from the Author or Editor:
Change as noted

This is the line:

print if /$RE{URL}{HTTP}/;

Change to:

print if /$RE{URI}{HTTP}/;

Note from the Author or Editor:
Change as noted

The return statement should be indented.

Note from the Author or Editor:
Change as noted

Change "allow" to "allows".

Note from the Author or Editor:
Change as noted

"flags that affect the pattern and flags that affected the operator"

should probably be

"flags that affect the pattern and flags that affect the operator"

Note from the Author or Editor:
Change as noted

This paragraph shows "end of string" written both with and without hyphens. For consistency, the text should use one form throughout.

Note from the Author or Editor:
Use hyphens in both cases since they are adjectives.

Change "Fred" to "Gilligan".

Note from the Author or Editor:
Change as noted

This is the sentence:

"Use a hash keyed by castaway name and whose values are IO::File objects for each output file."

Instead of using IO::File, the solution presented on page 325 uses open.

Note from the Author or Editor:
Change to

Hint: Use a hash keyed by castaway name and whose values are filehandle references for each output file.

Change "read from the output from a command" to "read the output of a command".

Note from the Author or Editor:
Change as noted

Change "hands" to "handles".

Note from the Author or Editor:
Change as noted

This code example would be more appropriate if $string_log contained some lines of text.

Note from the Author or Editor:
Change to

my $string_log = '...'; # assume many lines

Change "preface" to "the introduction".

Note from the Author or Editor:
Change as noted

This line of code should be indented at the same level as the previous line. In other words:

require Data::Dumper;
local $Data::Dumper::Terse = 1;

should be

require Data::Dumper;
local $Data::Dumper::Terse = 1;

Note from the Author or Editor:
undent that line as noted.

The code returned by coderef2text is not consistent between the code examples. For instance, on pages 109 and 110, the outputs contain:

use warnings;
use strict;
no feature;
use feature ':5.16';

But on pages 110 to 112, the outputs contain:

use warnings;
use strict 'refs';
BEGIN {
$^H{'feature_unicode'} = q(1);
$^H{'feature_say'} = q(1);
$^H{'feature_state'} = q(1);
$^H{'feature_switch'} = q(1);
}

I was able to duplicate both these outputs depending on the version of my Perl installation. The book should probably choose one of them for all the examples.

Note from the Author or Editor:
It looks like I ran those examples with different versions of Perl. I've made then the first version.

The closing curly brace is not properly aligned. It should be indented at the same level as the line that follows.

Note from the Author or Editor:
Add a single space before that brace

Change "referenced by subroutine" to "referenced by the subroutine".

Note from the Author or Editor:
Change as noted

Change "create_find_callback_that_counts" to "create_find_callbacks_that_sum_the_size".

Note from the Author or Editor:
This is at the end of the paragraph that starts "Distinguishing ..."

Change "we can the string form of eval" to "we can use the string form of eval".

Note from the Author or Editor:
Change as noted

In the PeGS diagram, change "gillign.crew.hut" to "gilligan.crew.hut".

Note from the Author or Editor:
Change as noted

In the PeGS diagram, change "$ginger" to "@ginger".

Note from the Author or Editor:
Change as noted

Change "$SIG{_ _WARN_ _}" to "$SIG{__WARN__}".

Note from the Author or Editor:
The __ together looks as unclear in print unless we separate them by a hair space so they look like two characters. Either way there's a typography problem.

This is the line:

print "Country code: " . $isbn->country_code . "\n";

In order to match the exercise description on page 24, change to the following:

print "Group code: " . $isbn->group_code . "\n";

Note from the Author or Editor:
The interface for Business::ISBN changed.

Change "the Perl" to "Perl".

Note from the Author or Editor:
In the note on that page, change as noted.

Change "Skipper" to "the Skipper".

Note from the Author or Editor:
Change as noted.

Change "Set::Crossproduct" to "Set::CrossProduct".

Change "$_" to "$file".

Change "foo" to "perlstuff".

Note from the Author or Editor:
This is the line


export PERL5LIB="/Users/Ginger/foo/lib/perl5/darwin&#8722;2level:/Users/Ginger/perlstuff/lib/perl5";

Change that to


export PERL5LIB="/Users/Ginger/perlstuff/lib/perl5/darwin&#8722;2level:/Users/Ginger/perlstuff/lib/perl5";

Change "/home/gilligan/lib/" to "/Users/gilligan/lib/".

Note from the Author or Editor:
Change as noted

Module::CoreList->first_release('Module::Build'); # 5.009004

should be

print Module::CoreList->first_release('Module::Build'); # 5.009004

Note from the Author or Editor:
Change as noted

"Some distributions, such as Strawberry Perl (...) or ActivePerl (...), add extra modules to its distribution."

should be

"Some distributions, such as Strawberry Perl (...) and ActivePerl (...), add extra modules to their distributions."

or the following (to avoid repeating the word "distributions")

"Some distributions, such as Strawberry Perl (...) and ActivePerl (...), include extra modules."

Note from the Author or Editor:
Change as noted

Change "feature" to "features".

"with which version of perl first included them"

should maybe be something like

"with which version of perl they were first included"

Note from the Author or Editor:
change to "which version of perl first included them", striking the "with"

Change "that" to "what".

Note from the Author or Editor:
Change to "which"

The first sentence says "to find and update when we need to move the file needs to a new..." The word "needs" should be removed.

Note from the Author or Editor:
Change to "This makes it easier to find and to update it when we need to move the file to a new system"

The sentence that starts "If we have the a recent version of Perl, should also...". Remove "the" from the sentence and add "we" before "should".

Note from the Author or Editor:
That should be "If we have a recent version of Perl, we should"

The sentence is a statement, not an inquiry, and should end with a period instead of a question mark.

Note from the Author or Editor:
This is the sentence "However, suppose we already had a dirname subroutine?" Change that to a full stop at the end.

Last sentence of the paragraph:

"Thus, the grep checks each required item against the list."

Is "grep" correct in this sentence?. I don't see the "grep" function used anywhere on this page.

Note from the Author or Editor:
Remove the sentence "Thus, the grep checks each required item against the list." This is left over from the example in the previous edition.

The sentence starts "We?ve included on the top portion..." The word "on" should be "only".

Note from the Author or Editor:
Changed as noted in r546856.