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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,60e2922351e0e780 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-11-06 16:22:42 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!cyclone-sf.pbi.net!216.218.192.242!news.he.net!newsfeed1.easynews.com!easynews.com!easynews!small1.nntp.aus1.giganews.com!border1.nntp.aus1.giganews.com!intern1.nntp.aus1.giganews.com!nntp.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail NNTP-Posting-Date: Thu, 06 Nov 2003 18:22:40 -0600 Date: Thu, 06 Nov 2003 19:22:39 -0500 From: "Robert I. Eachus" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Clause "with and use" References: <3FA50083.10709@noplace.com> <3FA777E9.4030605@noplace.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: NNTP-Posting-Host: 24.34.214.193 X-Trace: sv3-JpJmglPJbuZGvEjWRBg08+wU01fivSDTZe9CGTfNNi+p0YMgP3IE2uvgzkFTPjcuKz4ds7bV8m1gRc9!PvnGKAv90JVSJBQUZgU96OjdDwLaNkHgNscJ7S5Kh6EPFYyJ1BGC5OZ2PD7AUg== X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.1 Xref: archiver1.google.com comp.lang.ada:2176 Date: 2003-11-06T19:22:39-05:00 List-Id: Martin Dowie wrote: > So, Russ, have read AI-318? Do you still think that "+=",etc is > still necessary, now there is a mechanism to avoid that extra deep > copy for things like matrices/vectors? For the record, AI-318 as written applies to limited and unlimited types. But the current ARG discussion has determined that there are significant implementation problems with requiring this feature to be used with non-limited return types. I don't know what the final resolution will be. It could either allow implementations to do the "extra" copy when the type is non-limited, or involve a notation that made it clear in the subprogram declaration that this style of return is being used. Sorry this is one of those cases where the ARG has to be concerned about the "real" issues of language maintenance. (The final resolution might be to permit the notation for all cases, and require the "generate return value in place" behaviour for limited types only. That way a compiler could do the optimization if it can tell at the point of any calls that the function body is written this way.) -- Robert I. Eachus 100% Ada, no bugs--the only way to create software.