Why does mx-inlines.cc use throw ()?

[LachlanA]

Greetings all,

I'm trying to implement "dbstop if naninf" like Matlab has, which involves
turning on floating point exception signals.

Currently, I catch the signals, and then throw an
octave_execution_exception.  However, functions like  max  and  min  call
code in mx-inlines.cc that has "throw ()" declarations prohibiting them from
throwing exceptions.

Are these really needed?  Is it just to allow optimization or is it also
required to ensure functional correctness?

I've also read that they are deprecated, but the C++11 replacement
"noexcept" keyword would have the same problems for me.

Cheers,
Lachlan



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Why-does-mx-inlines-cc-use-throw-tp4676696.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.