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-Thread: 103376,eafb0c0f59b030c X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!postnews.google.com!i42g2000cwa.googlegroups.com!not-for-mail From: "Lucretia" Newsgroups: comp.lang.ada Subject: Re: Event mechanisms for GUI's Date: 26 Sep 2006 23:21:25 -0700 Organization: http://groups.google.com Message-ID: <1159338085.495558.286500@i42g2000cwa.googlegroups.com> References: <3egSg.208528$1i1.141541@attbi_s72> NNTP-Posting-Host: 62.56.75.133 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1159338091 9511 127.0.0.1 (27 Sep 2006 06:21:31 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 27 Sep 2006 06:21:31 +0000 (UTC) In-Reply-To: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060903 Firefox/1.5.0.5,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: i42g2000cwa.googlegroups.com; posting-host=62.56.75.133; posting-account=G-J9fgwAAADgpzBiEyy5tO4f8MX5fbpw Xref: g2news2.google.com comp.lang.ada:6768 Date: 2006-09-26T23:21:25-07:00 List-Id: Jeffrey R. Carter wrote: > tmoran@acm.org wrote: > >> There's nothing wrong with case statements. They're very clear and easy > > In small quantity, yes. But many-branched, nested, case statements with [snip] > > dispatching call on When_Left_Button_Down(The_Clicked_Window) is in effect > > a succinct abbreviation for a case statement on the type of Window, > > implemented efficiently and without forgetfullness or typing errors, > > automatically by the compiler. > > Sacrificing ease of reading for ease of writing. Well, this is actually another part of Ada's design, the ability to write *correct* code, by using nested case/if statements can introduce errors. That would be the wrong way to go. Also, I'd like this not to go off-topic too early. Thanks, Luke.