comment on

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

In reply to Re^2: Problems with seemingly simple string matching... by kcott
in thread Problems with seemingly simple string matching... by desertrat

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks