

Don't do this

[ This article has undergone major revisions since it was first published yesterday. ] Here is a line of Perl code: if ($self->fidget && blessed $self->fidget eq 'Widget::Fidget') { This looks to see if $self has anything in its fidget slot, and if so it checks to see if the value there is an instance of the class Widget::Fidget . If both are true, it runs the following block. That blessed check is bad practice for several reasons. It duplicates the declaration of the fidget member data: has fidget => ( is => 'rw', isa => 'Widget::Fidget', init_arg => undef, ); So the fidget slot can't contain anything other than a Widget::Fidget , because the OOP system is already enforcing that. That means that the blessed … eq test is not doing anything — unless someone comes along later and changes the declared type, in which case the test will then be checking the wrong condition. Actually, that has already happened! The declaration, as written, allows fidget to be an instance not just of Widget::Fidget but of any class derived from it. But the blessed … eq check prevents this. This reneges on a major promise of OOP, that if a class doesn't have the behavior you need, you can subclass it and modify or extend it, and then use objects from the subclass instead. But if you try that here, the blessed … eq check will foil you. So this is a prime example of “… in which case the test will be checking the wrong condition” above. The test does not match the declaration, so it is checking the wrong condition. The blessed … eq check breaks the ability of the class to work with derived classes of Widget::Fidget . Similarly, the check prevents someone from changing the declared type to something more permissive, such as “either Widget::Fidget or Gidget::Fidget ” or “any object that supports wiggle and waggle methods” or “any object that adheres to the specification of Widget::Interface ” and then inserting a different object that supports the same interface. But the whole point of object-oriented programming is that as long as an object conforms to the required interface, you shouldn't care about its internal implementation. In particular, the check above prevents someone from creating a mock Widget::Fidget object and injecting it for testing purposes. We have traded away many of the modularity and interoperability guarantees that OOP was trying to preserve for us. What did we get in return? What are the purported advantages of the blessed … eq check? I suppose it is intended to detect an anomalous situation in which some completely wrong object is somehow stored into the self.fidget member. The member declaration will prevent this (that is what it is for), but let's imagine that it has happened anyway. This could be a very serious problem. What will happen next? With the check in place, the bug will go unnoticed because the function will simply continue as if it had no fidget. This could cause a much more subtle failure much farther down the road. Someone trying to debug this will be mystified: At best “it's behaving as though it had no fidget, but I know that one was set earlier”, and at worst “why is there two years of inconsistent data in the database?” This could take a very long time to track down. Even worse, it might never be noticed, and the method might quietly do the wrong thing every time it was used. Without the extra check, the situation is much better: the function will throw an exception as soon as it tries to call a fidget method on the non-fidget object. The exception will point a big fat finger right at the problem: “hey, on line 2389 you tried to call the rotate method on a Skunk::Stinky object, but that class has no such method`. Someone trying to debug this will immediately ask the right question: “Who put a skunk in there instead of a widget?” It's easy to get this right. Instead of if ($self->fidget && blessed $self->fidget eq 'Widget::Fidget') { one can simply use: if ($self->fidget) { Moral of the story: programmers write too much code. I am reminded of something chess master Aron Nimzovitch once said, maybe in Chess Praxis, that amateur chess players are always trying to be Doing Something.

[Other articles in category /prog/perl] permanent link

