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,5f3fcf3eb242e4c1 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-07-19 14:37:22 PST Path: archiver1.google.com!newsfeed.google.com!postnews1.google.com!not-for-mail From: dewar@gnat.com (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: casecrash: language lawyers: C'mon! Date: 19 Jul 2001 14:37:22 -0700 Organization: http://groups.google.com/ Message-ID: <5ee5b646.0107191337.14b7a14a@posting.google.com> References: <9j1cpn$bis$1@infosun2.rus.uni-stuttgart.de> NNTP-Posting-Host: 208.224.77.203 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 995578642 9051 127.0.0.1 (19 Jul 2001 21:37:22 GMT) X-Complaints-To: groups-support@google.com NNTP-Posting-Date: 19 Jul 2001 21:37:22 GMT Xref: archiver1.google.com comp.lang.ada:10280 Date: 2001-07-19T21:37:22+00:00 List-Id: Peter Hermann wrote in message news:<9j1cpn$bis$1@infosun2.rus.uni-stuttgart.de>... GNAT says here: casecrash.adb:6:02: "H" conflicts with declaration at line 2 > Why on earth should I accept this rule in this case? Because, very deliberately, obverloading is restricted to function and procedure names (enumeration literals are function names from the point of view of this rule). We definitely do NOT want to allow overloading of variable names, since it is impossible to see how this could improve readability of programs. There is no excuse for reusing H in the sample program you gave. > Topic for Ada2005? Nope. I see no reason for changing a well designed and well founded rule here. This rule is clearly stated, and well understood by Ada programmers. There is no basis for change.