From: Greg.mpls@...
Date: 2017-11-29T04:36:21+00:00
Subject: [ruby-core:83939] [Ruby trunk Feature#14138] Define English.rb aliases by default and eliminate the library

Issue #14138 has been updated by MSP-Greg (Greg L).


Charles,

+1

You mentioned several good points.  I've got them doc'd in the ['Top Level Namespace'](https://msp-greg.github.io/ruby_trunk/Core/top-level-namespace.html) of my doc site so I could find the source, it would be nice if the comments could move there and replace the globals.rdoc file.  Along with RDoc picking them up somehow...

----------------------------------------
Feature #14138: Define English.rb aliases by default and eliminate the library
https://bugs.ruby-lang.org/issues/14138#change-67996

* Author: headius (Charles Nutter)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
----------------------------------------
There are many good reasons to simply define all the English.rb global aliases at boot:

* JRuby has done it for years with zero reported bugs.
* Rubinius has done it for years with zero reported bugs.
* Globals are in general discouraged, so the likelihood of collision with a user library is very low.
* The globals that remain are better indicated by using the long name rather than the Perl-esque short names.
* One less library to maintain.

The only argument to not do this seems to be the collision concern, but that has not affected hundreds of users of JRuby and Rubinius over the past decade. I think we're safe.

This would be ideal for 2.5, if it's not too late, since this is the big "gemifying" release. Eliminating English.rb would fit into that well.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>