I've never had a serious problem developing on Windows and deploying to *nix. Just avoid using platform specific modules (especially the Activestate Win32::* ones) and making calls to external utilities and commands. If you must do "platform specific" stuff, eg forking, use "require" in an eval and test for the OS type. Installing cygwin makes life a lot easier if you have to make external calls (in my case for re-encoding music) but there are still differences between how a shell call is executed in *nix and cygwin, though obviously not as severe as shell and cmd.
Getting the case right for your module names is something that *nix is very picky about, and one of the main causes of frustration when migrating from a Win32 dev platform.
For a bit of fun why not make your database Access or SQL Server on Windows and PostgreSQL or MySQL on *nix? :)
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.