Ahh, but here is the real problem: certain customers forbid us from changing the platform load. Has anyone else run into this? It's very common with many of the projects that I have worked on in the Detroit area.
Security and system administration are very, very tight at the auto companies. Everything must be served, and if I want to use cygwin, I'd have to jump through hoops to serve it along with the desired version of perl. Btw, perl is frowned upon quite seriously at the autos. The patent response from certain admins is: "Who's going to support it? If it breaks, who do I call, the Internet? Ha. Ha. Ha."
Geez, Louise.
So, for now, the answer is that we keep one server at the back end of our system that runs all of our perl scripts. This allows us to use perl without running into too many complaints. But the server could easily change from *nix to win32 in a year. So my code needs to be able to run if such a change occurs.
Thanks to everyone for the valuable input.
-- ccarden
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.