1. RE: Win32lib: ExitProcess
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01C22B82.A619B280
charset=iso-8859-1
Isn't it a weird world. It was placed there because somebody said it should
be there. I'm not an Windows expert yet so I trust the advice of the
community. Anyhow, if it's causing pain I can search for a better way.
--------
Derek.
> -----Original Message-----
> From: Thomas Parslow (PatRat) [mailto:tom at almostobsolete.net]
> Sent: Monday, 15 July 2002 7:35
> To: EUforum
> Subject: Win32lib: ExitProcess
>
>
>
> Hi,
>
> Does anyone know why win32lib calls ExitProccess when the primary
> window is closed? It's rather annoying for a couple of reasons, the
> first is that it stops code being executed after the call to WinMain
> and the second is that it stops Euphorias "with profile" from working.
> It probably causes other problems (it probably doesn't allow Euphoria
> to do its cleanup properly) and I can't see any reason for its use...
>
> Thomas Parslow (PatRat)
> E-Mail/Jabber: tom at almostobsolete.net
> ICQ: 26359483
>
>
>
>
==================================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
de afzender direct te informeren door het bericht te retourneren.
==================================================================
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the contents
herein and notify the sender immediately by return e-mail.
==================================================================
------_=_NextPart_000_01C22B82.A619B280
Content-Type: application/ms-tnef
2. RE: Win32lib: ExitProcess
> Isn't it a weird world. It was placed there because somebody said it
> should
> be there. I'm not an Windows expert yet so I trust the advice of the
> community. Anyhow, if it's causing pain I can search for a better way.
>
> --------
> Derek.
Hey Derek. I am almost sure that this call is not really needed.
Mostly it just unloads the linked DLLs and frees some Windows management
memory. However, since it is technically Euphoria that is doing the
loading of all these objects, I think these things will be cleared up
automatically anyways as soon as Euphoria itself terminates... ( I think
).
My 0.02 $
Don Phillips
3. RE: Win32lib: ExitProcess
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01C22C57.D1161F20
charset=iso-8859-1
Done. I will suggest that if somebody really, really wants to run
ExitProcess, that they do it in their App after WinMain() returns.
> -----Original Message-----
> From: Robert Craig [mailto:rds at RapidEuphoria.com]
> Subject: Re: Win32lib: ExitProcess
>
>
>
> Don Phillips writes:
> > Hey Derek. I am almost sure that this call is not really needed.
> > Mostly it just unloads the linked DLLs and frees some
> Windows management
> > memory. However, since it is technically Euphoria that is doing the
> > loading of all these objects, I think these things will be
> cleared up
> > automatically anyways as soon as Euphoria itself
> terminates... ( I think).
>
> Someone pointed out to me (Euman? Derek?) a long time ago
> that a small amount of space reserved for loaded .dll's was
> not being freed
> when Euphoria for Windows terminated.
>
> ExitProcess() frees these .dlls, so I started to use it in my
> local version
> of exw.exe. I discovered however (before releasing 2.3) that although
> ExitProcesss unloads the .dlls, it *doesn't* flush regular files
> that were written-to but never closed or flushed by the
> Euphoria program.
> This is something that the normal C exit() *does* do, and I'd like
> Euphoria users to be able to count on it. So I went back to
> using exit(),
> but I now keep track of all the loaded .dll's and I free them
> with FreeLibrary() at the end - see Cleanup() in runtime.c
> in the Euphoria source. Cleanup also outputs the profiling
> information,
> displays warning messages, and a few other minor things.
>
> So I think it's better that Win32Lib not call ExitProcess(),
> but if there's any other cleanup that we are now going to miss,
> I'd like to know about it.
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> http://www.RapidEuphoria.com
>
>
>
>
==================================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
de afzender direct te informeren door het bericht te retourneren.
==================================================================
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the contents
herein and notify the sender immediately by return e-mail.
==================================================================
------_=_NextPart_000_01C22C57.D1161F20
Content-Type: application/ms-tnef
4. RE: Win32lib: ExitProcess
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01C22CBA.7C6D1CE0
charset=iso-8859-1
Good point. I remember now why it was introduced. I will come up with a
cleaner solution. Thanks.
> -----Original Message-----
> From: 10963508 at europeonline.com [mailto:10963508 at europeonline.com]
> Subject: Re: Win32lib: ExitProcess
>
>
>
> If you use doEvents(0) in loop and user exits program exw.exe
> process will
> still be running.
> Maybe sending WM_CLOSE again will close that process?
>
> ----- Original Message -----
> From: "Derek Parnell" <Derek.Parnell at SYD.RABOBANK.COM>
> To: "EUforum" <EUforum at topica.com>
> Sent: Tuesday, July 16, 2002 1:31 AM
> Subject: RE: Win32lib: ExitProcess
>
>
> > Done. I will suggest that if somebody really, really wants to run
> > ExitProcess, that they do it in their App after WinMain() returns.
> >
> > > -----Original Message-----
> > > From: Robert Craig [mailto:rds at RapidEuphoria.com]
> > > Sent: Tuesday, 16 July 2002 7:28
> > > To: EUforum
> > > Subject: Re: Win32lib: ExitProcess
> > >
> > >
> > > Don Phillips writes:
> > > > Hey Derek. I am almost sure that this call is not
> really needed.
> > > > Mostly it just unloads the linked DLLs and frees some
> > > Windows management
> > > > memory. However, since it is technically Euphoria that
> is doing the
> > > > loading of all these objects, I think these things will be
> > > cleared up
> > > > automatically anyways as soon as Euphoria itself
> > > terminates... ( I think).
> > >
> > > Someone pointed out to me (Euman? Derek?) a long time ago
> > > that a small amount of space reserved for loaded .dll's was
> > > not being freed
> > > when Euphoria for Windows terminated.
> > >
> > > ExitProcess() frees these .dlls, so I started to use it in my
> > > local version
> > > of exw.exe. I discovered however (before releasing 2.3)
> that although
> > > ExitProcesss unloads the .dlls, it *doesn't* flush regular files
> > > that were written-to but never closed or flushed by the
> > > Euphoria program.
> > > This is something that the normal C exit() *does* do, and I'd like
> > > Euphoria users to be able to count on it. So I went back to
> > > using exit(),
> > > but I now keep track of all the loaded .dll's and I free them
> > > with FreeLibrary() at the end - see Cleanup() in runtime.c
> > > in the Euphoria source. Cleanup also outputs the profiling
> > > information,
> > > displays warning messages, and a few other minor things.
> > >
> > > So I think it's better that Win32Lib not call ExitProcess(),
> > > but if there's any other cleanup that we are now going to miss,
> > > I'd like to know about it.
> > >
> > > Regards,
> > > Rob Craig
> > > Rapid Deployment Software
> > > http://www.RapidEuphoria.com
> > >
> > >
> > ==================================================================
> >
> >
> > ==================================================================
> >
> >
>
>
>
==================================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
de afzender direct te informeren door het bericht te retourneren.
==================================================================
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the contents
herein and notify the sender immediately by return e-mail.
==================================================================
------_=_NextPart_000_01C22CBA.7C6D1CE0
Content-Type: application/ms-tnef
5. RE: Win32lib: ExitProcess
Derek,
its not needed, no wonder my clean up routines after WinMain() were not
being carried out. The only place i see it needed would be like in the
IDE were you would have to create dynamic processes for ran programs
from within.
jordah
Derek Parnell wrote:
> Isn't it a weird world. It was placed there because somebody said it
> should
> be there. I'm not an Windows expert yet so I trust the advice of the
> community. Anyhow, if it's causing pain I can search for a better way.
>
> --------
> Derek.
>
> > -----Original Message-----
> > From: Thomas Parslow (PatRat) [mailto:tom at almostobsolete.net]
> > Sent: Monday, 15 July 2002 7:35
> > To: EUforum
> > Subject: Win32lib: ExitProcess
> >
> >
> > Hi,
> >
> > Does anyone know why win32lib calls ExitProccess when the primary
> > window is closed? It's rather annoying for a couple of reasons, the
> > first is that it stops code being executed after the call to WinMain
> > and the second is that it stops Euphorias "with profile" from working.
> > It probably causes other problems (it probably doesn't allow Euphoria
> > to do its cleanup properly) and I can't see any reason for its use...
> >
> > Thomas Parslow (PatRat)
> > E-Mail/Jabber: tom at almostobsolete.net
> > ICQ: 26359483
> >
> >
> ==================================================================
>
>
> ==================================================================
>
>
