Re: Announce: Grace project site operational

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

Hard to say. Depends somewhat on the app. I might create a whole separate
floating point type for electrical calculations where I intend to mix volts
and amps and ohms. That would keep it separate from whatever other
calculations might be going on. In this case, I don't know that ranges would
figure into it - conceptually at least the calculations can go to +/-
infinity, so any subtype with a range constraint might be strictly for
hardware concerns. Unless, of course, you're getting the values from some
real world source with real world limitations.

My point is that you have to give some careful thought to creating types and
that doing it for every identifiable unique item is not usually smart.
Decisions should be made with some sensitivity as to what the types
represent and how much mixing together of the different types is needed. I'd
love to see some textbook on computer philosophy that attempted to describe
how to make those decisions, but I've not run into any.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com


"Preben Randhol" <randhol+abuse@pvv.org> wrote in message
news:slrnadq9vg.21p.randhol+abuse@kiuk0156.chembio.ntnu.no...
>
> Say you instead defined them as subtypes of Float (for this example)
> with allowed ranges for each type, would that be an enhancement over
> only using Float?
>