Mailinglist Archive: zypp-devel (116 mails)
| < Previous | Next > |
Re: [zypp-devel] Improve error reports by creating an error stack?
- From: Stanislav Visnovsky <visnov@xxxxxxx>
- Date: Mon, 18 Jun 2007 14:09:00 +0200
- Message-id: <200706181409.00718.visnov@xxxxxxx>
Dňa Po 18. Jún 2007 14:06 Michael Andres napísal:
> At various locations we catch exceptions and translate them into other
> exceptions.
>
> Would it be helpfull, if we'd create a simple stack of error strings in
> class Exception? So we could store and propagate the old Exceptions
> asString and/or asUserString.
>
> Something like this:
>
> Failed to create repository.
> -Reason: Failed to parse some file
> -Reason: Failed to provide some file
> -Reason: File not found
>
>
> But it's only worth the efford, if the UI is willing to display such
> multiline stacklike error messages.
How should UI report this? Typically, user is interested in 1 and last message
of the stack (reason & the overall result)
Stano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> At various locations we catch exceptions and translate them into other
> exceptions.
>
> Would it be helpfull, if we'd create a simple stack of error strings in
> class Exception? So we could store and propagate the old Exceptions
> asString and/or asUserString.
>
> Something like this:
>
> Failed to create repository.
> -Reason: Failed to parse some file
> -Reason: Failed to provide some file
> -Reason: File not found
>
>
> But it's only worth the efford, if the UI is willing to display such
> multiline stacklike error messages.
How should UI report this? Typically, user is interested in 1 and last message
of the stack (reason & the overall result)
Stano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |