comment on

moritz already demonstrated how precedence might break.

Further, context might break. (Update: And tye said so already, while I was writing this. Eh.)

Given those prototypes, files_identical( foo(), bar() ) currently means files_identical( scalar(foo()), scalar(bar()) ). Dropping prototypes means putting foo() and bar() in list context instead.

If foo() is (or returns something that is) context sensitive, this may break.

(Likewise, inspection_current( @array ) will, given the prototype, get the number of elements in @array. Without the prototype, it will get the first element. Given that this argument is called $file, this is a rather far-fetched scenario, but should serve to illustrate context sensitivity.)

In this case, the standard wisdom on prototypes may well be trumped by the standard wisdom of legacy code:

If it ain't broke, don't fix it.

print "Just another Perl ${\(trickster and hacker)},"
The Sidhekin proves Sidhe did it!

In reply to Re: Refactoring prototypes - what am I going to break by Sidhekin
in thread Refactoring prototypes - what am I going to break by throop

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Keep It Simple, Stupid
	PerlMonks