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,730a7c3edfcae91f X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-11-03 06:24:56 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!uio.no!ntnu.no!not-for-mail From: Preben Randhol Newsgroups: comp.lang.ada Subject: Re: Macks - adding unit constants? Date: Mon, 3 Nov 2003 14:24:55 +0000 (UTC) Organization: PVV Message-ID: References: <3F8514EC.8050702@crs4.it> <3F904FD6.7040301@crs4.it> <3FA63FED.9050705@crs4.it> NNTP-Posting-Host: kiuk0156.chembio.ntnu.no X-Trace: tyfon.itea.ntnu.no 1067869495 6922 129.241.83.82 (3 Nov 2003 14:24:55 GMT) X-Complaints-To: usenet@itea.ntnu.no NNTP-Posting-Date: Mon, 3 Nov 2003 14:24:55 +0000 (UTC) User-Agent: slrn/0.9.8.0 (Linux) Xref: archiver1.google.com comp.lang.ada:1979 Date: 2003-11-03T14:24:55+00:00 List-Id: On 2003-11-03, Jacob Sparre Andersen wrote: > Preben Randhol wrote: >> On 2003-10-17, Jacob Sparre Andersen wrote: > >>>It is very impractical to have to remember to write "0.000_86" and not >>>"0.86", when you put constants in your code. I prefer to have to write >>>"0.000_86 * m" (or "0.86 * mm") so there is an explicit conversion from >>>nondimensional to dimensional units. Since this preference is rather >>>strong, I have decided to use a hand-written units package for this project. >> >> why not 8.6E-4 ? As 0.000_86 etc.. where you can get the 0's wrong. :-) > > As opposed to what? It still doesn't tell which units we are working > in. Dimensionless numbers should not be able to suddenly become > dimensioned numbers without som kind of explicit conversion. well you can write 8.6E-4 * m Preben -- "Saving keystrokes is the job of the text editor, not the programming language."