From: "naruse (Yui NARUSE)" Date: 2012-04-02T19:05:01+09:00 Subject: [ruby-core:44065] [ruby-trunk - Bug #4453] Overriding #to_s changes #inspect Issue #4453 has been updated by naruse (Yui NARUSE). qwerty55 (salvatore giudice) wrote: > Is there some reason that this bug persists for years? Because you didn't report it. You should thank yimutang. ---------------------------------------- Bug #4453: Overriding #to_s changes #inspect https://bugs.ruby-lang.org/issues/4453#change-25595 Author: yimutang (Joey Zhou) Status: Assigned Priority: Normal Assignee: matz (Yukihiro Matsumoto) Category: Target version: ruby -v: ruby 1.9.2p180 (2011-02-18) [i386-mingw32] # My Ruby is: ruby 1.9.2p180 (2011-02-18) [i386-mingw32] # sample codes 1: class Foo # subclass of Object, inherits #inspect and #to_s def initialize(bar,baz) @bar, @baz = bar, baz end end obj = Foo.new(:cat, :dog) puts "\n== #inspect =====" p obj # puts obj.inspect # printf "%p", obj # puts "\n== #to_s ========" puts obj.to_s # printf "%s", obj # # Yes, #inspect and #to_s are not synonyms, they return different strings. # sample codes 2, add 'def to_s': class Foo def initialize(bar,baz) @bar, @baz = bar, baz end def to_s # override #to_s method "has @bar = #{@bar}, @baz = #{@baz}." end end obj = Foo.new(:cat, :dog) puts "\n== #inspect =====" p obj # has @bar = cat, @baz = dog. puts obj.inspect # has @bar = cat, @baz = dog. printf "%p", obj # has @bar = cat, @baz = dog. puts "\n== #to_s ========" puts obj.to_s # has @bar = cat, @baz = dog. printf "%s", obj # has @bar = cat, @baz = dog. # However, overriding #to_s makes #inspect do the identical thing. I don't think it's perfect. # In fact, the problem was reported in 2009. http://redmine.ruby-lang.org/issues/1786 # At the bottom of the page, Matz said: # "Redefining #to_s should not affect inspect, if they are totally different." # I agree with Matz. #to_s and #inspcet should not be synonyms: # #to_s maybe for the user of the application, they want a readable message; # but #inspect maybe for the programmer, they want a debug information. # So, if this is a bug, maybe it should be fixed. If it's a feature in 1.9.2, I think it's not a good one, # because I lose a quick and convenient debug method to know an object's class the its instance variables. # I may want to show something readable to user of my app, as well as something usable for myself. # The feature (or bug) doesn't satisfy both. -- http://bugs.ruby-lang.org/