From: "sorah (Shota Fukumori)" Date: 2013-09-10T10:48:18+09:00 Subject: [ruby-core:57095] [ruby-trunk - Bug #8884][Assigned] `caller(1, nil)` raises a runtime error while its reference says its signature as `caller(start=1, length=nil)` Issue #8884 has been updated by sorah (Shota Fukumori). Status changed from Open to Assigned Assignee set to ko1 (Koichi Sasada) This patch fixes: https://gist.github.com/sorah/6503895 I'll commit this if doc is correct. ---------------------------------------- Bug #8884: `caller(1, nil)` raises a runtime error while its reference says its signature as `caller(start=1, length=nil)` https://bugs.ruby-lang.org/issues/8884#change-41703 Author: gfx (Goro Fuji) Status: Assigned Priority: Normal Assignee: ko1 (Koichi Sasada) Category: Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.4.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN > $ ruby -e 'caller(1, nil)' > -e:1:in `caller': no implicit conversion from nil to integer (TypeError) > from -e:1:in `
' Either the behaviour or the document looks wrong; I don't know which is wrong, though. -- http://bugs.ruby-lang.org/