The file compiles clean ... if you add option -TP to cause the compiler to treat the file as C++ .

Easiest way to achieve that is to start the build process with perl Makefile.PL CC="cl -TP".
For me, that allows Encode-Detect-1.01 to build ok (though I first had to copy the 2 header files that are in the 'include' folder into the 'src' folder). However, I strike runtime problems when running the test suite: 
Can't locate loadable object for module Encode::Detect::Detector

[download]
I haven't the time at the moment to take a look at what's going wrong there. It's the same problem if I build with MinGW (starting with perl Makefile.PL CC="g++").

Cheers,
Rob

In reply to Re^2: Cannot compile Encode::Detect on Windows by syphilis
in thread Cannot compile Encode::Detect on Windows by gvr

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.