Bug #6644: Weird behavior of defined?(super) check invoked from a metaprogrammatically defined class method

• Status: Closed
• Assignee: -
• Target version: 2.0.0
• ruby -v: ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux]

[alexisowl (Alexey Smolianinov)]

=begin
Lately I came across some weird behavior with the (({defined?})) operator used to check if (({super})) keyword can be invoked in current context. Usually it works fine, but when I tried to combine the (({defined? super})) check with a tiny bit of metaprogramming, it gave me unexpected results.

Here's an example:

class A;
def self.def_f!;
singleton_class.send(:define_method, :f) { defined? super }
end
end
class AA < A; end

A.def_f!

A.f # => nil
AA.f # => nil

AA.def_f!

AA.f # => "super"
A.f # => "super" - WHY???

The last result is really strange, isn't it?

A.f has no super method, so I would expect the last (({A.f})) to return (({nil})).
Is it a bug?

=end

[alexisowl (Alexey Smolianinov)]

Hello? Is anyone here? :)

[nobu (Nobuyoshi Nakada)]

• Category set to core
• Target version changed from 1.9.3 to 2.0.0

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed
• % Done changed from 0 to 100

This issue was solved with changeset r36369.
Alexey, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

---

defined: me in cfp

• insns.def (defined): use method entry and id in cfp for proper
  superclass, since klass in iseq is shared by dynamically defined
  methods from the same block. [ruby-core:45831][Bug #6644]