Yeap. But be careful. Immutables are not released before the end. It is a
very bad idea to use them in recurring functions. That's why the only place
they are used is in initialization & configuration.
BR,
Nikos
----- Original Message -----
From: "Alejandro Guerrieri" <aguerri...@kannel.org>
To: "Dilan Anuruddha" <dilan...@gmail.com>
Cc: <devel@kannel.org>
Sent: Wednesday, November 25, 2009 1:23 PM
Subject: Re: memory leak in octstr_imm
I don't think so, immutables are kept in memory until the process
finishes. That's by design.
Read the comments on gwlib/octstr.h, there's an explanation about it
there.
Regards,
--
Alejandro Guerrieri
aguerri...@kannel.org
On 25/11/2009, at 12:04, Dilan Anuruddha wrote:
Hi all,
I've been using kannel libraries for a campus project. When we
create Octstr objects using octstr_imm (e.g. when we pass arguments to a
function), we don't release the memory.... Isn't this leaking memory???
So do we have to explicitly release memory inside the function????
thanks in advance,
Dilan
