From: "Haase, Konstantin" <Konstantin.Haase@...>
Date: 2011-08-17T02:34:20+09:00
Subject: [ruby-core:38988] Re: [Ruby 1.9 - Bug #5196][Open] true should be True.

But constant doesn't mean you can't change it in Ruby... keywords are basically the only thing you can't change. And most of those are not capitalized.
`true` is a literal, just like `nil` or `250`. You can't change those either.

Ease of use and conventions always outweigh consistency and simplicity in Ruby.

Konstantin

On Aug 16, 2011, at 19:28 , Tomoki Imai wrote:

> 
> Issue #5196 has been reported by Tomoki  Imai .
> 
> ----------------------------------------
> Bug #5196: true should be True.
> http://redmine.ruby-lang.org/issues/5196
> 
> Author: Tomoki  Imai 
> Status: Open
> Priority: Normal
> Assignee: 
> Category: core
> Target version: 
> ruby -v: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] 
> 
> 
> Hello.I'm Tomoki Imai.
> 
> I found Ruby has inconsistency.
> 
> true is constant value.
> In irb,
> 
> true = nil
> (irb):5: Can't assign to true
> true = nil
>      ^
> 	from (irb):5
> 	from :0
> 
> We can't change value true.
> 
> In Ruby,we use capitalized name for constant value.
> For example,
> A = 3 .
> 
> This is why true should be True.
> 
> 
> -- 
> http://redmine.ruby-lang.org
>