Re: Using generic package to store and retrieve string data

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2016-10-08 11:01, Simon Wright wrote:
> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
>
>> On 2016-10-08 01:11, Jeffrey R. Carter wrote:
>>
>>> If your Strings may have differing lengths, then you should either
>>> use Unbounded_String or one of the indefinite containers.
>>
>> Unbounded_String is not self-contained. Normally it is important for a
>> stack and containers to have this.
>
> It looks self-contained to me. (I mean, if I 'with
> Ada.Strings.Unbounded' I can pretty-much use it without further ado;
> just a little complication with translating to/from String).

The string body will be allocated in the pool not on the stack. That, 
not always, but usually defeats the purpose of having a stack of strings.

>> IMO, the best way to implement an indefinite elements LIFO is on top
>> of a custom memory pool.
>
> I doubt this is going to help the OP.

My comment was addressed to Jeffrey's about indefinite elements. (The OP 
wanted fixed strings)

A stack of indefinite objects sitting on the stack would require either 
custom allocation or custom serialization (e.g. using stream 
attributes). In both cases it is important to grow the stack towards 
lesser addresses/indices to have access to the beginning of the last 
element.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de