Answer.

History of the question:

The while loop is one of the basic control structures in Perl, used since the beginning for processing data, reading files, and iterating over collections. It is closely integrated with the special variable $_, which by default takes values when reading lines from a file or during other iterations.

Problem:

Incorrect use of the variable $_, reading files without explicit filehandles, and improper termination of loops can lead to errors in string processing and data loss. Automatic handling by default using $_ increases flexibility, but requires care when writing code, especially with nesting and modifying the string within the loop.

Solution:

For reading files, the expression

while (<FILEHANDLE>) {
    # ...
}

or even just while (<>) for reading from the input stream or list of files passed to the script is commonly used. Inside such a loop, Perl automatically places the read line into $_, allowing succinct use of regular expressions, substitutions, and other operations. If a variable needs to be explicitly defined, the construct while (my $line = <FILEHANDLE>) is used.

Example code:

open my $fh, '<', 'file.txt' or die $!;
while (<$fh>) {
    chomp;                # works with $_
    print "Line: $_
";
}
close $fh;

Key features:

Automatic handling of the variable $_ within the loop body
Reading lines from files or STDIN using the <> operator
Ability to concisely process data without explicitly specifying variables

Trick questions.

What happens if you modify $_ inside the while loop?

Changing $_ within the loop does not affect the file being read, but only the value of the variable within a single iteration. However, reusing $_ can be confusing if working with multiple data sources simultaneously.

What happens if you use while (<>) without opening a file first?

The <> operator without explicitly opening a file reads either from STDIN or from files specified in @ARGV when launching the script. If nothing is specified, it waits for input from the keyboard.

Is it necessary to use chomp inside while to remove \n?

No, it is not necessary, but without chomp, each line will contain a newline character \n. This often leads to unexpected results (such as double newlines when printing).

Common mistakes and anti-patterns

Not using chomp when needed
Overriding $_ in nested loops without saving the previous value
Using while (<>), not considering the absence of input data

Real-life example

** Negative case

In a script parsing logs, forgetting to add chomp inside while (<FILE>) led to extra newline characters during console output.

Pros:

Quick implementation

Cons:

Incorrect output formatting

** Positive case

The developer always uses clear variable declaration with my $line = <$fh> and chomp immediately after reading the line.