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,LOTS_OF_MONEY autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,27b7b39155b8a0d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-28 19:41:52 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: dewar@gnat.com (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: Generics not overloadable Date: 28 Nov 2001 19:41:52 -0800 Organization: http://groups.google.com/ Message-ID: <5ee5b646.0111281941.2620b70a@posting.google.com> References: NNTP-Posting-Host: 205.232.38.14 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1007005312 19744 127.0.0.1 (29 Nov 2001 03:41:52 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 29 Nov 2001 03:41:52 GMT Xref: archiver1.google.com comp.lang.ada:17146 Date: 2001-11-29T03:41:52+00:00 List-Id: Ted Dennison wrote in message news:... > It annoyed me too when I discovered it I find it hard to believe that it would be easy to come up with an example where it would help the reader to name two visible generic units with the same name. Indeed, far too often overloading in Ada is misused to save the bother of thinking of different names. You should only overload by deliberate decision where it makes reading clearer, otherwise overloading can confuse a reader.