|Think about Loose Coupling|
Re^2: Use reference for functions in functionsby 7stud (Deacon)
|on Feb 26, 2013 at 01:03 UTC||Need Help??|
In addition to the problems pointed out by BrowserUk and 7stud,
Nope. You win.
Problems with Reference Prototypes At some level, they're more predictable...But I'm afraid that these, too, may often be more trouble than they're worth. You see ... (\$) (\@) (\%) ... don't actually say that you must pass in a scalar reference, an array reference, and a hash reference. Rather, they say you must pass in a scalar variable, an array variable, and a hash variable. That means that the compiler insists upon seeing a properly notated variable of the given type, complete with ``$'', ``@'', or ``%'' in that slot ['slot' means the corresponding position in the argument list when you call the subroutine.] You must not use a backslash. The compiler silently supplies the backslash for you.
So given this sub:
...you can call the sub like this:
But the prototype prevents you from calling the sub like this:
But the prototype doesn't stop you from doing this:
...and then you end up with unintended consequences.