From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,23ace43a488fab29
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 30 Nov 2005 18:14:31 -0600
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <dkv059$hit$1@netnews.hinet.net> <dl1kho$t76$1@netnews.hinet.net>
 <1fxvr41a6cj64$.1cin7p2ro7ua2$.dlg@40tude.net>
 <dl20qv$4ku$1@netnews.hinet.net> <5h23dl2sire9.hk0tsc5bj1ot.dlg@40tude.net>
Subject: Re: function "&" for strings type cause memory problem.
Date: Wed, 30 Nov 2005 18:18:38 -0600
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4952.2800
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4952.2800
Message-ID: <56qdnTk6D-j63RPeRVn-iA@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-cYVF6GvIVc4WxuosdjkyuH/puv3GdASM2TsRrpg3aD4PkivtqkJNi0OYt2P06khaBjQKUbq43jpcK0p!ZS3pAENioksEaiLxkvL2ejeMxCHqae6sUP13RA5nh9Z8NnduuVnwQ0gRGWnNTwl6YUvTMhXHYPua
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.32
Xref: g2news1.google.com comp.lang.ada:6698
Date: 2005-11-30T18:18:38-06:00
List-Id: <comp.lang.ada>

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message
news:5h23dl2sire9.hk0tsc5bj1ot.dlg@40tude.net...
> On Fri, 11 Nov 2005 19:55:05 +0800, bubble wrote:
> > may be I need rethink the strategies of string types.
> > and the ARM do not say string merge may raise error when lack of stack
> > space.
>
> Storage_Error is an "implied" exception.

Right. See 11.1(6) in the ARM. Note that 11.1(6) says "any construct"; that
means *anything* may raise Storage_Error, even "null;" or "1 + 1".
Storage_Error is never wrong, at most it is unfriendly.

                                     Randy.