trust me, every behavior is better than just throwing a MAV into the endusers face! :)
I'm not talking about end users. As I said, "during development". FarFlame's function makes changes to the fields of a type - if the code is passing a Null pointer to it at any stage, this is a bug in the code and needs to be addressed.There are other situations where checking against Null is required, I'm just saying that this particular situation may not be wise to employ it. :)