Bug #10105
closed
- Status changed from Open to Third Party's Issue
- Assignee changed from zzak (zzak _) to drbrain (Eric Hodel)
- Priority changed from 3 to Normal
Rather I think it a bug of RDoc.
I don't think that it is only a bug in RDoc.
There are at least 3 ways to define class methods in ruby, and I think that all are acceptable, but define two class methods in different ways in the standard library it's not a good example, nor a good practice and does not help in readability.
Ok, there is a lacking feature in RDoc, but I don't think that keeping it that way is the way to go.
It's valid code, at least.
Whether you consider it a good example or not is another story.
- Assignee changed from drbrain (Eric Hodel) to zzak (zzak _)
- Status changed from Third Party's Issue to Assigned
I've tried to fix it only touching documentation, and it seems to be
impossible, rdoc does not understand the class << self
syntax (I
understand rdoc in this point, ruby is not easy to parse). I've added an
issue in Rdoc for it ( https://github.com/rdoc/rdoc/issues/317 ).
So the Tempfile.open method needs to be redefined to be understand by rdoc.
I've updated the pull request with the minimal change that will fix the
issue I don't like it as it define class methods outside of the class
itself (so the source is harder to read), and it hardcode the class name
two times (that I think is ugly).
I quite not understand why there is so much resistance to refactor the code
for readability.
--- Eloy
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Applied in changeset r47133.
lib/tempfile.rb: include doc of Tempfile.open
- lib/tempfile.rb: start rdoc parsing inside singleton class
definition to include the document there.
[ruby-core:64157] [Bug #10105]
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0