Scalar and List Context: One Value or Many

Part I · Module 2 · Chapter 2.9 · Scalar and List Context: One Value or Many

1. The Idea

Chapter 2.6 established a rule in miniature: the operator decides whether a value is read as a number or as text. Perl applies the same philosophy to a much bigger question.

Before evaluating any expression, Perl works out what the surrounding code is asking for:

• Scalar context — the surroundings want one value.
• List context — the surroundings want a list of values.

The expression is then evaluated in that context, and many expressions answer the two questions differently. Not slightly differently: they can return completely unrelated things.

This is unusual. In most languages an expression means one thing and the surroundings take it or leave it. In Perl the surroundings ask first.

2. A Note on the Example

Demonstrating this needs something that answers the two questions differently, and the clearest such thing is an array. Chapter 2.1 introduced @ as the sigil for a list of values, which is all you need.

Arrays are Module 5, and this chapter does not teach them. The array below is created with a literal list and then used only as a subject — nothing is indexed, added, sorted or looped over. If you can read my @marks = (72, 65, 90); as "three numbers, in order", you have everything required.

3. Two Assignments, One Difference

use strict;
use warnings;

my @marks = (72, 65, 90);

my $how_many = @marks;
my ($first)  = @marks;

print "how many: $how_many\n";
print "first:    $first\n";

how many: 3
first:    72

Lines 6 and 7 differ by one pair of parentheses, and they produce 3 and 72.

• my $how_many = @marks; — the left side is a single scalar, so this is scalar context. Asked for one value, an array reports how many elements it has: 3.
• my ($first) = @marks; — the parentheses on the left make it a list assignment, so this is list context. Asked for a list, the array hands over its elements; the list on the left has one slot, so it takes the first and the rest are discarded: 72.

Nothing about @marks changed between the two lines. The same expression was asked two different questions and gave two correct answers.

4. How to Tell Which Context You Are In

You do not have to guess. The context is decided by the surroundings, and the surroundings are visible in the line you are reading. A few reliable signals:

The first two rows are the ones to internalise, because the difference between them is two characters and it is the most common source of confusion in this area.

The print row explains something you have already seen. Interpolating an array into a string gives its elements, not its count:

use strict;
use warnings;

my @marks = (72, 65, 90);

print "elements: @marks\n";
print "count:    ", scalar(@marks), "\n";

elements: 72 65 90
count:    3

A reader expecting 3 from the first line is applying the wrong context. A string being built is assembling a list of things to include, so the array supplies its elements.

5. Why It Is Worth the Effort

Context looks like a complication and is better understood as a compression. Because the surroundings already say what is wanted, Perl does not need separate names for "the count of" and "the elements of" — the same expression serves both, and the line you wrote says which you meant.

Once you can see it, three things stop being arbitrary:

• Why if (@failures) means "if anything failed". It is a truth test, which wants one value, so the array gives its count — and a count of zero is false, exactly as Chapter 2.8 described.
• Why a function can return a count in one line and a list in another. Chapter 10.6 is about that, and it is the same mechanism.
• Why the parentheses in my ($first) = ... are load-bearing rather than decorative.

That is why this chapter is marked critical. It is not a feature to use; it is the thing you need in order to read Perl.

6. Why This Matters in Engineering Work

Context is the most common cause of a Perl line that looks obviously correct and is quietly wrong, and the shape is always the same: the author wanted a count and wrote a line that asked for a list, or the reverse.

The concrete version you will meet in Part II: a script gathers the failing tests, then reports how many there were. If the gathering produces a list and the report asks for one value, the count appears. If a later edit adds parentheses — perhaps while making the line look like its neighbours — the same line starts yielding the first failing test instead, which is a string, and the report says alu_smoke where it used to say 7. Nothing warns, because both lines are valid and both produce a plausible value.

The defence is to read the destination before the source. What is on the left tells you what the right-hand side will produce, and in a code review that is the half people skip.

7. Common Mistakes

Expecting an interpolated array to give its count. "@marks" yields the elements. Use scalar(@marks) when you want the number, which is Chapter 2.10's subject.

Writing my ($x) = ... when you meant my $x = .... Two characters, a completely different result: the first element instead of the count. This is the single most common context error.

Assuming context is a property of the expression. It is a property of the surroundings. The same @marks yields different things on adjacent lines, as §3 showed.

Thinking context is about types. It is about how many values are wanted. A scalar context does not ask for "a number"; it asks for one value, which may be a count, a string, or anything else.

Trying to memorise every context rule at once. Learn the two assignment forms and print. The rest you will recognise as you meet it, and perldoc perldata — Chapter 1.14 — is where the complete account lives.

8. What You Should Be Able to Say Now

1. Perl decides, before evaluating an expression, whether the surroundings want one value or a list.
2. Those two situations are called scalar context and list context.
3. An array in scalar context yields its element count; in list context it yields its elements.
4. my $x = @a is scalar context; my ($x) = @a is list context. The parentheses are the whole difference.
5. Interpolating an array into a string is list context, so you get the elements.
6. Context is a property of the surroundings, not of the expression.
7. Reading the destination first is how you predict what an expression will produce.

9. Exercise

Exercise 1 — run the two forms. Create context.pl from §3 and run it. Then swap the two left-hand sides so that $how_many is written with parentheses and $first without, predict the output before running, and check.

Exercise 2 — predict four lines. Given my @tests = ("alu_smoke", "fifo_basic", "arb_fair");, write down what each prints before running any of them:

my $a = @tests;
my ($b) = @tests;
print "@tests\n";
print scalar(@tests), "\n";

Exercise 3 — explain a truth test. Chapter 2.8 said if (@failures) means "if anything failed". Explain, using this chapter's vocabulary, which context that is and why an empty array makes the test false.

Exercise 4 — review a change. A colleague edits a working line from my $count = @failures; to my ($count) = @failures; while tidying up. The script still runs and still prints a value. Describe what the reported number becomes, why nothing warns, and what you would say in the code review.

10. Summary

• Perl asks the surroundings first: does this position want one value, or a list?
• Those are scalar context and list context, and many expressions answer them differently.
• An array gives its count in scalar context and its elements in list context.
• my $x = @a and my ($x) = @a differ by two characters and by what they produce.
• A string being built is list context, which is why an interpolated array shows its elements.
• Context belongs to the surroundings, so the same expression can mean different things on adjacent lines.
• Read the destination before the source — it is what tells you which question is being asked.

Chapter 2.10 turns this from something you have to detect into something you can state: the three short forms that force the context you meant, so a reader never has to work it out.