1. Re[4]: Any bug on compiled abort()?
- Posted by akusaya at gmx.net
Jan 23, 2006
R> I don't see anything wrong with it, but I'm not
R> an expert on C .dlls. I learned what I had to,
R> a long time ago, to make Euphoria .dlls from the translator.
R> I found the documentation available on C .dll creation to
R> be very murky and very inconsistent across the various
R> C compilers.
To prevent interfering with Eu discussion now I send this via private
mail.
I have asked the customer and he said he didn't see any dos window.
The customer said he asked for refund if I cannot solve this problem.
Is there any way to exit the program without closing files/unloading
dlls/cleaning up etc? Maybe using win32 API or something else?
Thank you.
2. Re: Re[4]: Any bug on compiled abort()?
akusaya wrote:
>
> R> I don't see anything wrong with it, but I'm not
> R> an expert on C .dlls. I learned what I had to,
> R> a long time ago, to make Euphoria .dlls from the translator.
> R> I found the documentation available on C .dll creation to
> R> be very murky and very inconsistent across the various
> R> C compilers.
>
> To prevent interfering with Eu discussion now I send this via private
> mail.
>
> I have asked the customer and he said he didn't see any dos window.
>
> The customer said he asked for refund if I cannot solve this problem.
>
> Is there any way to exit the program without closing files/unloading
> dlls/cleaning up etc? Maybe using win32 API or something else?
You might try calling the WIN32 API routine, ExitProcess:
VOID ExitProcess(
UINT uExitCode // exit code for all threads
);
As I recall though, you must be sure to close all your open (normal)
files first, using Euphoria's close(),
because ExitProcess() won't do it for you, though
it does close .dll files (only).
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
