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=0.7 required=5.0 tests=BAYES_00,MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,75a8a3664688f227 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-01-14 13:25:01 PST Path: supernews.google.com!sn-xit-02!supernews.com!news.gv.tsc.tdk.com!newsfeed.berkeley.edu!ucberkeley!nntp2.deja.com!nnrp1.deja.com!not-for-mail From: Robert Dewar Newsgroups: comp.lang.ada Subject: Re: Parameter Modes, In In Out and Out Date: Sun, 14 Jan 2001 21:10:56 GMT Organization: Deja.com Message-ID: <93t4kr$vec$1@nnrp1.deja.com> References: <3A57CD7F.2228BFD5@brighton.ac.uk> <938p3u$omv$1@nnrp1.deja.com> <93cagm$c1j$1@nnrp1.deja.com> <93e4e6$ucg$1@nnrp1.deja.com> <93encq$brm$1@nnrp1.deja.com> <93f6ar$m44$1@nnrp1.deja.com> <93flab$2mh$1@nnrp1.deja.com> <93fqau$6m2$1@nnrp1.deja.com> <93h9mo$bbm$1@nnrp1.deja.com> <93il87$iqo$1@nnrp1.deja.com> <93k6dv$qt6$1@nnrp1.deja.com> <93ko49$auq$1@nnrp1.deja.com> <93modu$36k$1@nnrp1.deja.com> <93n2co$alq$1@nnrp1.deja.com> <93q39q$oq0$1@nnrp1.deja.com> <93q6cd$r3k$1@nnrp1.deja.com> <3A6140CB.63EE9B8F@acm.org> <93sdcn$dr0$1@nnrp1.deja.com> <3A61EC64.A61FDF61@acm.org> NNTP-Posting-Host: 205.232.38.14 X-Article-Creation-Date: Sun Jan 14 21:10:56 2001 GMT X-Http-User-Agent: Mozilla/4.61 [en] (OS/2; U) X-Http-Proxy: 1.0 x57.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 X-MyDeja-Info: XMYDJUIDrobert_dewar Xref: supernews.google.com comp.lang.ada:4009 Date: 2001-01-14T21:10:56+00:00 List-Id: In article <3A61EC64.A61FDF61@acm.org>, Jeffrey Carter wrote: > Also, this guideline is apparent to application developers, > while ease of migration for Ada-83 vendors is not. Indeed! Actually that's a special case that ease (and realiability) of implementation are criteria that are not very visible (or easy to evaluate) from an application developer point of view. There are lots of things that would make life easier for a programmer that would not make implementors happy. A good example is overloading. The clean definition of overloading would simply be that for any expression if there is one interpretation, then its right, if there is more than one, it is wrong. Although that is the general spirit of the overloading rules, it turns out we have to make some nasty exceptions, and make some things illegal even though there is only one possible interpretation, to keep things reasonable :-) Sent via Deja.com http://www.deja.com/