Xref: utzoo comp.lang.c:26948 comp.lang.misc:4471
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!mephisto!mcnc!ecsvax.uncecs.edu!utoddl
From: utoddl@uncecs.edu (Todd M. Lewis)
Newsgroups: comp.lang.c,comp.lang.misc
Subject: Re: C strongly typed?
Message-ID: <1990Mar15.133044.18600@uncecs.edu>
Date: 15 Mar 90 13:30:44 GMT
References: <259@eiffel.UUCP) <1990Mar1.172526.28683@utzoo.uucp) <849@enea.se) <1990Mar7.182230.5517@utzoo.uucp) <862@enea.se> <39941@ism780c.isc.com> <3744@tukki.jyu.fi> <3965@nmtsun.nmt.edu> <6475@bd.sei.cmu.edu>
Organization: UNC Educational Computing Service
Lines: 17

In article <6475@bd.sei.cmu.edu> firth@sei.cmu.edu (Robert Firth) writes:
>Well, I know of a minor programming language that allows one to
>achieve most of what is required at a fairly low cost in language
>feature overhead.  The concepts and their rationale are explained
>in the "Rationale for the Design of the Ada programming language",
>sections 7.2 and 7.3.  Examples there of types with implied units
>are FRANC and MARK, DOLLAR and CENT, LENGTH and AREA.  You might
>want to look it up.

Hey, this sounds really neat.  Tell me, how does the rationale
deal with keeping the conversions from FRANCs to MARKs to DOLLARs
and CENTs?  I've been using a file with the conversion factors
in it for my own stuff, but that's always seemed just a little
too cavalier for my tastes, what with these values changing by 
the second in the real world.  I'm glad to see the solution
so well worked out that it becomes part of the rationale for 
designing a language!  Wow!