Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Dearest Monks,

It has taken me several years that I have given in on a topic and cannot see any option but to include more than simple exception catching in my code. So far all I did was setup a log file and hand out debug versions that would come with an config file that writes a very high detail log file that I could normally interpret to find the errors.

However I am currently importing and converting a file that quite regularly was edited manually and does not quite live uf to its tight formatting standards.

I have seen packages that go a lot further than the standard eval{}; or $SIG{ __DIE__ } = &\catch_me basics and would like to make use of a relatively robust and basic one. However at the same timeI have a list of requirements:

  1. Class independent default types: I need to be able to define standard exception types a la "ArrayIndexOutOfBounds" , "StringContainsOnlyNumericCharacters", etc.
  2. I need integration into TK to display error messages
  3. I need to be able to set up different kinds of error levels due to different kind of debug levels. E. g. report all expected behaviour for internal testing and report fatal for client only.

What are other users using? I am interested in your answers.


Cheers,
PerlingTheUK

In reply to Exception Safe Perl by PerlingTheUK

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others studying the Monastery: (7)
As of 2024-04-19 09:35 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found