Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
EVL and NVL
Message
From
19/05/2004 09:14:21
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
 
 
To
19/05/2004 06:36:17
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Miscellaneous
Thread ID:
00905138
Message ID:
00905240
Views:
22
I am quite sure you know this, but for anyone else who is reading: the "slow to evaluate" part is not always the worst effect. The worst effect is the possibility of "side effects", if a function gets executed when you don't expect it.

>
><snip>
>Hey MS - Any plans to change of "fix" this.
>

>
>I agree with you,
>but it is a Function,
>and therefore it is necessary to estimate all the parameters before executing of the code.
>
>Of course VFPT can crack this standard schema,
>but i think that this event non occur on the future VFP releases.
>
>EVL() and NVL() are usefull with a :
>
>EVL(EXPRESSION,surrogateCostant or Variable)
>NVL(EXPRESSION,surrogateCostant or Variable)
>
>but if second parameter is slow to evaluate, use IIF(),
>
>IIF(ISNULL(EXPRESSION),surrogateCostant or Variable,EXPRESSION)
>
>but if EXPRESSION is slow to evalute or worse, it is not deterministic,
>you must to please you of:
>
>varExp=EXPRESSION
>IIF(ISNULL(m.varExp),surrogateCostant or Variable,m.varExp)
>
>
>Fabio
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform