< Previous by Date	Date Index	Next by Date >
< Previous in Thread	Thread Index

Re: [reSIProcate] ConfigParse.cxx: more detail in exceptions

From: Scott Godin <sgodin@xxxxxxxxxxxxxxx>
Date: Tue, 20 May 2014 12:33:49 -0400

Hi John,

Thanks! I have committed a variation of this fix. I added the additional details in a few more places and I used the resip::Data class to build the strings instead.

Regards,

Scott

On Thu, May 15, 2014 at 2:06 PM, John Gregg <jgregg@xxxxxxxxx> wrote:

When we throw exceptions if we don't like a command line argument or can't read a config file, we should include the offending argument/filename in the text of the exception. This makes it a lot clearer to the end user what went wrong in a fatal error.

Then enclosed file consists of two small changes to the 1.9.6 version.

-John Gregg

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

References:
- [reSIProcate] ConfigParse.cxx: more detail in exceptions
  - From: John Gregg

Prev by Date: Re: [reSIProcate] Log::initialize should take log level in upper or lower case (rutil)
Next by Date: [reSIProcate] rutil Log: give app control over syslog facility; don't hardcode LOCAL6
Previous by thread: [reSIProcate] ConfigParse.cxx: more detail in exceptions
Next by thread: [reSIProcate] TransactionState::processStateless() should not assert in stateful timer case
Index(es):
- Date
- Thread