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,1dd28d5040ded1f8 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-05-09 02:50:24 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.cwix.com!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Announce: Grace project site operational Date: 9 May 2002 04:50:21 -0500 Organization: LJK Software Message-ID: References: <3CD88FBD.4070706@telepath.com> <3CD91E31.1060004@telepath.com> <3CD94E63.3050607@mail.com> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1020937823 17719 192.135.80.34 (9 May 2002 09:50:23 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Thu, 9 May 2002 09:50:23 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:23759 Date: 2002-05-09T04:50:21-05:00 List-Id: In article , "Marin David Condic" writes: > I see the usefulness of different numeric types coming into play with items > that have very distinct usages. For example, if I get data from a pressure > transducer and a temperature sensor and an RPM sensor and they were all 16 > bit integers, I would want to make sure I didn't accidentally mix them up > because they all represent very different things with different units, etc. > There, I'd want separate types. But for a counter or index where typically > all I want to do is "for X in 1..Data_Structure_Size loop" I don't see a lot > of food value to be had by making all those unique types. > > I'd be hard pressed to come up with a rule as to when it requires a separate > type and when it can use one of the predefined types. It sort of feels like > "art" to me. I'd suggest that it gains importance as the numbers in question > get closer to modeling something in the "real world". The closer it gets to > "internal housekeeping", the less interest I have in creating unique types > for it. Is there no way a generic type parameter can have a default value ?