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.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,30df5a909ff1af4 X-Google-Attributes: gid103376,public From: Robert Dewar Subject: Re: Answering an Ada/COBOL Question Date: 1999/11/15 Message-ID: <80pd2g$8fg$1@nnrp1.deja.com>#1/1 X-Deja-AN: 548863102 References: <80hr16$5q2$1@nntp5.atl.mindspring.net> <382FA652.A72E4150@concentric.net> X-Http-Proxy: 1.0 x36.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Mon Nov 15 16:40:48 1999 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I) Date: 1999-11-15T00:00:00+00:00 List-Id: In article <382FA652.A72E4150@concentric.net>, Joseph P Vlietstra wrote: > For example, the following decision table: > A B C > T X X Action_1 > F T X Action_2 > F F T Action_3 > F F F Action_4 > can be implemented as: > if A then > Action_1; > elsif B then > Action_2; > elsif C then > Action_3; > else > Action_4; > end if; But this is a poor implementation because it overspecifies, precisely by not clearly indicating exactly what the don't care conditions are. One very serious problem with the elsif structure is precisely that you don't know if the ordering is critical or not. When it comes to modifying the conditions, this lack of information can be problematical. When we deal with conditions that are not exclusive, this problem always arises, and is one of the reasons that complex condiitonals are so hard to deal with in maintenance programming. Sent via Deja.com http://www.deja.com/ Before you buy.