... the argument in PPP is much stronger, the warning is issued at compile-time !!!
My PBP (1st English ed., printed July 2005, which seems from the O'Reilly website info to be the latest English edition and printing) does say (pg. 183, 2nd para.) "... will be reported ( usually at compile time) in the caller's context ...", but I don't see how this is so. (I have also checked the on-line errata list and there is no correction of this statement.)
Certainly the malformed function call
func_1({ one => 'uno', two => 'dos', three => });
from my example code in Re: Preferred technique for named subroutine parameters? does compile and only warns at run time.
Can you give an example of a compile time error associated with this invocation format, or any explanation or example of what Conway was referring to?
But a run-time-error can happen years after you wrote and sold the code ...
True, but if it does happen years after I wrote and sold the code, cashed the check, spent the money and moved to another state ...
Update: "edition" -> "edition and printing" in para. 1.
-
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.
|
