cpoirier (Chris Poirier)
- Login: cpoirier
- Email: [email protected]
- Registered on: 08/06/2012
- Last sign in: 09/03/2012
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
08/06/2012
-
01:24 PM Ruby Bug #6838: class_eval and instance_eval do not scope class names the same as direct code
- On more thought, I can understand that Ruby views class names the same way it does variables, and so pulls them from the binding. It just doesn't feel like it's the right behaviour, in this context.
-
01:13 PM Ruby Bug #6838 (Rejected): class_eval and instance_eval do not scope class names the same as direct code
- class X
def self.f()
puts "::X"
end
end
class Y
class X
def self.f()
puts "Y::X"
end
end
def self.c()
X.f()
end
end
Y.class_eval do
def self.k()
X....