comment on

Yes, but of the 90% of all deployed machines, over 99.99% will never have a user issueing Perl one-liners.

To do statistics in a meaningful way, the number of deployed machines with a certain shell isn't relevant. You'd have to look at the number of users (where a single person working on N platforms counts as N different users) that issue Perl one-liners. And I'm pretty sure that more than 10% of them run non-Windows shells.

Not to mention that Unix shells have been ported to Windows, and I do know people using Unix shells on Windows (myself included). I've never heard of the Windows shell having been ported to Unix, never mind any one actually running the Windows shell on Unix.

Oh, and MacOS has gone Unixy as well, so that's another platform that will have a Bourne shell compatible shell available.

As for VMS and other exotic OSses, my knowledge about them is too limited to comment.

In reply to Re^3: RFC: A Primer on Writing Portable Perl Programs by Anonymous Monk
in thread RFC: A Primer on Writing Portable Perl Programs by yumpy

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks