From: Matthew Heaney <matthewjheaney@earthlink.net>
Subject: Re: Free-ing memory: not springing leaks?
Date: Sun, 14 Sep 2003 12:51:55 GMT
Date: 2003-09-14T12:51:55+00:00 [thread overview]
Message-ID: <uwucb8rbh.fsf@earthlink.net> (raw)
In-Reply-To: 9JY8b.1963$WI3.25442@newsfep4-glfd.server.ntli.net
chris <spamoff.danx@ntlworld.com> writes:
> What if there is no call to free memory?
Then your binding is missing at least one operation.
> For example, the library loader for linux error mechanism is to return
> an error msg describing the problem. Once you have it appears to be
> your problem what you do with it. There is no call present in the
> library to return the memory.
This is an Ada binding? Who wrote it?
> Should I bind to a C compiled function to do this? Perhaps in the
> case of linux, to the free function in the std lib? I guess you are
> left to free it yourself in C because it provides "free" and it is
> natural to use it in C.
If you know it was malloc'd, then yes, just write a binding to free and
call that.
next prev parent reply other threads:[~2003-09-14 12:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 21:33 Free-ing memory: not springing leaks? chris
2003-09-14 1:10 ` Matthew Heaney
2003-09-14 11:02 ` chris
2003-09-14 12:51 ` Matthew Heaney [this message]
2003-09-14 12:14 ` chris
2003-09-14 14:24 ` Ludovic Brenta
2003-09-14 19:00 ` chris
2003-09-14 16:06 ` Simon Wright
2003-09-15 7:13 ` Martin Krischik
2003-09-18 20:15 ` Warren W. Gay VE3WWG
2003-09-19 3:02 ` Hyman Rosen
2003-09-19 13:07 ` Warren W. Gay VE3WWG
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox