Well, the if you find it difficult to correlate a return value (exceptions are
just fancy return values) with where they came from you have a very big problem.
- Original Message -
> From: "Dan Kenigsberg"
> To: "Saggi Mizrahi"
> Cc: "Simon Grinberg" , "arch" , "VDSM
> Project Developm
On Thu, Aug 16, 2012 at 02:10:28PM -0400, Saggi Mizrahi wrote:
>
>
> - Original Message -
> > From: "Simon Grinberg"
> > To: "Saggi Mizrahi"
> > Cc: "arch" , "VDSM Project Development"
> >
> > Sent: Thursday, August 16, 2012 12:12:04 PM
> > Subject: Re: [RFC] Exception is VDSM
> >
>
- Original Message -
> From: "Simon Grinberg"
> To: "Saggi Mizrahi"
> Cc: "arch" , "VDSM Project Development"
>
> Sent: Thursday, August 16, 2012 12:12:04 PM
> Subject: Re: [RFC] Exception is VDSM
>
>
>
> - Original Message -
> > From: "Saggi Mizrahi"
> > To: "arch" , "VDS
Currently we have very specific exceptions.
This causes proliferation of exception with no real gain.
There is really no benefit for each call to throw it's own error message:
For instance,
MiscFileReadException
MiscFileWriteException
MiscBlockReadException
MiscBlockWriteException
* There are abo
