in reply to Re^3: Need help deleting *.bak files
in thread Need help deleting *.bak files

You might have had an case if this code was part of larger project, but you're saying you assumed it wasn't?

If it's not part of a bigger project, then it's a command line tool. Mixing everything together like that makes for a very bad command line tool. It makes it harder to use, and that's not even counting the difficulty in grepping the format you used.

You also removed the code that makes it useful outside a big project: the reporting of whether an error occurred or not via the exit code.

Finally, convention and tradition is being ignored without justification. Doing something different without reason is poor programming.

Replies are listed 'Best First'.
Re^5: Need help deleting *.bak files
by Anonymous Monk on Jan 19, 2010 at 07:15 UTC
    You also removed the code that makes it useful outside a big project: the reporting of whether an error occurred or not via the exit code.

    Saying it twice doesn't make it true. The output on failure would be "filename: failure ($!)"

[reply]

      What did I say twice?

      How does the quoted passage relate to your comment?

      Why did you make that comment? It's redundant and doesn't contradict anything I said.

      I believe you misread something. Or maybe you don't know what an exit code is?

[reply]
        "It would also be useful to say what failed" was a strange response to the code in a comment that provided that information in the form of filename and error code. There was nothing to refute but where it should be displayed (stderr) or how (as infrequent warning rather than status message).
[reply]

In Section Seekers of Perl Wisdom