... 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.

In reply to Re^3: Preferred technique for named subroutine parameters? by AnomalousMonk
in thread Preferred technique for named subroutine parameters? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.