Re: OpenGl again.
Christopher Hickman writes:
> The insistance by call_dll() that *function* must be called and
> for it to return a value might be causing the stack to become
> corrupted. That could cause the program to jump to a bad address
> when a machine code RET pops one off the stack, causing the
> "Invalid Instruction" error.
> [To Rob]
> What do you think? Am I way off here? If not, any chance of a
> fix?
I'm not sure what you mean by "call_dll",
however, it's my impression that you will crash if
you declare the wrong number of arguments to a C routine
that you call from Euphoria, but getting the void or non-void
part of its declaration wrong will not matter.
In the worst case you will just get a garbage value returned,
or you will ignore a legitimate value that is returned.
Maybe someone can test this to be sure.
Regards,
Rob Craig
Rapid Deployment Software
http://members.aol.com/FilesEu/
|
Not Categorized, Please Help
|
|
