From: Chris M. <ch...@al...> - 2010-10-15 13:59:27
|
John Fay writes: > > The primary issue here is maintaining compatibility > with GLUT. GLUT calls "exit"; therefore "freeglut" > will call "exit". I've already suggested a strategy for extending FreeGLUT to support "soft errors" in a comment to the feature request: 2116152 add fgError() exit callback/routine The idea is to add a command line argument to enable the "soft fail" mode and to return some status in the case of a fail of glutInit(). Once you've made it past that hurdle, everything else can be done within the current framework. > We've already added extensions to handle cases > in which the application programmer wants to do > something besides exiting Err, what are these and how do they solve the problem of FreeGLUT taking out the perl interpreter by calling exit on error? Cheers, Chris |