Answer

In Perl, objects are typically references to hashes, and "slots" are individual fields of the hash that store the object's data. To save on code and dynamically create methods, the magical method AUTOLOAD is often used.

AUTOLOAD allows intercepting calls to non-existent methods and dynamically implementing them "on-the-fly". For example, auto-generating getter and setter methods:

package MyObj;
sub new { bless { foo => 1, bar => 2 }, shift }

our $AUTOLOAD;
sub AUTOLOAD {
    my ($self) = @_;
    my $field = $AUTOLOAD =~ s/.*:://r;
    die "No such slot $field" unless exists $self->{$field};
    return $self->{$field};
}

my $obj = MyObj->new;
print $obj->foo;  # 1

Dangers:

• Errors are not caught at compile time but only at runtime.
• Uncontrolled dynamic method creation may occur (autolambda).
• Typos in method names are even intercepted, complicating error detection.

Trick question

What is the difference between AUTOLOAD and directly defining a method? What are the downsides of using AUTOLOAD for all class accessors?

Answer: AUTOLOAD works at runtime, unlike explicit methods. Typically, errors related to incorrect method names surface only during execution, not at compile time, which complicates debugging. Example of misuse:

$obj->fop; # instead of foo — will not lead to a compile error, will hit AUTOLOAD

It's better to explicitly generate methods through eval in the compile section.

Examples of real errors due to ignorance of the nuances of the topic

---

Story

In a web application framework, all getter methods were implemented through AUTOLOAD to reduce duplication. Some programmers made typos in method names that did not trigger an error during compilation or runtime but simply returned undef, leading to incorrect business logic behavior.

Story

A project with a large number of dynamic accessor methods grew to such an extent that AUTOLOAD became a "bottleneck": performance dropped significantly due to frequent calls to AUTOLOAD and memory consumption for creating code references "on-the-fly".

Story

In a library for object serialization, methods were auto-generated through AUTOLOAD, but a special DESTROY was forgotten, resulting in AUTOLOAD being triggered when deleting objects, leading to errors about the missing DESTROY method and memory leaks.