comment on

Sounds like you are missing a C compiler. Get a copy of the latest free MS C compiler (involves installing tons of crap) or get your company to buy one. Either way the amount of money you save by being able to build open source on your MS box will quickly recoup the cost of the compiler.

Er, the above is assuming that binary interoperability with MS is important, if it isnt then use cygwin perl and cygwin gcc. OTOH, a native compiler will probably result in a faster executables overall. (With some exceptions, AS'es Perl isnt optimal with respect to certain memory operations, especially realloc.)

---
demerphq

In reply to Re^5: XSLT processing huge XMLs by demerphq
in thread XSLT processing huge XMLs by Anonymous Monk

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.


"be consistent"
	PerlMonks