warning: undefining `object_id' may cause serious problems

[srpouyet]

Hi,

Since jbuilder 0.5.0 the following warning pops up when I $ bundle install or $ rails console:

/Users/sebastiaan/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/gems/blankslate-3.1.2/lib/blankslate.rb:51: warning: undefining 'object_id' may cause serious problems

As you can see I'm running Ruby 1.9.3-p194.

This warning has been popping up since the bump to 0.5.0 so I thought it best to post an issue here instead of the blankslate repo. If I'm barking up the wrong tree let me know :)

Cheers,
Sebastiaan

[MSch]

I don't see why the blankslate gem is still necessary now that Ruby 1.9 has BasicObject

[dhh]

Feel free to whip up a patch!

On Sep 10, 2012, at 9:15 AM, Martin Schürrer notifications@github.com wrote:

I don't see why the blankslate gem is still necessary now that Ruby 1.9 has BasicObject

—
Reply to this email directly or view it on GitHub.

[SamSaffron]

not that easy @MSch

  define_method(:__class__, find_hidden_method(:class))
  define_method(:_tap, find_hidden_method(:tap))
  reveal(:respond_to?)

How would you port that to BasicObject? It has no tap or class or respond_to? method,

[14] pry(main)> BasicObject.instance_methods
=> [:==, :equal?, :!, :!=, :instance_eval, :instance_exec, :__send__, :__id__]

[SamSaffron]

ok,

 def __class__
    (class << self; self; end).superclass
  end

  def _tap
    yield self
    self
  end

seems ok, does anyone know why :respond_to is revealed?

[SamSaffron]

Getting jbuilder to work with BlankObject is not trivial, I am half an hour in and still no luck

[SamSaffron]

and another question ... where is the source for blankslate now, github seems out of date.

[jjaffeux]

@SErepo you can now close it

[srpouyet]

@SamSaffron & @rolftimmermans thanks for your work good sirs!

cheers

[axelson]

What version do we need to revert to to avoid the object_id warning?

[jjaffeux]

gemfile :

gem "jbuilder", :git => 'git://github.com/rails/jbuilder.git', :branch => 'master'

then :

bundle update

[dhh]

I pushed a new gem, so bundle update will take care of it.

On Sep 21, 2012, at 1:49 PM, Jason Axelson wrote:

What version do we need to revert to to avoid the object_id warning?

—
Reply to this email directly or view it on GitHub.

David Heinemeier Hansson