NetBeans can't find implementation_backtrace
Reported by David Chelimsky | November 21st, 2008 @ 04:48 AM | in Maintenance
Looks like NetBeans uses a method that we renamed from implementation_backtrace to example_backtrace.
This was an internal method, so it was refactored to a more meaningful name without realizing it would have this impact.
Looking at it again, I'm not particularly fond of either name, so here's what I plan to do:
Rename the method to backtrace (so you call example.backtrace) and reinstate implementation_backtrace with a deprecation warning.
I'm also going to add rdoc to #backtrace and treat it as a formal API, thus committing to maintaining it so extenders can use it without fear of future changes without significant planning/warning.
Comments and changes to this ticket
-
David Chelimsky November 21st, 2008 @ 04:56 AM
- → Milestone changed from “No-Milestone-Assigned” to “Maintenance”
- → State changed from “new” to “open”
Upon further investigation, this rename occurred between releases, so this should only affect people using RSpec's edge.
I'm still going w/ the proposed plan:
- deprecate ExampleMethods#implementation_backtrace
- add ExampleMethods#backtrace
-
David Chelimsky November 21st, 2008 @ 05:03 AM
- → State changed from “open” to “resolved”
(from [931aa93fdf62c12388c4389601b739a7e723320f]) deprecated ExampleMethods#implementation_backtrace - use ExampleMethods#backtrace instead [#609 state:resolved] http://github.com/dchelimsky/rsp...
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 »
Behaviour Driven Development for Ruby.
