The big problem is line endings. On WinBlows you need carriage return and line feed (ascii 13 and 10, respectively). However on (*nix) lines are terminated by line feed. By transferring in binary mode, you will see ^M at the end of line (remember ascii 13 ?). This alone should not cause any issues with running Perl scripts, I have done this many times. BTW, there is a nifty little program called dos2unix (not sure if this is standard for all (*nix)), that removes extraneous carriage returns from files.

Chuck Fox

[EMAIL PROTECTED] wrote:

I have a perl script that I developped in a windows machine and it had to be transfered by ftp to a UNIX server. The codes worked fine when I tested them on my windows machine. Is it true that the data could get corrupted while being ftp'ed from Windows to Unix. I was told by the Unix people


If you ftp them in binary mode instead of ascii mode yes that will screw it up.




that they couldn't get the code to work at first because the codes were developped in windows


What do you mean by "didn't work". They failed completely, output not as expected, ... What modules did you use? Are those installed on the unix host? What errors are you getting? To the screen or a log of some kind?



environment. Codes are working now though. Just being curious.





Reply via email to