warning: undefining `object_id' may cause serious problems about jbuilder HOT 11 CLOSED

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

from jbuilder.

Feel free to whip up a patch!

On Sep 10, 2012, at 9:15 AM, Martin Schürrer [email protected] 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.

from jbuilder.

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__]

from jbuilder.

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?

from jbuilder.

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

from jbuilder.

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

from jbuilder.

@SErepo you can now close it

from jbuilder.

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

cheers

from jbuilder.

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

from jbuilder.

gemfile :

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

then :

bundle update

from jbuilder.

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

from jbuilder.