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: a07f3367d7,57f8540942f8e060 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!news4.google.com!news2.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx01.iad01.newshosting.com!209.197.12.246.MISMATCH!nx02.iad01.newshosting.com!newshosting.com!198.186.194.250.MISMATCH!news-xxxfer.readnews.com!news-out.readnews.com!transit4.readnews.com!panix!bloom-beacon.mit.edu!newsswitch.lcs.mit.edu!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Initialization and Finalization of limited object "returned" by a function Date: Fri, 12 Feb 2010 14:07:30 -0500 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <75a9f860-ad3c-49a0-b2a1-a8f1386e6ff6@x10g2000prk.googlegroups.com> <2801be3a-afd6-4d14-ad7f-feb23a511f02@a5g2000yqi.googlegroups.com> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: pcls6.std.com 1266001637 27800 192.74.137.71 (12 Feb 2010 19:07:17 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Fri, 12 Feb 2010 19:07:17 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:1AqXjwbfqvOrLJUmgreh2IDKegw= Xref: g2news1.google.com comp.lang.ada:9181 Date: 2010-02-12T14:07:30-05:00 List-Id: "(Hibou57) Yannick Duch�ne" writes: > Le Fri, 12 Feb 2010 16:10:19 +0100, Robert A Duff > a �crit: >>>> Extended return statements are not so important for nonlimited types, >>>> but they do come in handy in that case, too. >>> While this may be useful, if it was, to have a way to return none- >>> limited as built-in-place, for efficiency purpose (just suggesting >>> this be to investigated, I do not assert this could surely be done >>> like this and as-is). >> >> Again, extended returns do NOT cause build-in-place. >> For non-limited, the compiler may choose build-in-place >> for efficiency in some cases. >> >> - Bob > It was a suggestion... You mean a suggestion for the language, or a suggestion for a compiler optimization? If the latter, well, I think the compiler ought to do the optimization whether or not the code uses extended return. >...(you seems to really be afraid of this possible > confusion) Well, yeah, lots of people seem to think that extended return does much more than it does. I'm just trying to help avoid that confusion. ;-) - Bob