Re: Error Handling in 2.0

[John Locke <..hidden..>]

Ok this might be a dumb noob question, but why use some hexadecimal
notation of the module? Why not just the string module name?

-- John

-------- Original Message  --------
Subject: [Ledger-smb-devel] Error Handling in 2.0
From: Chris Travers <..hidden..>
To: Development discussion for LedgerSMB
<..hidden..>
Date: Sat 13 Mar 2010 10:22:29 AM PST
> Hi all;
>
> I am looking into error handling beyond 1.3 and wondering what people
> think.  I am tentatively inclined to suggest as follows:
>
> use Class::Struct LedgerSMB::Error => {
>        type => '$', # one of FATAL, ERROR, WARN, DEBUG, INFO
>        module => '$', # Hexadecimal notation of module raising the error
>        id => '$', # hexadecimal notation of error id
>        msg => '$', # Unlocalized string of error message
>        extended => '$', # Extended information on error, may be logged
> displayed
>                               # to user depending on context and settings
>         stack_trace => 'Devel::StackTrace' # generated automatically if settings
>                                                           # require
> };
>
> I am then thinking about subclassing this out to LedgerSMB::Error::Web
> with no additional members.
>
> What do folks think?
>
> Best Wishes,
> Chris Travers
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Ledger-smb-devel mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
>