1. exotica+error -> crash
Another question to Todd or Rob:
If there's an error in the Euphoria source of exotica program in =
MainLoop (when using emain.ew) my computer will crash and I have to =
restart it. Is there any way to prevet this?=20
ex.err contains the crash message like:=20
F:\EUPHORIA\exotica\Examples\t3de.exw:179
Syntax error - expected to see possibly 'do', not 'for'
for c=3D1 to LastCam
^
My quess is that the error message (like above) crashes my machine when =
euphoria's error handle tries to display the message while DirectX is =
still active.
--Tapani
2. Re: exotica+error -> crash
- Posted by Todd Riggins <triggins at AIRMAIL.NET>
Sep 19, 1999
-
Last edited Sep 20, 1999
Talvitie wrote:
>
> Another question to Todd or Rob:
>
> If there's an error in the Euphoria source of exotica program in MainLoop
> (when using emain.ew) my computer will crash and I have to restart it. Is there
> any way to prevet this?
> ex.err contains the crash message like:
>
> F:\EUPHORIA\exotica\Examples\t3de.exw:179
> Syntax error - expected to see possibly 'do', not 'for'
> for c=1 to LastCam
> ^
>
> My quess is that the error message (like above) crashes my machine when
> euphoria's error handle tries to display the message while DirectX is still
> active.
That one really got me stomped cause this doesn't happen to me.
When I did something wrong with Euphoria code, it will automatically
close my program and pop up the Euphoria error box.
Only thing I can think of is mabie since DirectX allocates memory usage
while the interpeter is running through your program and then it catches
the error, mabie there isn't enough resources left to open up a Euphoria
error box and then it crashes your machine? This could happen if you
go through this process enough times.
Or does Euphoria checks code syntax before actually running the program?
- Todd Riggins
