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,487310d7e1471eac
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!wns14feed!worldnet.att.net!attbi_s22.POSTED!53ab2750!not-for-mail
From: "Jeffrey R. Carter" <spam.jrcarter.not@acm.nospam.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: parent package referring to child
References: <1191997397.865251.322480@d55g2000hsg.googlegroups.com>
 <1192095936.309410.62410@k79g2000hse.googlegroups.com>
In-Reply-To: <1192095936.309410.62410@k79g2000hse.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <bxCPi.129728$Xa3.92874@attbi_s22>
NNTP-Posting-Host: 12.201.97.213
X-Complaints-To: abuse@mchsi.com
X-Trace: attbi_s22 1192162503 12.201.97.213 (Fri, 12 Oct 2007 04:15:03 GMT)
NNTP-Posting-Date: Fri, 12 Oct 2007 04:15:03 GMT
Organization: AT&T ASP.att.net
Date: Fri, 12 Oct 2007 04:15:03 GMT
Xref: g2news2.google.com comp.lang.ada:2435
Date: 2007-10-12T04:15:03+00:00
List-Id: <comp.lang.ada>

george@gentoo.org wrote:
> I have been faced with just such a problem, when writing a library to
> access abf files (a special data format used by the most common
> software in electrophysiology). I needed to define a record type with
> near a thousand fields (beat you here ;)) and did not want to put it
> all into the single spec. My solutions was exactly redesign, or rather
> I designed it from ground up to be appropriately split between the
> parent and child modules.

This perhaps makes sense for this specific situation (files with a 
number of different layouts, based on the data at the beginning of the 
file), but I don't understand this attitude in general. Given the basic 
package structure

package P is
    type T is ...

    procedure P1 (V : [mode] T ...);
    procedure P2 (V : [mode] T ...);
    ... -- Additional operations as needed.
end P;

why do some seem to think it's OK to have T declared here if the 
declaration is short, but not if it is (perceived to be) long? It's the 
same concept in both cases and should, I think, be implemented in a 
uniform way.

-- 
Jeff Carter
"You tiny-brained wipers of other people's bottoms!"
Monty Python & the Holy Grail
18