Re: Using exceptions in the core

[John W. Eaton]

On 10/07/2015 12:09 PM, Mike Miller wrote:

> But this is about the same as having, say
>
>    std::string octave_value::string_value (); // this one throws an exception
>    std::string octave_value::safe_string_value (const std::string& msg) nothrow;
>
> Do we want to give the user the option of handling the exception or
> having error() called for them?

Since error throws an exception, both of these would throw exceptions, 
but the first would just display only the default "wrong-type-argument" 
message.

jwe