Bug #2211
closedeval Documentation Claims Proc Accepted for Binding
Description
=begin
eval
's documentation wrongly claims it accepts a Proc for the binding argument. This patch fixes the RDoc.
=end
Files
Updated by marcandre (Marc-Andre Lafortune) about 15 years ago
- Category changed from doc to core
- Assignee set to matz (Yukihiro Matsumoto)
=begin
Patch applied in r25335 for now. Should eval accept a Proc? It might be preferable not to, since it might be clearer to pass some_proc.binding then only some_proc.
=end
Updated by marcandre (Marc-Andre Lafortune) about 15 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
=begin
This issue was solved with changeset r25335.
Run Paint, thank you for your reporting of the issue.
You have greatfully contributed toward Ruby.
May Ruby be with you.
=end
Updated by marcandre (Marc-Andre Lafortune) about 15 years ago
- Status changed from Closed to Open
=begin
=end
Updated by marcandre (Marc-Andre Lafortune) over 14 years ago
- Status changed from Open to Closed
=begin
=end
Updated by marcandre (Marc-Andre Lafortune) over 14 years ago
- Status changed from Closed to Open
- Priority changed from 3 to Normal
- Target version set to 1.9.2
=begin
Since Ruby 1.8 does allow passing a Proc, we should agree on the desired behavior.
=end
Updated by mame (Yusuke Endoh) over 14 years ago
- Status changed from Open to Closed
=begin
Hi,
Ko1 asked matz to delete this feature for ease of YARV
implementation, and matz approved. [ruby-dev:34915]
So this is intended change. I close this ticket.
Ko1 also invited public opinion about the feature (is
there people who want this feature?). [ruby-dev:34917]
Only akr answered that he want for his library (htree),
and the discussion stopped.
If you want the feature, please register new ticket with
reason to Feature tracker.
--
Yusuke Endoh mame@tsg.ne.jp
=end