On Sat, Mar 13, 2010 at 11:20 AM, Luke wrote:
> On Sat, 13 Mar 2010, Chris Travers wrote:
>
>> On Sat, Mar 13, 2010 at 10:46 AM, John Locke wrote:
>>> Ok this might be a dumb noob question, but why use some hexadecimal
>>> notation of the module? Why not just the string module name?
>>
>> I was t
On Sat, Mar 13, 2010 at 11:07 AM, John Locke wrote:
> I'm not a big fan of error codes, and coding modules so that casual
> programmers not familiar with the codebase have to go hunt around to
> find the source of the issue... well, ugh.
The idea of error codes is to solve a different set of prob
On Sat, 13 Mar 2010, Chris Travers wrote:
> On Sat, Mar 13, 2010 at 10:46 AM, John Locke wrote:
>> Ok this might be a dumb noob question, but why use some hexadecimal
>> notation of the module? Why not just the string module name?
>
> I was thinking about having a much more compact error notation
unction name, line number, string
message, severity if nothing else.
Cheers,
John
Original Message ----
Subject: Re: [Ledger-smb-devel] Error Handling in 2.0
From: Chris Travers
To: Development discussion for LedgerSMB
Date: Sat 13 Mar 2010 10:56:43 AM PST
> On Sat, Mar 13,
On Sat, Mar 13, 2010 at 10:46 AM, John Locke wrote:
> Ok this might be a dumb noob question, but why use some hexadecimal
> notation of the module? Why not just the string module name?
I was thinking about having a much more compact error notation. Maybe
the namespace it is called from would be
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
To: Development discussion for LedgerSMB
Date: Sat
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 raisin
