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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,92c39a3be0a7f17d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-03-13 16:37:28 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!nntp.cs.ubc.ca!freenix!wanadoo.fr!opentransit.net!news.tele.dk!small.news.tele.dk!130.240.42.8!luth.se!psiuk-p2!psiuk-p3!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Future with Ada Date: Wed, 13 Mar 2002 09:15:05 -0500 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: References: <3C7B0B13.3080003@worldnet.att.net> <3C7D1C89.2000803@home.com> <3C7E7CAD.7070504@mail.com> <3C7FB9D2.D9C6E055@boeing.com> <3C81DF1F.9000503@mail.com> <3C83A112.6080302@mail.com> <3C84223C.A356F466@adaworks.com> <3C853A04.34826F39@despammed.com> <3C8D0D70.BB09F3DA@despammed.com> <3C8F4571.3BE24266@brighton.ac.uk> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1016028906 19311 136.170.200.133 (13 Mar 2002 14:15:06 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 13 Mar 2002 14:15:06 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:21177 Date: 2002-03-13T14:15:06+00:00 List-Id: "John English" wrote in message news:3C8F4571.3BE24266@brighton.ac.uk... > > I think I'd be tempted to use an array of access-to-procedures here. > That would certainly be an interesting approach and one that might greatly simplify the code. But I'd imagine it might not work well in all cases - where the branches might have common behavior for some set of the enumerals, but with slight variations with specific cases, or where the procedure calls needed different parameter lists, or any number of other things like that. The technique you suggest hadn't occurred to me & I could see it as useful and probably a good idea for a lot of cases. I just wouldn't imagine it totally eliminates all instances wherein one might have a fairly long case statement and that being a "good" implementation of the solution. MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/