However now consider this:

use Modern::Perl;

sub create_output (\@$) {
    my ($arrayref_of_lines, $entry_no_new) = @_;
    say "array:  @{$arrayref_of_lines}";
    say "scalar: $entry_no_new";
}
my @array = qw/1 2 3 4/;
create_output @array, 5;
[download]

array:  1 2 3 4
scalar: 5
[download]

This is actually one of the few cases of a prototype being applied in a useful way.

The prototype (\@$) means the first argument to your sub MUST start with a @ (in other words, it must be an array), followed by a scalar. Due to the (\@) in the prototype, Perl actually takes a reference to the array and passes that as the first argument to your sub. So don't you forget to de-reference it in your sub!

It is this automagical referencing that allows you to pass one or more arrays to a subroutine without them all getting flattened in one big @_.

Perl actually takes a reference to the array and passes that as the first argument to your sub. So don't you forget to de-reference it in your sub!



Is there a popper way to do the dereferencing, given the context?

Sadly, there will be no automatic dereferencing done by Perl. But it is very easy to do: to get the original array, just add the @ sigil to the front of the scalar holding the reference.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

Is something like the following equally cool?

sub look_through_file ($$) {   
    
    my ($start_point, $continue_tag) = @_;
[download]

As a general rule don't use prototypes unless there is a good reason for it such as passing in several arrays without them getting flattened into one @_. And even then passing references to the arrays is probably a more clear solution.

I see no merit in adding a prototype definition of ($$).

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

my (@array, ...) = ...
[download]

Update: Other problems may emerge after solving this one because of the usage of prototypes.

sub create_output {                    # no prototype
    my ($lines, $entry_no_new) = @_;   # $lines is arrayref
[download]

See The purpose of prototypes in perl subroutines, The Problem with Prototypes, Why are Perl 5's function prototypes bad?, Prototype

You don't tell us how it fails for you (besides the obvious syntax error).

Perl flattens passed parameters into @_. perlsub explains some more of that.

The other alternative, if you don't want to deal with references and if there is only one array (or hash) to be passed, is to pass any and all scalars (and there can be more than one) first, and then pass the sole array (or hash). The following works the same way with or without the  (@) prototype for the reason explained by CountZero (i.e., in general, don't bother with prototypes):

perl -wMstrict -le
"sub S {
   my ($scalar, @ra) = @_;
   ;;
   print qq{scalar: '$scalar'  array:(@ra)};
   }
 ;;
 my @array = (1, 2, 3);
 S('foo', @array);
"
scalar: 'foo'  array:(1 2 3)
[download]

my $entry_no_new   = pop @_;
my @array_of_lines = @_;
[download]

my @array_of_lines = @_;
my $entry_no_new   = pop @array_of_lines;
[download]