Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: JRuby 1.1.3
-
Fix Version/s: JRuby 1.1.3
-
Component/s: Core Classes/Modules
-
Labels:None
-
Number of attachments :
Description
See this thread:
http://archive.jruby.codehaus.org/dev/3454c9680807160519p66012a2ao4f00994a6c6b8c76%40mail.gmail.com
Pasting important for convenience (follow the thread for the rest)
RubyKernel#proc and RubyModule#ancestors (with a bunch of other methods)
changed their signature in rev. 7131:http://fisheye.codehaus.org/changelog/jruby/?cs=7131
RubyArray ancestors()
RubyProc proc(IRubyObject recv, Block block)becomes
RubyArray ancestors(ThreadContext context)
RubyProc proc(ThreadContext context, IRubyObject recv, Block block)Any chance they will be taken back as deprecated for JRuby 1.1.3? E.g.
I've changed call:RubyProc proc = RubyKernel.proc(recv, block);
to:
ThreadContext ctx = ThreadContext.newContext(recv.getRuntime());
RubyProc proc = RubyKernel.proc(ctx, recv, block);Is that right? If yes, the original method could be taken back.
If they are not taken back it would mean that already released
extensions like (j)ruby-debug-base will not work with JRuby 1.1.3. I've
supposed that during minor version increase (1.1.x) the API is kept. Is
that right assumption so above is a bug? I would file it.
The API breakage was unintentional, and we can certainly add for convenience the old versions of these signatures. I'll do that today.