Re: Messages Round II (was Leveraging known constructs (was Public API firs

2006-05-05 Thread Jason Carreira
Yeah, I generally like it, but I still prefer the more obvious addError(), addWarning(). I like my methods as verbs... makes reading the code easier (to me). - The attached version supports arbitrary levels. I used an interface instead of an enum so the user can define additional levels if

Re: Messages Round II (was Leveraging known constructs (was Public API firs

2006-05-05 Thread Bob Lee
I'm cool with that. Sticking with verbs, there's also err(), warn(), inform(). ;) Bob On 5/5/06, Jason Carreira [EMAIL PROTECTED] wrote: Yeah, I generally like it, but I still prefer the more obvious addError(), addWarning(). I like my methods as verbs... makes reading the code easier (to

Re: Messages Round II (was Leveraging known constructs (was Public API firs

2006-05-05 Thread Craig McClanahan
On 5/5/06, Jason Carreira [EMAIL PROTECTED] wrote: Yeah, I generally like it, but I still prefer the more obvious addError(), addWarning(). I like my methods as verbs... makes reading the code easier (to me). I can see how verbs make the code easier to *read*, but not sharing a common prefix

Re: Messages Round II (was Leveraging known constructs (was Public API firs

2006-05-05 Thread Jason Carreira
To err is human... do not lightly give this power to web applications ;-) I'm cool with that. Sticking with verbs, there's also err(), warn(), inform(). ;) - Posted via Jive Forums