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 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8179c5e594eb425e X-Google-Attributes: gid103376,public From: stt@houdini.camb.inmet.com (Tucker Taft) Subject: Re: Contraint error Date: 1998/10/11 Message-ID: #1/1 X-Deja-AN: 399950110 Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.camb.inmet.com References: <3620BB8F.2973CE00@phoenix.net> Organization: Intermetrics, Inc. Newsgroups: comp.lang.ada Date: 1998-10-11T00:00:00+00:00 List-Id: Renwick Preston (rpreston@phoenix.net) wrote: : My program just started creating a constraint error after I added some Boolean variables : with code that used those variables. I'm thinking that the way I'm using them is what is : causing the problem. : I first initialize them all to False. In my program I have a case statement with some code for : each case. Here is a snippet: : case Month : when June : If June_Completed then <- Line added : < some code here> : June_Completed := True; <- Line added : End if; <- Line added : : end case; : Everything worked fine until I added the lines marked. : What could be the problem? The added lines look a bit suspicious, since you are setting "June_Completed" to True only if it is already True (your indenting leaves a bit to be desired ;-). In any case, to really diagnose this problem, the reader will need a complete but minimal test case which shows the problem. A "snippet" will rarely be enough for someone to figure out what is going wrong. : Ren -- -Tucker Taft stt@inmet.com http://www.inmet.com/~stt/ Intermetrics, Inc. Burlington, MA USA An AverStar Company