From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glauber de Oliveira Costa Subject: Re: [PATCH] Error message for device not found at blkif.py Date: Wed, 18 Oct 2006 18:28:47 -0300 Message-ID: <20061018212846.GC16266@redhat.com> References: <20061018200845.GB16266@redhat.com> <453695B2.9080307@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <453695B2.9080307@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anthony Liguori Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Wed, Oct 18, 2006 at 03:59:30PM -0500, Anthony Liguori wrote: > Instead of throwing a VmError, could you subclass VmError with a more > specific error and throw that? Fore sure I can. But what does this condition have so differently from others that justifies that for it only? Although I agree with you that such a specificiness is good, VmError is being thrown everywhere, meaning that your proposal would require touching a great amount of code change. Is there any plans/opposals for that? -- Glauber de Oliveira Costa Red Hat Inc. "Free as in Freedom"