Re: code works in Windows (Strawberry Perl), fails in Unix

"I'm forced to work with someone else within the company who is running this in the Unix environment. This disconnect makes resolving issues frustrating."

Quite the opposite. It is your co-worker that is being forced to work with your code. When you have no unit testing in place, nor any smoke tests or commit hooks, this is what happens. How can your co-worker expect to use your code if it has not been tested, in the environment it wiill be deployed to, first?

Comment on Re: code works in Windows (Strawberry Perl), fails in Unix - possible path/environment issue

Replies are listed 'Best First'.
Re^2: code works in Windows (Strawberry Perl), fails in Unix - possible path/environment issue by Anonymous Monk on Mar 03, 2015 at 20:53 UTC
That's fair. I should have said: 'Due to company restrictions, I do not have access to a Unix environment to test my code, and can only relay error messages from my coworker. This is frustrating for both* of us!*	[reply]
Re^3: code works in Windows (Strawberry Perl), fails in Unix - possible path/environment issue by Anonymous Monk on Mar 03, 2015 at 21:46 UTC
""I'm forced to work with someone else within the company who is running this in the Unix environment ... Due to company restrictions, I do not have access to a Unix environment to test my code ..." Let us break this down. You are both within the same company, yet one has access to a Unix environment while the other does not. This is the problem, and unless you push back you will be forever the brunt of it. Good luck!	[reply]