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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: some trivial questions? Date: Mon, 20 Nov 2017 16:03:37 -0600 Organization: JSA Research & Innovation Message-ID: References: <6a5368c5-f015-4dcb-9291-e77b40fa1bf1@googlegroups.com> Injection-Date: Mon, 20 Nov 2017 22:03:37 -0000 (UTC) Injection-Info: franka.jacob-sparre.dk; posting-host="rrsoftware.com:24.196.82.226"; logging-data="9069"; mail-complaints-to="news@jacob-sparre.dk" X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246 Xref: feeder.eternal-september.org comp.lang.ada:49021 Date: 2017-11-20T16:03:37-06:00 List-Id: "Dmitry A. Kazakov" wrote in message news:ouotuh$1ig3$1@gioia.aioe.org... > On 2017-11-18 02:14, Randy Brukardt wrote: ... >> Changing names of overloadable things is not a maintenance hazard unless >> the >> things have the exact same profile. (And that's a problem by any >> definition, >> having two identical entities with different meanings.) > > And if they are not overloadable I still can use long names. Use-clause > makes nothing worse than already is. Giving things junk names to avoid name conflicts is more evil than even package use clauses. ;-) See the bogus naming conventions of C systems where encoded type names are jammed into other things. That makes it all the harder to model the problem space (rather than the solution space). >> An alternative fix for this problem would be to make more things >> (preferably >> all things) overloadable. But that would cause some existing Ada code to >> silently change meaning, which is considered unacceptable. (It also would >> require some sort of meta-types, which I'd rather not try to get into, >> but >> that's a detail.) So it's not going to happen for Ada. > > Sure, nothing useful going to happen for Ada. I agree that this is annoying. The problem is that an incompatible Ada would be starting over from scratch (as existing libraries would not be usable), and whether such a thing could get traction (and get new versions of GTK and Claw and Dmitry's libraries, and so on.) is unknown. If it didn't get traction, it would be of little practical interest - and a lot of work. Randy.