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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,3d0afc9a32541780,start
X-Google-Attributes: gid103376,public
From: Pascal MALAISE <malaise@magic.fr>
Subject: Task storage_size on task types with gnat
Date: 1998/12/13
Message-ID: <3673E6EF.7EDFBDB0@magic.fr>#1/1
X-Deja-AN: 422217316
Content-Transfer-Encoding: 7bit
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@ulysse.magic.fr
X-Trace: ulysse.magic.fr 913565424 597 127.0.0.1 (13 Dec 1998 16:10:24 GMT)
Organization: Magic On Line
Mime-Version: 1.0
NNTP-Posting-Date: 13 Dec 1998 16:10:24 GMT
Newsgroups: comp.lang.ada
Date: 1998-12-13T16:10:24+00:00
List-Id: <comp.lang.ada>

I have a task which needs a large (at least more than the deafult)
stack.
-- In fact, it dynamically instanciates a generic.

With gnat 3.10p (on linux) I cannot specify my task storage_size:

task STUFF is
...
end STUFF;
for STUFF'STORAGE_SIZE use 4*1024*1024;
--> storage size cannot be given for "STUFF"

But if I use a task type:
task type STUFF_T is
...
end STUFF_T;
for STUFF_T'STORAGE_SIZE use 4*1024*1024;
STUFF : STUFF_T;

It works OK.


Does anyone know - why the first approach is refused?
                 - a way to avoid a task type (I don't realy mind
though).
--
Pascal MALAISE
(priv) mailto:malaise@magic.fr
(prof) mailto:malaise@fr.airsysatm.thomson-csf.com