Indeed, there were two exactly same places with that incompatibilities between Borland C++ and MSVC++ compilers, and I forgot to mention them earlier. In order to compile, I edited that file in error (zconf.h) in two places just to throw away a couple of lines for Borland compiler some version, so I stepped forward, and that was like a right direction.

Seems to me like "MakeMaker" is to blame here. Although I saw following places:

#if (defined(__BORLANDC__)&&(__BORLANDC__<=0x520)) \
 || (defined(__MINGW32__) && !defined(_ANONYMOUS_UNION))
.......
#endif
[download]

in perl source code distribution, which are essentially same as we faced.

BTW do you wish for me to email my build directory for reference? It's ~1Mb in size.

addition: may be we should prepare compatibility patch for miscellaneous compilers on win32 systems and sent it to author of a module?

Courage, the Cowardly Dog

---

---

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