Re: Unbounded string deallocation

[mcc@entropy.cs.princeton.edu (Martin C. Carlisle)]

As Pascal pointed out, you are absolutely correct.  A reassignment will
reclaim the previous storage.

A common implementation of Unbounded_Strings is to use Controlled types.
Using controlled types you can create a lot of such data structures that
manage their own memory.

--Martin

In article <37C54509.17E067C1@res.raytheon.com>,
Andy Askey  <askeya@res.raytheon.com> wrote:
>Martin,
>Thanx for the info.  My unbound string never goes out of scope until I
>terminate my program (which is why I "thought" needed to deallocate it
>myself).  If all I have to do to reclaim the memory is to create a new
>string using the same variable, then this takes care of all my
>problems.  Just to make sure I understand this correctly:
>
>my_string : ada.strings.unbounded_string;
>begin
>
>  -- grab approx 1024 bytes of memory
>  my_string := new ada.strings.unbounded_string.To_Unbound_String(1024);
>
>  -- give back the 1024 bytes and grab 2048 new memory bytes
>  my_string := new ada.strings.unbounded_string.To_Unbound_String(2048);
>
>end
-- 
Martin C. Carlisle, Asst Prof of Computer Science, US Air Force Academy
carlislem@acm.org, http://www.usafa.af.mil/dfcs/bios/carlisle.html
DISCLAIMER:  This content in no way reflects the opinions, standards or 
policy of the US Air Force Academy or the United States Government.