Take a look at this API: ClassNode#addProperty. Turns out that if you pass null into getterBlock and setterBlock, you get the default implementations. Maybe1. Normally passing null around blows up in unhelpful ways, but here null is a useful value. How is a programmer to know?
I’m increasingly convinced that immutability2 and strong type systems in languages aren’t just about concurrency or letting the computer optimize or catching bad code early. Increasingly, I’m convinced that the key value they provide is clear, meaningful, and maintainable code. Which is really the key problem in software development these days, isn’t it?
1 As of this writing, it’s an outstanding question if the compile phase of the AST transformation impacts whether or not the null values are translated: mailing list conversation.
2 See this nice presentation from Rich Hickey, author of Clojure.
Comments
- November 6, 2009, New PeriodicalUpdater Feature, and, Mutable Data Sucks: A Case in Point | Enfranchised Mind wrote: [...] said before that null sucks, but now I’ve got a case in point for why mutable data sucks, [...]
This post was by Robert Fischer, written on October 17, 2009.
Comment on this post: http://enfranchisedmind.com/blog/posts/null-sucks-a-case-in-point/#respond
Public Permalink: http://enfranchisedmind.com/blog/posts/null-sucks-a-case-in-point/
This article was a post on the EnfranchisedMind blog. EnfranchisedMind Blog by Robert Fischer, Brian Hurt, and Other Authors is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.
