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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9cccf6ef6149fdaa X-Google-Attributes: gid103376,public From: "Matthew Heaney" Subject: Re: Operators -> unit analysis Date: 2000/01/05 Message-ID: <3873a70b_1@news1.prserv.net>#1/1 X-Deja-AN: 568780216 Content-transfer-encoding: 7bit References: <38620350.48F8FC08@gecm.com> <83u8l0$5i5$1@nnrp1.deja.com> <84rd2f$snm$1@nntp3.atl.mindspring.net> <84thof$9r3$1@nntp4.atl.mindspring.net> <387383D0.4EA02E95@earthlink.net> Content-Type: text/plain; charset="US-ASCII" X-Complaints-To: abuse@prserv.net X-Trace: 5 Jan 2000 20:18:19 GMT, 129.37.62.74 Organization: Global Network Services - Remote Access Mail & News Services Mime-version: 1.0 Newsgroups: comp.lang.ada Date: 2000-01-05T00:00:00+00:00 List-Id: In article , Hyman Rosen wrote: > Charles Hixson writes: >> And some good way to handle units. So that we could safely say things like: >> speed := 37.miles / 1.5.hours; > > There is already a very good way to handle units, without any runtime > overhead if you don't need to determine units dynamically. Yes, there is, by using type qualification: Speed := Miles'(37.0) / Hours'(1.5);