|
From: | John W. Eaton |
Subject: | Re: Opinions: exceptions in user oct files |
Date: | Wed, 3 May 2017 18:28:39 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 |
On 05/02/2017 10:35 PM, Mike Miller wrote:
Yes, that is what I meant. And maybe even a special case for any std::exception, which is guaranteed to have a what() method that might help describe the reason.
I experimented with this a bit and came up with the attached patch. There may be other places that would need similar treatment.I also experimented with deriving the octave exceptions (execution, index, interrupt, and exit) from std::exception, but then realized that it would probably cause trouble for the interrupt and exit exceptions to be derived from std::exception. We might still want to derive the octave execution and index exceptions from std::exception, however.
jwe
except-diffs.txt
Description: Text document
[Prev in Thread] | Current Thread | [Next in Thread] |