Page MenuHomeFeedback Tracker

BIS_fnc_areEqual returns true if both param's are nil or null - very bad standard
New, WishlistPublic

Description

According to the function header comment of the function BIS_fnc_areEqual,

Quote: "-If both values are undefined / nil / null, then this function will return true."

So [objNull, objNull] call BIS_fnc_areEqual, will return true, which is logically wrong.
So [nil, nil] call BIS_fnc_areEqual, will return true, which is logically wrong.

This is a terrible standard to be adopting, programming wise.
The golden rule is that:
(objNull == objNull) MUST return false and the same for nil.
There is "nothing" to compare, so how can it ever be equal?

Details

Legacy ID
3006009289
Severity
None
Resolution
Open
Reproducibility
Always
Category
Scripting

Event Timeline

Dr_Eyeball edited Additional Information. (Show Details)
Dr_Eyeball set Category to Scripting.
Dr_Eyeball set Reproducibility to Always.
Dr_Eyeball set Severity to None.
Dr_Eyeball set Resolution to Open.
Dr_Eyeball set Legacy ID to 3006009289.May 7 2016, 5:04 PM