GSL numeric overflow

Is there some plan for handling GSL problems in a more graceful way  
than killing the interpreter?

Not presently a big issue, other than perhaps the least squares stuff  
I kicked over, but it seems like simple stuff like numeric overflow  
should get caught when you, say, (factorial 200)

Looks pretty easy to point someplace useful with gsl_set_error_handler

-Scott

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/