In general, it's the other way round you need to worry about more: perl on Windows lacks a number of functions that work on Unix (alarm, chroot, etc). However, the most important things to consider in making a script written on Windows work on Unix are when you interact with the system, either directly (using system or backticks), or indirectly (when manipulating files). Some general guidelines:
- Avoid system unless you want the user to have to install Unxutils or similar.
- Be careful with newlines: text files end in CRLF under Windows, but just LF under Unix.
- Use File::Spec, File::Temp and friends to construct paths and filenames portably.
- Know that unlink doesn't necessarily delete a file completely under Unix.
- Don't use Win32 modules, for obvious reasons.
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.