Calling a method on undef/NULL doesn't cause a runtime error. I'm not sure what I think about that.
return null/undef? Michel and I were talking about overloading undef to get the same behaviour so that chaining method calls that might fail to return an object would not blow up but instead propagate the returned undef to the lhs.
