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=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.236.28.102 with SMTP id f66mr10505501yha.31.1421379883481; Thu, 15 Jan 2015 19:44:43 -0800 (PST) X-Received: by 10.140.22.48 with SMTP id 45mr261252qgm.5.1421379883362; Thu, 15 Jan 2015 19:44:43 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!v8no1346660qal.1!news-out.google.com!n9ni489qai.0!nntp.google.com!v8no1346658qal.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 15 Jan 2015 19:44:43 -0800 (PST) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=50.138.174.211; posting-account=AvekzAoAAABj-TclKcOWQmXwA49MFPGX NNTP-Posting-Host: 50.138.174.211 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <121014ba-309c-45a0-950a-20b5b15210c5@googlegroups.com> Subject: Generics crash course From: John Smith Injection-Date: Fri, 16 Jan 2015 03:44:43 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Received-Bytes: 1478 X-Received-Body-CRC: 761676500 Xref: news.eternal-september.org comp.lang.ada:24588 Date: 2015-01-15T19:44:43-08:00 List-Id: Hello, I'm going through the wikibook about Ada. It has this example when it comes to generics: http://wikibook-ada.sourceforge.net/html/Algorithms__binary_search__adb.htm What I don't understand is from lines 12 to 21. How does this work exactly? I mean, does this somehow "connect" the overloaded < operator to the Search procedure? Also, on line 53, if this code is ever reached, then this means that the entire application will stop executing, yes? The procedure won't just return to the caller.