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_20,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: Richard D Riehle <laoXhai@ix.netcom.com>
Subject: Re: Simple Case Study in Types. Chords.
Date: 1999/12/04
Message-ID: <829qci$ctj$1@nntp8.atl.mindspring.net>#1/1
X-Deja-AN: 556421222
References: <3831283B.20807F08@interact.net.au>
 <x7vogcpowyx.fsf@pogner.demon.co.uk>
Organization: MindSpring Enterprises
X-Server-Date: 4 Dec 1999 01:22:26 GMT
Newsgroups: comp.lang.ada
Date: 1999-12-04T01:22:26+00:00
List-Id: <comp.lang.ada>

In article <x7vogcpowyx.fsf@pogner.demon.co.uk>,
	Simon Wright <simon@pogner.demon.co.uk> wrote:

>  -- 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;

This works fine for an equal-tempered scale such as that on a
pianoforte or fretted string instrument.  One of the beauties of
the violin family is the ability to play the subtle difference
between, say, an  G Sharp and an A Flat.  Of course, most of us
are accustomed to thinking that the sharp form of one note exactly
corresponds to the flat form of the next ascending note, so the
distinction is often unimportant.  There is also the problem of
Asian tones, some of which are slightly off from the Pythagorean
model.  

Richard Riehle