Short-circuit evaluation(minimal evaluation), or McCarthy evaluation denotes the semantics of some Boolean operators in some programming languages in which the second argument is executed or evaluated only if the first argument does not suffice to determine the value of the expression: when the first argument of the AND function evaluates to false, the overall value must be false; and when the first argument of the OR function evaluates to true, the overall value must be true.[1], Here's sample of(thanks to me for all you people that don't know about these one, I'll give you sample about these, by the implementation!!),
I believe for all programming practician, the imperative evaluation is not popular or even known, as the modern evaluation drift going to Short-circuit evaluation, why??(read below reference), and Me?, agrees with McCarthy, evaluating will be actually faster to evaluate both conditions used in boolean operation at once, as it always requires a single calculation cycle, as opposed to one or two cycles used in short-circuit evaluation (depending on the value of the first). The difference in terms of computing efficiency between these two cases depends heavily on compiler and optimization scheme used; with proper optimization they will execute at the same speed, as they will get compiled to identical machine code.[1]
And if you wondered if the Imperative . evaluation might be worthwhile?!, let me give you samples, you have a coming event of celebrating birthday party, the state where you need to arranges some preparation event and the date is your concious of deadline. Condition is arranging every preparation event, and what do you do?!, for me, I would like to do it parallelly , if one of the preparation event failed, then I don't have any option to cancel/pending the birthday(WTF, whose expecting delaying birthday??!!). By the state it will created and AND LOGIC of Imperative Evaluation, where the preparation event will be the action with logic status and the end result is Partying!!(Trust me, this kind of scenario would be better with short-circuit evaluation). The end is the imperative evaluation would be good for any parallel action or condition, where you need to keep the evaluation even-though pre-definition event is failed(simple!!, right??). Here's the sample of implementation by programming approach by the way, enjoy it!!
And if you wondered if the Imperative . evaluation might be worthwhile?!, let me give you samples, you have a coming event of celebrating birthday party, the state where you need to arranges some preparation event and the date is your concious of deadline. Condition is arranging every preparation event, and what do you do?!, for me, I would like to do it parallelly , if one of the preparation event failed, then I don't have any option to cancel/pending the birthday(WTF, whose expecting delaying birthday??!!). By the state it will created and AND LOGIC of Imperative Evaluation, where the preparation event will be the action with logic status and the end result is Partying!!(Trust me, this kind of scenario would be better with short-circuit evaluation). The end is the imperative evaluation would be good for any parallel action or condition, where you need to keep the evaluation even-though pre-definition event is failed(simple!!, right??). Here's the sample of implementation by programming approach by the way, enjoy it!!
[1]http://en.wikipedia.org/wiki/Short-circuit_evaluation