On Wed, 17 Jul 2013 10:56:06 -0400, John Gilmore wrote: > >You need to keep two things in mind. Even very simple optimizers 1) >break off evaluation with the outcome FALSE as soon as an AND >component is found to be false, and 2) break off evaluation with the >outcome true as soon as an OR component is found to be true. > Subject to considering possible side effects of evaluating later components?
For some languages, such as C, it is a specification of the language that evaluation is broken off as soon as the result can be known in a left-to-right evaluation. This can be useful for intentionally suppressing side effects. For others (Pascal, IIRC), the behavior is left implementation-dependent. PL/I? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
