Note, however, that (unlike most other OO languages) Perl does not
ensure or enforce encapsulation in any way. If you want objects to
actually I<be> opaque you need to arrange for that yourself. This can
-be done in a varierty of ways, including using L<"Inside-Out objects">
+be done in a variety of ways, including using L</"Inside-Out objects">
or modules from CPAN.
=head3 Objects Are Blessed; Variables Are Not
my $bar = $foo;
bless $foo, 'Class';
- print blessed( $bar ); # prints "Class"
+ print blessed( $bar ) // 'not blessed'; # prints "Class"
$bar = "some other value";
- print blessed( $bar ); # prints undef
+ print blessed( $bar ) // 'not blessed'; # prints "not blessed"
When we call C<bless> on a variable, we are actually blessing the
underlying data structure that the variable refers to. We are not
contains a list of that class's parent classes, if any. This array is
examined when Perl does method resolution, which we will cover later.
-It is possible to manually set C<@ISA>, and you may see this in older
-Perl code. Much older code also uses the L<base> pragma. For new code,
-we recommend that you use the L<parent> pragma to declare your parents.
-This pragma will take care of setting C<@ISA>. It will also load the
-parent classes and make sure that the package doesn't inherit from
-itself.
+Calling methods from a package means it must be loaded, of course, so
+you will often want to load a module and add it to C<@ISA> at the same
+time. You can do so in a single step using the L<parent> pragma.
+(In older code you may encounter the L<base> pragma, which is nowadays
+discouraged except when you have to work with the equally discouraged
+L<fields> pragma.)
However the parent classes are set, the package's C<@ISA> variable will
contain a list of those parents. This is simply a list of scalars, each
my $pod = File->new( 'perlobj.pod', $data );
$pod->save();
-The C<< -> >> syntax is also used when dereferencing a reference. It
+The C<< -> >> syntax is also used when dereferencing a reference. It
looks like the same operator, but these are two different operations.
When you call a method, the thing on the left side of the arrow is
itself. Remember, under the hood, this object is still just a hash.
Later, we'll write accessors to manipulate this data.
-For our File::MP3 class, we can check to make sure that the path we're
-given ends with ".mp3":
+For our C<File::MP3> class, we can check to make sure that the path
+we're given ends with ".mp3":
package File::MP3;
Perl supports several other ways to call methods besides the C<<
$object->method() >> usage we've seen so far.
+=head3 Method Names with a Fully Qualified Name
+
+Perl allows you to call methods using their fully qualified name (the
+package and method name):
+
+ my $mp3 = File::MP3->new( 'Regin.mp3', $data );
+ $mp3->File::save();
+
+When you a fully qualified method name like C<File::save>, the method
+resolution search for the C<save> method starts in the C<File> class,
+skipping any C<save> method the C<File::MP3> class may have defined. It
+still searches the C<File> class's parents if necessary.
+
+While this feature is most commonly used to explicitly call methods
+inherited from an ancestor class, there is no technical restriction
+that enforces this:
+
+ my $obj = Tree->new();
+ $obj->Dog::bark();
+
+This calls the C<bark> method from class C<Dog> on an object of class
+C<Tree>, even if the two classes are completely unrelated. Use this
+with great care.
+
+The C<SUPER> pseudo-class that was described earlier is I<not> the same
+as calling a method with a fully-qualified name. See the earlier
+L</Inheritance> section for details.
+
=head3 Method Names as Strings
Perl lets you use a scalar variable containing a string as a method
$object->$meth();
}
-=head3 Deferencing Method Call
+=head3 Dereferencing Method Call
Perl also lets you use a dereferenced scalar reference in a method
call. That's a mouthful, so let's look at some code:
=head3 Indirect Object Syntax
X<indirect object>
-B<Outside of the file handle case, use of this syntax is discouraged
-as it can confuse the Perl interpreter. See below for more details.>
+B<Outside of the file handle case, use of this syntax is discouraged as
+it can confuse the Perl interpreter. See below for more details.>
-Perl suports another method invocation syntax called "indirect object"
+Perl supports another method invocation syntax called "indirect object"
notation. This syntax is called "indirect" because the method comes
before the object it is being invoked on.
Without the C<our $AUTOLOAD> declaration, this code will not compile
under the L<strict> pragma.
-As the comment says, this is not a good way to implement accessors.
+As the comment says, this is not a good way to implement accessors.
It's slow and too clever by far. However, you may see this as a way to
provide accessors in older Perl code. See L<perlootut> for
recommendations on OO coding in Perl.
If your C<DESTROY> method issues a warning during global destruction,
the Perl interpreter will append the string " during global
-destruction" the warning.
+destruction" to the warning.
During global destruction, Perl will always garbage collect objects
before unblessed references. See L<perlhacktips/PERL_DESTRUCT_LEVEL>
https://perl5.git.perl.org / perl5.git / blobdiff