in reply to dbi: PrintError and RaiseError

There can be good reasons for certain exceptions (accidental pun) but in general always RaiseError. Software that is broken should act broken. I'd always rather explain to a customer why an app stopped working over why an app put orders in the bit bucket for two weeks or sent reports with incorrect information while acting like everything was running fine.

Replies are listed 'Best First'.
Re: RaisePetPeeve => 1
by gube (Parson) on Dec 24, 2008 at 05:52 UTC
    I too agree to RaisePetPeeve. Most of the times if we try to delete 3 things as zwon mentioned and 1st and 3rd delete and 2nd record not getting delete due to some constraints, we may not known exactly in big application and it will create problem later. So, rather use RaiseError find the issue(constraint issue or whatever) and fix the problem.
[reply]

In Section Seekers of Perl Wisdom