Answer.

Perl is a unique language where most expressions and functions change their behavior depending on the context: scalar, list, or void. Historically, this mechanism was introduced to enhance the flexibility of data handling and the conciseness of the code.

Problem: Many beginner developers do not realize that the same functions return different values and behave unexpectedly when the context changes, leading to data processing errors.

Solution: It is important to understand how Perl defines context and to use the wantarray function and explicit data casting to avoid issues.

Code example:

my @lines = grep {/error/} @log;       # List of matching lines (list context)
my $count = grep {/error/} @log;        # Number of matching lines (scalar context)

Key features:

Context is determined by the location of the expression call.
Operators and functions may behave differently in different contexts.
The wantarray operator is used to control the returned values from functions.

Trick questions.

Can a function always be used in any context and expect a correct result?

No. For example, the reverse function returns a string in scalar context and a list in list context. An incorrect context may lead to unexpected results.

Code example:

my $str = reverse('abc'); # "cba"
my @arr = reverse('abc'); # ('abc') — result NOT what a beginner expects

What does a function return in void context?

In void context, the result is ignored. Some functions may optimize and not perform unnecessary work. For example,

reverse(@array); # Does not affect the array, result is lost

What is the difference between list context and scalar context for the localtime function?

In list context, localtime returns a list of time parts, and in scalar context, it returns a time string.

my $now_str = localtime();      # 'Tue Apr 16 13:00:00 2024'
my ($sec,$min,$hour) = localtime(); # (0, 0, 13)

Typical errors and anti-patterns

Implicit use of functions in the wrong context.
Expecting a single return type when the function behaves otherwise.
Overwriting variables in different contexts.

Real-life example

Negative case

A developer writes a function to search for strings and expects to get a count of matches, but uses it in list context and receives an array of strings.

Pros:

Immediately gets the content of matching strings.

Cons:

Error when passing to another function that expects a scalar — behaves differently than intended.

Positive case

A developer explicitly specifies the expected context, uses wantarray in functions, tests both variants of function operation.