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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5997b4b7b514f689 X-Google-Attributes: gid103376,public From: Mats Weber Subject: Re: Reading a line of arbitrary length Date: 1997/02/14 Message-ID: <330481C5.5096@elca-matrix.ch>#1/1 X-Deja-AN: 218962766 References: <5ds40o$rpo@fg70.rz.uni-karlsruhe.de> <33032AE2.666F@mds.lmco.com> <33037A74.44AF@mds.lmco.com> Content-Type: text/plain; charset=us-ascii Organization: ELCA Matrix SA Mime-Version: 1.0 Reply-To: Mats.Weber@elca-matrix.ch Newsgroups: comp.lang.ada X-Mailer: Mozilla 3.01 (Macintosh; I; PPC) Date: 1997-02-14T00:00:00+00:00 List-Id: > Probably first will be stack space, tasks tend to be limited in > stack by about 100_000 bytes (I realize this can be adjusted). > A problem will occur when the catenation result is stored temporarily > on the stack because there won't be enough stack space to save it. OK. > Assuming this is fixed, the next problem will occur when heap space > is exhausted, probably around 1_000_000 bytes. This is because both > Str1.all and Str2.all must exist for a short period together meaning > that 2 megabytes of heap will be in use at one time. Since tasks > tend to have their own heap allocations, I'm predicting a > Storage_Error exception will occur. Wrong, the heap is generally global with respect to tasks, and it has to be that way in this case because the type String_Access is a global access type, potentially visible from any task.