Forum Discussion
Errors / Omissions in All Functions Listing
I have completed my review of the All Functions listing at support.microsoft.com In total, I have 349 reports of errors/omissions/inadequacies. Of the 492 functions in my records some 'star' more...
IF(1,) actually returns a missing argument which is treated as a blank in many formulas, for example the following all return TRUE:
=ISBLANK(IF(1,))
=IF(1,)=""
=IF(1,)=0
=IF(1,)=FALSE
Since blank cells cannot contain formulas in Excel =IF(1,) gets converted to zero in cell results. Google sheets on the other hand returns a blank value which is perhaps a more logical approach.
Interesting what you say about Google sheets being more logical.
However, it seems to me that if you were so minded as to leave the value_if_true argument optional, you would give it the return of TRUE following the same logic that always applied if the value_if_false was left optional. In that case the underlying values of the opitional arguments would be 1 for value_if_true and 0 for value_if_false.
But, I have yet to find anyone who mounts any argument for supporting the first step of the process which is, "Should the value_if_true argument be optional?" If that is supportable, we can then move on to the second step which is to ask, "What should the default value be?"
What you are working towards is the vital area of trapping the problem that arises because Microsoft have failed to approach the problem logically.
My vote goes for rejuecting the first proposition and leaving what was working very well alone.
Thanks for your thoughts!
Norman
However, it seems to me that if you were so minded as to leave the value_if_true argument optional, you would give it the return of TRUE following the same logic that always applied if the value_if_false was left optional. In that case the underlying values of the opitional arguments would be 1 for value_if_true and 0 for value_if_false.
But, I have yet to find anyone who mounts any argument for supporting the first step of the process which is, "Should the value_if_true argument be optional?" If that is supportable, we can then move on to the second step which is to ask, "What should the default value be?"
What you are working towards is the vital area of trapping the problem that arises because Microsoft have failed to approach the problem logically.
My vote goes for rejuecting the first proposition and leaving what was working very well alone.
Thanks for your thoughts!
Norman