Comment out use CGI; and it will work as you expect.

One of the first things CGI.pm does on Win32 is binmode STDIN, STDOUT and STDERR. A side effect of binmode is that perl no longer does its transparent line-end adjustments.

Try this little demo:

use strict;
use warnings;

print "Just hit enter (before CGI)";
my $var = <STDIN>;
print ":", ord $_, ":" for (split //, $var);
print "\nChomping\n";
chomp $var;
print ":", ord $_, ":" for (split //, $var);
print "\n";

eval 'use CGI;';
print "Just hit enter (after CGI)";
$var = <STDIN>;
print ":", ord $_, ":" for (split //, $var);
print "\nChomping\n";
chomp $var;
print ":", ord $_, ":" for (split //, $var);

__END__
output:
Just hit enter (before CGI)
:10:
Chomping

Just hit enter (after CGI)
:13::10:
Chomping
:13:
[download]

As you see, there is a carriage return left after using CGI that isn't there before CGI.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.