Re:True, False And Nil Objects In Ruby
by masklinn on Tuesday September 08, 2009 @10:43AM
(#811093)
That's a potential solution in any language (you don't even have to extend a none/nil/whatever object), but it doesn't help interact with standard or third-party libraries which return `nil` already.
[ Parent
| on HN ]
Re:True, False And Nil Objects In Ruby
by stcredzero on Wednesday September 09, 2009 @02:18AM
(#812644)
My stock solution to libraries with, let's call it, "substandard polymorphism" -- facades and/or wrappers. This often lets you put all of your conditional logic for dealing with the errant library in just one place. It's better than nothing. Sometimes, it's a lot better.