Re: Program Terminates ...

["Robert I. Eachus" <rieachus@comcast.net>]

Jeff C, wrote:

>>Hey. Could it be that the Unbounded_String's are not the problem per se,
>>but the fact that they are within record objects being dynamically
>>allocated is the problem?  Or one of the problems?

> Well, if these record are either not controlled types or are never
> explicitly free'd then yes this could be the problem.

Definitely true.  If you allocate an object on the heap, then don't free 
it, any Unbounded_Strings within the object won't be deallocated unless 
you leave the scope of the object type.  (In the normal case of the type 
being declared in a library package or the main program, read never.)

The other potential problem is that your Unbounded_String use could be 
fragmenting the heap.  Unfortunately the way to fix/test this is to 
allocate everything else from some non-default heap.  If you have only a 
few such types it should be easy enough to give each its own heap with a 
specified size, but if you have lots of dynamically allocated types 
using non-default heaps can get old fast.

Incidently, it sounds like Bounded_String is probably the right solution 
for your problem.  If it is possible to put a reasonable limit on the 
size of the strings nested inside other dynamic types, this should solve 
your problem--and result in faster code.

-- 
                                           Robert I. Eachus

"The war on terror is a different kind of war, waged capture by capture, 
cell by cell, and victory by victory. Our security is assured by our 
perseverance and by our sure belief in the success of liberty." -- 
George W. Bush