Re: Whatever happened to chomp?

2 is a number, and perl is trying to DWYM with the numerical compare (==). Try putting
one two three four
[download]

~~in __DATA__, and~~

change the conditional to if ($data eq '2'). Now see what effect chomp has...

Update: Struck out the data section and added bit about numerical compare to the first sentence. I shouldn't have included the red herring (one, two, three). The original point was supposed to be that perl will treat a variable like a number in numerical context (== instead of eq).

Comment on Re: Whatever happened to chomp? Select or Download Code

Replies are listed 'Best First'.
Re: Re: Whatever happened to chomp? by pg (Canon) on Dec 14, 2003 at 19:53 UTC
2 is a number. No, 2 could be a number or a string base on the context as how you use it. A better answer is to point out what he really misunderstood: the context. It is pretty straight to simply change == to eq, and quot 2: `use Tk; use Tk::NoteBook; use strict; use warnings; use strict; use warnings; while (my $data = <DATA>) { chomp $data; print $data; if ($data eq "2"){print "->got 2\n"} } print "Enter a 2\n"; my $input = <>; chomp $input; if ($input eq "2"){print "->got 2\n"} __DATA__ 1 2 3 4` [download]	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Whatever happened to chomp?
by pg (Canon) on Dec 14, 2003 at 19:53 UTC

2 is a number.

No, 2 could be a number or a string base on the context as how you use it. A better answer is to point out what he really misunderstood: the context.

It is pretty straight to simply change == to eq, and quot 2:

use Tk;
use Tk::NoteBook;
use strict;
use warnings;
use strict;
use warnings;

while (my $data = <DATA>) {
chomp $data; 
print $data;
if ($data eq "2"){print "->got 2\n"}
}

print "Enter a 2\n";
my $input = <>;
chomp $input;
if ($input eq "2"){print "->got 2\n"}

__DATA__
1
2
3
4
[download]

[reply]
[d/l]