in reply to Re: Re: extract useful infos from cvs diff output
in thread extract useful infos from cvs diff output

I'd like to think the stuff I removed in my version added flexibility.

The global variable in Text::Tabs irritates me too, but we're talking about a 10-liner utility script here. I don't use strictures on oneliners either, you know.

Your "exception handling" message is misleading. If the open fails due to permission problems, your message still says the script found no file. The diamond operator will produce a good error message: detailing the operation (opening in this case), filename and reason for failure ($!). Note that it will not look like a Perl error - it doesn't contain the "at line [..]" bits.

I don't see any exception handling on your write-open either. That's an issue I just forgo entirely by printing to STDOUT and letting the user take care of it.

And finally, if I ever change my mind about my file naming conventions, this script will not have to be touched. To me, that's very important. I try to write my utility scripts with the Unix toolset philosophy in mind and so far, it's paid off.

Makeshifts last the longest.

  • Comment on Re^3: extract useful infos from cvs diff output