[#537 state:resolved]

This changes the behaviour of the `._?.` "dot".  It now returns 'nil'
rather than calling the trailing function more often.

hobo/CHANGES.txt

@@ -10,6 +10,21 @@ likely to cause conflicts, so it is highly recommended that you have
 your code backed up and in a change control system such as git or
 subversion.
 
+=== Hobo Edge ===
+
+Major enhancements:
+
+Major bug fixes:
+
+  - [#537](https://hobo.lighthouseapp.com/projects/8324-hobo/tickets/537)
+    The `._?.` "smart dot" now returns 'nil' rather than calling its
+    trailing function more often than it used to, more closely
+    matching its documentation.
+
+Minor enhancements:
+
+Minor bug fixes:
+
 === Hobo 0.9.0 ===
 
 Major enhancements:

hobosupport/lib/hobo_support/methodcall.rb

@@ -56,9 +56,32 @@ def try(*args)
 class SafeNil
   include Singleton
 
+  DONT_REDEFINE_METHODS = "__id__", "__send__"
+
+  NIL_RESPONSE_METHODS = ["to_s", "to_json", "to_yaml", "__id__", "__is_a__", "__metaclass__", "__send__"]
+
+  (NIL_RESPONSE_METHODS - DONT_REDEFINE_METHODS).each do |method|
+    # can't use define_method with a block
+    eval "
+      def #{method}(*args, &b)
+        nil.send(:#{method}, *args, &b)
+      end"
+  end
+
+  (instance_methods - NIL_RESPONSE_METHODS - DONT_REDEFINE_METHODS).each do |method|
+    # can't use define_method with a block
+    eval "
+      def #{method}(*args, &b)
+        nil
+      end"
+  end
+
+  def to_s
+    ""
+  end  
+
   def method_missing(method, *args, &b)
-    return nil unless nil.respond_to? method
-    nil.send(method, *args, &b) rescue nil
+    return nil
   end
 end
 

hobosupport/test/hobosupport.rdoctest

@@ -34,15 +34,21 @@ Like `is_a?` but multiple types to be checked in one go
 
 ## Method call extensions
 
+We have the "." operator to call methods on objects. These extensions introduce two "special dots". 
+
 ### `Object#_?`
 
-We have the "." operator to call methods on objects. These extensions introduce two "special dots". "`._?.`" only calls the method if the receiver is not `nil`.
+"`._?.`" only calls the method if the receiver is not `nil`.  Otherwise it returns nil.
 
     >> "foo"._?.length
     => 3
     >> nil._?.length
     => nil
 
+`to_s`, `to_yaml` and `to_json` and a few system functions that start with an underscore are the only exceptions -- they call their corresponding functions on nil.
+
+    >> nil._?.to_s
+    => ""
 
 ### `Object#try`
 
@@ -53,4 +59,14 @@ We have the "." operator to call methods on objects. These extensions introduce
     >> :foo.try.length
     => nil
 
+### What's the difference?
 
+`_?` is generally used when nil is an expected response.  `try` is
+generally used when interfaces may be different.  For instance, you
+may use `try` to call a Rails 2.3 function that doesn't exist on Rails
+2.2.  nil responds to some functions that may surprise you.
+
+    >> nil.try.to_i
+    => 0
+    >> nil._?.to_i
+    => nil