Prototypes alter how a function call is parsed, but need to do so at compile time. So the interpretation of the function call depends on whether List::BinarySearch has already been loaded or not at the time your call to it is compiled.
Because you don't know whether or not List::BinarySearch, it is safer to avoid the issue by bypassing prototypes (which is what the & does).
In reply to Re^3: List::BinarySearch and conditional tests with Test::More
by tobyink
in thread List::BinarySearch and conditional tests with Test::More
by glasswalk3r
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |