[Octave-bug-tracker] [bug #59592] using std::exception to catch errors

[Rik]

Update of bug #59592 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #2:

I can see that this would be easy to resolve.  It may have even been an
oversight not to "public"ly inherit from std::runtime_error.  I've CC'ed jwe
who did the work on this to review that question.

But, I do wonder how critical it is to fix this.  When coding for Octave, such
as an octfile, a C++ programmer has access to all the functions and data types
that Octave itself has.  Since this is a try block for Octave code, why not
catch an Octave exception rather than catching the generic C++ exception?  For
example, the following works:


  catch (const octave::execution_exception& e)


Is there some benefit that I'm not seeing for catching the more general parent
class of std::exception?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59592>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/