You are entirely correct. I had missed the line stating its limitation to MySQL and Postgres -- I confess I didn't read the entire POD through. In my defense, I did look -- but I was looking for a BUGS or LIMITATIONS type of section, and the limitation is listed in the DESCRIPTION section.
Win32 support in Perl is nothing short of incredible. When I was able to follow *identical* directions (from perlxstut) on Windows and Linux to flawlessly produce an XS module from h2xs, I nearly fell out of my chair.
And, yes, I am in the minority. But it just grates me when something won't work because they did something like use `pwd` instead of use Cwd, or something depends on a case-sensitive filesystem (there was another meditation on that recently).
However, I wonder I would have been spared the IO::Zlib trouble I suffered on any other OS...
--Stevie-O
$"=$,,$_=q>|\p4<6 8p<M/_|<('=>
.q>.<4-KI<l|2$<6%s!<qn#F<>;$,
.=pack'N*',"@{[unpack'C*',$_]
}"for split/</;$_=$,,y[A-Z a-z]
{}cd;print lc
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.