I think the old saying goes garbage in garbage out. range checking should probablly catch this sort of stuff but that has a high performance penalty and is therefore usually disabled.
At the end of the day if you force out of range data into your booleans then its your problem. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Jesus Reyes > Sent: 30 December 2004 21:49 > To: FPC developers' list > Subject: RE: [fpc-devel] compiler bug? > > > --- peter green <[EMAIL PROTECTED]> escribiˇ: > > you are forciblly putting an out of range value in a variable what > > do you > > expect to happen? > > > > > > > > Of course the program was made to do that evident, but what happen > when you find a procedure, for example: > > procedure doAorB(value: boolean); > begin > case value of > true: doA; > false: doB; > end; > end; > > one might think either doA or doB will executed, but the reality is > that sometimes neither doA or doB will do. > > > > > _________________________________________________________ > Do You Yahoo!? > La mejor conexiˇn a internet y 25MB extra a tu correo por $100 al > mes. http://net.yahoo.com.mx > > _______________________________________________ > fpc-devel maillist - email@example.com > http://lists.freepascal.org/mailman/listinfo/fpc-devel _______________________________________________ fpc-devel maillist - firstname.lastname@example.org http://lists.freepascal.org/mailman/listinfo/fpc-devel