Re: Problem with Unbounded Strings

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

On Sat, 5 Dec 2015 02:22:36 -0800 (PST), Laurent wrote:

>>No, the strategy is to pass lines or other parts of the >message further 
>>instead of accumulating it in the memory. Instead of this >"hamster" design 
>>I would do something like: 
> 
>>   Buffer : String (1..Size); -- Input is accumulated here 
> 
> Eh isn't that a contradiction? There is still a buffer

For just one line. You are trying to merge an unlimited number of. This is
a waste of resources and potential problem with latencies. For example,
modern poorly designed text editors load whole file first. What happens
when the file is large? The editor gets blocked.

> and it is even combined with those evil accesses!?

Access is needed for the mix-in pattern. It is a language design bug that
the discriminant must be an access even if the target is a by-reference
type. Instead of mix-in you can pass stream to each call explicitly, which
is not better. Or you can pack the access type into a handle type. BTW,
Unbounded_String is just that, a handle type wrapping some access to the
dynamically allocated body.

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