Project

General

Profile

Feature #9864

Rename 'optparse' to 'optionparser', or the main class OptionParser to OptParse

Added by shevegen (Robert A. Heiler) over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
[ruby-core:62750]

Description

Hello.

I don't like the inconsistency in the naming of optparse and the class that
we are supposed to use itself.

I think it would be better to do:

require 'optparse'
OptParse.new

or

require 'optionparser'
OptionParser.new


Related issues

Related to Ruby master - Bug #13281: [DOC] OptionParser docs leak into class documentation of ObjectClosedstomar (Marcus Stollsteimer)Actions

Updated by shevegen (Robert A. Heiler) over 6 years ago

Currently, we have to do this:

require 'optparse'
OptionParser.new

Updated by nobu (Nobuyoshi Nakada) over 6 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Applied in changeset r46126.


lib/optionparser.rb

  • lib/optionparser.rb, lib/optparse.rb (OptParse): aliases. [ruby-core:62751] [Feature #9864]
#3

Updated by stomar (Marcus Stollsteimer) almost 4 years ago

  • Related to Bug #13281: [DOC] OptionParser docs leak into class documentation of Object added

Also available in: Atom PDF