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.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,791ecb084fdaba75 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-09-29 02:16:49 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!panix!cmcl2!thecourier.cims.nyu.edu!thecourier.cims.nyu.edu!nobody From: dewar@cs.nyu.edu (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: Types with physical dimension Date: 28 Sep 1994 09:59:36 -0400 Organization: Courant Institute of Mathematical Sciences Message-ID: <36bss8$79@gnat.cs.nyu.edu> References: NNTP-Posting-Host: gnat.cs.nyu.edu Date: 1994-09-28T09:59:36-04:00 List-Id: "What do Ada programmers do to guard against dimensional errors" Probably not much, because in practice, at least in my experience, such errors are rare, although they are an obvious target for theoretical discussions. Using private types is of course the appropriate way to do things in Ada 83. In Ada 9X, abstract operations can be used to eliminate unwanted operations.