Actions
Feature #12574
closedRemove TRUE, FALSE, and NIL
    Feature #12574:
    Remove TRUE, FALSE, and NIL
  
Description
I believe TRUE, FALSE, and NIL are no longer used.
Why not remove them?
        
           Updated by nobu (Nobuyoshi Nakada) over 9 years ago
          Updated by nobu (Nobuyoshi Nakada) over 9 years ago
          
          
        
        
      
      Deprecate them first?
        
           Updated by shugo (Shugo Maeda) over 9 years ago
          Updated by shugo (Shugo Maeda) over 9 years ago
          
          
        
        
      
      Nobuyoshi Nakada wrote:
Deprecate them first?
Sounds reasonable.
I found that tool/mkconfig.rb uses them....
        
           Updated by matz (Yukihiro Matsumoto) over 9 years ago
          Updated by matz (Yukihiro Matsumoto) over 9 years ago
          
          
        
        
      
      You have to wait until Ruby 3.0 at least.
I'd agree to remove TRUE, FALSE, NIL first.
Matz.
        
           Updated by shugo (Shugo Maeda) over 9 years ago
          Updated by shugo (Shugo Maeda) over 9 years ago
          
          
        
        
      
      - Status changed from Open to Assigned
- Assignee set to matz (Yukihiro Matsumoto)
Yukihiro Matsumoto wrote:
You have to wait until Ruby 3.0 at least.
I'd agree to remove TRUE, FALSE, NIL first.
Do you mean deprecating them first in 2.4?
        
           Updated by nobu (Nobuyoshi Nakada) about 9 years ago
          Updated by nobu (Nobuyoshi Nakada) about 9 years ago
          
          
        
        
      
      - Status changed from Assigned to Closed
Applied in changeset r55824.
deprecate TRUE,FALSE,NIL
- object.c (InitVM_Object): deprecate toplevel constants TRUE,
 FALSE, and NIL. [Feature #12574]
Actions