comment on

I've never worked in a place were there was the smallest chance one of my Perl programs needed to be ported to Windows or any other non-Unix platform.

However, I've written large shell scripts on Solaris that needed to be ported to both Windows NT and to HP-UX. The port to Windows was *trivial*. One directory needed to be renamed, and we installed a Unix tools package on Windows (I think it was MKS). Porting to HP-UX was actually more work.

Generally, I don't give a rats ass whether my programs can be easily ported to Windows or not. If you want to cripple yourself running on that platform, be my guest. Don't expect any pity or help from me.

I'm a toolsmith. I write tools, usually highly specialized tools. Needing to do one particular job, on a particular platform. Portability to non-Unix platforms usually is a non-issue. Besides, there are Unix toolkits for non-Unix systems available. Install them, and your platform will become better.

Abigail

In reply to Re: "Native Perlish" by Abigail-II
in thread "Native Perlish" by spurperl

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.


Welcome to the Monastery
	PerlMonks