Re: Problems with seemingly simple string matching...

damned line endings it was. When I replaced chomp($instr) with chop($instr);chop($instr); everything worked as expected.

NOW what puzzles me is why chomp didn't work. the input file was created on the same platform as the program and the perl interpreter, why didn't it properly remove the <CR>:<NEWLINE> pair?

Comment on Re: Problems with seemingly simple string matching...

Replies are listed 'Best First'.
Re^2: Problems with seemingly simple string matching... by Anonymous Monk on Oct 05, 2013 at 01:02 UTC
NOW what puzzles me is why chomp didn't work. ddumper^{Basic debugging checklist} $line and $/ OTOH, $line =~ s/\s+$//; ## trim trailing whitespace	[reply]
Re^2: Problems with seemingly simple string matching... by kcott (Archbishop) on Oct 05, 2013 at 15:15 UTC
G'day desertrat, "NOW what puzzles me is why chomp didn't work. the input file was created on the same platform as the program and the perl interpreter, why didn't it properly remove the <CR>:<NEWLINE> pair?" From your shebang line, it looks like you're on a nix OS: default line-ending is `"\n"`. The file you're dealing with has `"\r\n"`, which is the MSWin default. I'm not familiar with `iCal`. Perhaps its default output format is the same as MSWin. You may be able to change that via configuration or options. Assuming you are on a nix OS, given a string ending in `"\r\n"`, I'd expect `chomp` to remove the trailing newline and leave the carriage return. -- Ken	[reply] [d/l] [select]