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,3abdaa39e1c27f49
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!news.glorb.com!cyclone1.gnilink.net!gnilink.net!wns13feed!worldnet.att.net!attbi_s53.POSTED!53ab2750!not-for-mail
From: tmoran@acm.org
Newsgroups: comp.lang.ada
Subject: Re: Discriminant computation problem
References: <2vsns5F2p6vbpU1@uni-berlin.de>
X-Newsreader: Tom's custom newsreader
Message-ID: <aVamd.100382$R05.30042@attbi_s53>
NNTP-Posting-Host: 67.161.24.234
X-Complaints-To: abuse@comcast.net
X-Trace: attbi_s53 1100561094 67.161.24.234 (Mon, 15 Nov 2004 23:24:54 GMT)
NNTP-Posting-Date: Mon, 15 Nov 2004 23:24:54 GMT
Organization: Comcast Online
Date: Mon, 15 Nov 2004 23:25:04 GMT
Xref: g2news1.google.com comp.lang.ada:6212
Date: 2004-11-15T23:25:04+00:00
List-Id: <comp.lang.ada>

Another approach is to make the type controlled, then have the
Initialize routine do the size calculations based on the discriminant
and call an allocator for the actual data.  Finalize then deallocates
the data, of course.

>I've found this problem to be a pain myself, in the past. You just just have
>to 'program around it'.
  Yes.