Feature #12574: Remove TRUE, FALSE, and NIL

• Status: Closed
• Assignee: matz (Yukihiro Matsumoto)
• Target version: -

[shugo (Shugo Maeda)]

I believe TRUE, FALSE, and NIL are no longer used.
Why not remove them?

[nobu (Nobuyoshi Nakada)]

Deprecate them first?

[shugo (Shugo Maeda)]

Nobuyoshi Nakada wrote:

Deprecate them first?

Sounds reasonable.

I found that tool/mkconfig.rb uses them....

[matz (Yukihiro Matsumoto)]

You have to wait until Ruby 3.0 at least.
I'd agree to remove TRUE, FALSE, NIL first.

Matz.

[shugo (Shugo Maeda)]

• 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?

[nobu (Nobuyoshi Nakada)]

• 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]