in reply to General tips for Unix to Windows script migration?

Big pain in the neck for me was that on *NIX machines you could do: 
print "Hello\n";

[download]
and everything works just dandy. Where as if you run the same code with say ActiveState, you will actually get an extra \r\n at the end of your print statement. So from a formatting perspective, keep that in mind...I am sure there is probably a way to get around it, but I am lazy, so I just change it to 
print "Hello";

[download]
and it works the same. Just something to keep in mind! later krazken

Replies are listed 'Best First'.
Re: Re: General tips for Unix to Windows script migration?
by Fastolfe (Vicar) on Jun 27, 2002 at 19:38 UTC
    Define "extra"? DOS/Win32 newlines are different, but when you write something like this: 
    print "line one\n";
print "line two\n";

    [download]
    You should not get double-spaced output. There shouldn't be any "extra" newlines inserted here.

    You may, however, be seeing a trailing newline at the termination of your script. This is added by the Win32 command prompt. Even typing 'rem' will give you an empty line before showing the next prompt.

[reply]
[d/l]

In Section Seekers of Perl Wisdom