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.6 required=5.0 tests=BAYES_40,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,fd26676e94ec9b24 X-Google-Attributes: gid103376,public From: Simon Wright Subject: Re: Simple Case Study in Types. Chords. Date: 1999/11/20 Message-ID: #1/1 X-Deja-AN: 551071103 X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98 References: <3831283B.20807F08@interact.net.au> X-Trace: news.demon.co.uk 943139031 nnrp-09:258 NO-IDENT pogner.demon.co.uk:158.152.70.98 Organization: At Home Newsgroups: comp.lang.ada X-Complaints-To: abuse@demon.net Date: 1999-11-20T00:00:00+00:00 List-Id: G writes: > With the following code fragments, I am not > sure if I constructed the types in [Chord_Definition.ads] > such that they actually mean what I think they do. Since I don't know what you think they mean (!), may I just suggest > type Twelve_Tone is > -- Thirteen because that allows the octave. > (One, Two, Three, Four, > Five, Six, Seven, Eight, > Nine, Ten, Eleven, Twelve, Thirteen); > > type Chord_List is array (1..13) of Twelve_Tone; -- Assuming that no Chord ever spans more than an octave, we can -- represent a Chord by indicating the Notes present in it type Chord is array (Twelve_Tone) of Boolean;