Re^2: Passing variables into a subroutine

Is something like the following equally cool?


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

Comment on Re^2: Passing variables into a subroutine Download Code

Replies are listed 'Best First'.
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]

Replies are listed 'Best First'.

Re^3: Passing variables into a subroutine
by CountZero (Bishop) on Sep 04, 2012 at 16:29 UTC

don't use prototypes

@_

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]