|
in reply to Re: A Semi-automatic word search solver
in thread A Semi-automatic word search solver
Thanks for the subroutine, I think I will use that as part of the update I'm planning. As for using a prototype on the subroutine, I've always done it that way, but if this is considered incorrect or foolish, please do tell me. |
Re^3: A Semi-automatic word search solver
by CountZero (Bishop) on Sep 26, 2009 at 19:34 UTC
|
Prototypes in Perl are very special. They are not --as many people expect-- a tool to check at compile-time or even run-time wether the parameters of your subroutine call are correct. Have a look at Gratuitous use of Perl Prototypes, it explains clearly why Perl "prototypes" are totally different from (for example) C "prototypes".
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
| [reply] |
|
|
Thanks, that does clear it up for me, coming from a C(++) background prototyping had just become a default behaviour like putting #!/usr/bin/perl at the top of every bit of perl code has.
| [reply] |
|
