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-Thread: 103376,672b169dc220673a X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.191.225 with SMTP id hb1mr13912194pbc.5.1337347920559; Fri, 18 May 2012 06:32:00 -0700 (PDT) Path: pr3ni1308pbb.0!nntp.google.com!news2.google.com!newsfeed2.dallas1.level3.net!news.level3.com!bloom-beacon.mit.edu!newsswitch.lcs.mit.edu!nntp.TheWorld.com!.POSTED!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Vector (container) initialization: the schizophrenic ampersand Date: Fri, 18 May 2012 09:31:59 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <10616734.43.1337286031745.JavaMail.geo-discussion-forums@vbjy7> <70510fa1-e554-44a7-9364-e745674c1bda@googlegroups.com> <28845c63-b06c-4ac2-b5d5-e408c0ff4b7f@googlegroups.com> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 X-Trace: pcls6.std.com 1337347920 14019 192.74.137.71 (18 May 2012 13:32:00 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Fri, 18 May 2012 13:32:00 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:Svo9PNy4MsSmXKvuGCEzHehW6+4= Content-Type: text/plain; charset=us-ascii Date: 2012-05-18T09:31:59-04:00 List-Id: Marius Amado-Alves writes: > Adam is right: it is confusion with the predefined "&" for arrays, when the elements are arrays. (But the compiler error messages indicate undecision only between the two Vectors "&" functions.) So my new solution is > > function "+" (L : My_Vectors.Vector; R : My_Element_Type) > renames My_Vectors."&"; > > function "+" (L, R : My_Element_Type) > renames My_Vectors."&"; > > V : My_Vectors.Vector := Element1 + Element2 + Element3; > > A bit less inelegant. > > /* But more than parenthesis or T'(...) in my view. */ You mean more inelegant, or more elegant? IMHO, a qualified expression is the elegant (and usual) way to resolve ambiguities. Renaming "&" to be "+" just seems confusing, to me. - Bob