Its a common problem in most JEE projects, handling null-values. But why is this a problem? What strategies and patterns can we follow to reduce this problem?
The whole programming by contract I get, but is the general opinion working with empty objects is better than checking for null. IMO, you still have to check for state somewhere. Example, I request a collection , i still have to check for empty case. If I request a user for an id i still have to check if its empty or not. Isn't null for these type of conditions.. what is point of null value if we want to avoid it completely ?
Comments
ceaseoleo replied ago:
The whole programming by contract I get, but is the general opinion working with empty objects is better than checking for null. IMO, you still have to check for state somewhere. Example, I request a collection , i still have to check for empty case. If I request a user for an id i still have to check if its empty or not. Isn't null for these type of conditions.. what is point of null value if we want to avoid it completely ?
Voters For This Link (24)
Voters Against This Link (0)