Let's face it. The 32-bit Win32 builds have always produce 100 of warnings, even at their best, before they started consting everything in sight.

With the 64-bit builds it must be close to 2,000 warnings? I'll do realclean and count them later.

But can you imagine me submitting a patch that changed *every* source file? And 10s to 100s of lines in each source file.

I might just as well suggest putting the whole codebase through a C-beautifier to sort out the indentation :)

Update: 2106 warnings:

<Reveal this spoiler or all in this thread>

In reply to Re^11: Perl 5.12.0 has been released! (exetype problem 64-bit) by BrowserUk
in thread Perl 5.12.0 has been released! by ikegami

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.