Re: Passing variables into a subroutine

Your prototype definition is wrong. Your definition of (@) says that your sub takes one array or list as argument, so all arguments are flattened into one list. This is the way any "normal" subroutine without prototypes works.

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]

And its output:

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 @_.

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

Comment on Re: Passing variables into a subroutine Select or Download Code

Replies are listed 'Best First'.
Re^2: Passing variables into a subroutine by Freezer (Sexton) on Sep 04, 2012 at 10:26 UTC
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?	[reply]
Re^3: Passing variables into a subroutine by CountZero (Bishop) on Sep 04, 2012 at 16:24 UTC
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	[reply] [d/l]
Re^2: Passing variables into a subroutine by Freezer (Sexton) on Sep 04, 2012 at 10:29 UTC
Is something like the following equally cool? `sub look_through_file ($$) { my ($start_point, $continue_tag) = @_;` [download]	[reply] [d/l]
Re^3: Passing variables into a subroutine by CountZero (Bishop) on Sep 04, 2012 at 16:29 UTC
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	[reply] [d/l] [select]


Welcome to the Monastery
	PerlMonks