What kind of error states are we talking about? divide by zero and out of memory?
IMHO a C++ library should just throw C++ exceptions, thats what they are here for. If only for better readability -> less bugs. If you declare methods with "except +" to Cython then they will automatically be converted into Python exceptions, so its also very convenient for us. Pynac uses that all the time. Pretty much the only potential downside are rumors that exceptions might possibly hinder the optimizer. Though I've never seen that in a reasonable benchmark. While that is certainly a possibility, it would just be an optimizer bug. All reasonable C++ compilers uses a zero-cost model so its at least as fast as handling / returning some error flag. What _is_ expensive is when an exception occurs, but in C++ you are not supposed to use exceptions for program flow like in Python. On Tuesday, November 11, 2014 10:15:44 PM UTC, Jean-Pierre Flori wrote: > > Dear all, > > As you must have noticed, Victor Shoup just released a new thread safe > version of NTL. > > He also took the opportunity to ask me (and surely a bunch of other > people) what would be expected from exception handling in NTL > Currently NTL just prints something and then aborts. > Note that we patch that in Sage to call one of our own functions and avoid > aborting. > I'm no C++ expert and don't usually play with exceptions, so I don't have > anything that sart to say. > But your comments/ideas/suggestions are more than welcomed. > I can gather them and forward them back to Victor. > > Best, > JP > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
