RE: Loadlib's callfromlib() - anybody using it?!?

["Dirk Ringe" <ringe@...>]

Thats wrong. WinNT based systems free all resources after the process exits
even if the process leaked something. This was somewhat a problem afaik with
win9x based systems with ui and gdi resources but also not with plain
memory.

Dirk

-----Original Message-----
From: owner-lua-l@tecgraf.puc-rio.br
[mailto:owner-lua-l@tecgraf.puc-rio.br]On Behalf Of Philippe Lhoste
Sent: Monday, June 10, 2002 5:57 PM
To: Multiple recipients of list
Subject: Re: Loadlib's callfromlib() - anybody using it?!?


Note that I don't think Windows releases automatically allocated memory, as
somebody reported memory leaks because he didn't knew the -c switch.
Windows closes file descriptors, but we still have to clean the memory after
ourselves. That's why Windows systems become instable after some time when
running bad applications: as they leak memory, the available resources are
slowly eaten.
That's why we have BoundsChecker, Purify, etc. :-)

Can I make a suggestion to put your quote in the new manual? Thank you.

Regards.

--
--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--
Philippe Lhoste (Paris -- France)
Professional programmer and amateur artist
http://jove.prohosting.com/~philho/
--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--

GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net