[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: RE: exit
- From: Jim Mathies <Jim@...>
- Date: Sat, 26 Aug 2000 15:57:17 -0700
We had the same problem with our embedded app. I reworked the
alert a little and removed the exit call, replacing it with a
flag i check in a few key places to force the execution thread to
unwind and exit from my initial dobuffer call.
You also might be able to do it with setjmp and longjmp, although i have
not tried this. I do use setjmp and longjmp in a similar library (GLUT)
which has the same problem.
From: Andre de Leiradella [mailto:firstname.lastname@example.org]
Sent: Thursday, August 24, 2000 6:20 AM
To: Multiple recipients of list
I'm using Lua to extend Moray - a 3D modeller for POV-Ray that runs
under Windows - but I noticed that, in some situations, Lua calls
_ALERT (wich has been redefined to pop a MessageBox) and exits.
Well, I can't let Lua exit without giving the user the chance to save
his/her work. So I would like to know where exactly Lua can call exit
() and how to avoid it.
Of course I'm aware of luaL_opt*, but are there any other places
where exit() can be called besides argument passing from Lua to C?
For those who want to check this project, visit
http://members.xoom.com/leiradel/. The source code will be available
as soon as I have a resonable stable version, without exit()'s!
Andre de Leiradella