So your example would be:
product.?offering.?merchant.?name
Java's really the language that needs a better solution for this. I think a lot of Java programmers don't use null values because it's so hard to express the intended semantics without building your own type annotations and such. The proposal for Javascript where nullable types are different from non-nullable ones makes a lot of sense to me.
Oliver Steele lives in Western Massachusetts and commutes to downtown LA, where he is bringing an operating system from handwaving to reality. He was the architect of OpenLaszlo, the author of PyWordNet and other open source projects. His interests include programming languages, knowledge representation, information visualization, and math education. [more]
Nice post Oliver. I recently saw that Groovy as this feature built in:
http://groovy.codehaus.org/Operators#Operators-SafeNavigationOperator%28...
So your example would be:
product.?offering.?merchant.?name
Java's really the language that needs a better solution for this. I think a lot of Java programmers don't use null values because it's so hard to express the intended semantics without building your own type annotations and such. The proposal for Javascript where nullable types are different from non-nullable ones makes a lot of sense to me.