[BUG] eval/instance_eval fails to correctly modify TOPLEVEL_BINDING
Reported by Brian Ford | February 23rd, 2008 @ 11:22 AM | in 1.0 preview
I've pushed a branch (instance_eval) that changes MSpec to use instance_eval rather than calling blocks. bin/mspec -tr spec/ruby runs without errors on intel Leopard. But bin/mspec spec/ruby has over 100 errors. All seem related to constants and method defs.
There is a particular spec for TOPLEVEL_BINDING in spec/ruby/1.8/core/module/include_spec.rb, access with
bin/mspec -e 'Module#include imports constants to the toplevel' spec/ruby/1.8/core/module/include_spec.rb
Comments and changes to this ticket
-
Brian Ford February 24th, 2008 @ 03:57 PM
- → State changed from “new” to “open”
- → Assigned user changed from “” to “Evan Phoenix”
-
Ryan Davis March 5th, 2008 @ 05:27 PM
- → Assigned user changed from “Evan Phoenix” to “Ryan Davis”
-
Wilson Bilkovich March 10th, 2008 @ 03:50 PM
- → State changed from “open” to “resolved”
- → Assigned user changed from “Ryan Davis” to “Wilson Bilkovich”
Fixed in 746d89d6d55c82f26be08f182
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Evan Phoenix