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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1dd28d5040ded1f8 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-05-17 09:44:10 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Announce: Grace project site operational Date: 17 May 2002 12:43:23 -0400 Organization: NASA Goddard Space Flight Center (skates.gsfc.nasa.gov) Message-ID: References: <4519e058.0205140718.3ddb1b2a@posting.google.com> <3CE15D0A.3050100@mail.com> <3ce21f37$1@pull.gecm.com> <3CE2AB7E.AD4A9956@san.rr.com> <3CE2B842.7060705@mail.com> <3CE2F4E3.DABF19D7@san.rr.com> <3CE3D578.901D6C43@san.rr.com> <3CE52B0B.C6978AF@san.rr.com> NNTP-Posting-Host: anarres.gsfc.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: skates.gsfc.nasa.gov 1021654227 23063 128.183.220.71 (17 May 2002 16:50:27 GMT) X-Complaints-To: usenet@news.gsfc.nasa.gov NNTP-Posting-Date: 17 May 2002 16:50:27 GMT User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.ada:24291 Date: 2002-05-17T16:50:27+00:00 List-Id: Darren New writes: > I was thinking more like saying > kilo=1000 > and automatically getting kilograms, kilometers, kilomiles, etc. hmm. I'd stick to explicitly requested types. The point of the autogenerated package is to keep it as small as possible. > Also foot=0.3*meter or some such, and then automatically getting > foot/second from meter/second. No non-SI please :). Actually, there's no reason for the Auto_Unit tool to restrict the names of the types in any way. I don't think I'd use something like 'foot = 0.3 * meter', but I can see some applications might want it. > > > Dealing with things like "area=length*length*length" as another > > > example. > > > > Yes, we'd want to define secondary types in terms of primary types. > > area=length*length is easy. volume=length*length*length is harder, because > you would need to automatically generate the intermediate type involved in > the volume. I.e., if "area" weren't defined, how would you define operator > "*"(l,r : length)? Good point. I would have automatically generated type names like "Meters_Squared", and define "Area" as a subtype of Meters_Squared. Then Volume is a subtype of Meters_Cubed. That way, you get the user's secondary units defined in terms of the user's primary units. -- -- Stephe