F
fkocherga
=20interpreter complains about uninitialized constant N. What is the big =
reason for dynamically defined class to behave so differently? It would =
be very non obvious and unexpected behavior. Actually both cases work as =
expected in Ruby 1.9.1 and this is correct behavior according to the =
Ruby Draft.
doubt that both forms will behave the same.=20
reason for dynamically defined class to behave so differently? It would =
be very non obvious and unexpected behavior. Actually both cases work as =
expected in Ruby 1.9.1 and this is correct behavior according to the =
Ruby Draft.
I believe they are aspects of the same issue.=20
Nice clarification.
=20
Are there two issues here? This issue and the resolution of constants
via instance_eval? Or are these two aspects of the same issue?
I agree, but if constant lookup rules are going to be reverted to 1.8 I =In either case, there is no doubt in my mind that 'class B' and 'B =3D
Class.new do' should work the same.
doubt that both forms will behave the same.=20