Project

General

Profile

Actions
Copy link

Bug #19882

closed

:$0x should be rejected

Bug #19882: :$0x should be rejected

Added by mame (Yusuke Endoh) about 3 years ago. Updated about 3 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
Backport:
3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
[ruby-core:114761]

Description

irb(main):001> :$0x
=> :"$0x"

Since $0x is not a valid global variable name, I think it should be rejected unless quotation marks are used.

Related issues 1 (0 open — 1 closed)

Related to Ruby - Bug #19549: Inconsistency in backref parsingClosedActions

Updated by kddnewton (Kevin Newton) about 3 years ago Actions
Copy link
 #1 [ruby-core:114762]

I think it is rejected at the moment:

-e:1: identifier $0x is not valid to get
-e: compile error (SyntaxError)

Updated by mame (Yusuke Endoh) about 3 years ago Actions
Copy link
 #2 [ruby-core:114763]

Don't overlook the colon!

Updated by nobu (Nobuyoshi Nakada) about 3 years ago Actions
Copy link
 #3

  • Related to Bug #19549: Inconsistency in backref parsing added

Updated by nobu (Nobuyoshi Nakada) about 3 years ago Actions
Copy link
 #4 [ruby-core:114770]

It's subtly intentional.

The former seemed better to me.

$ ruby -e '$01234'
-e:1: identifier $01234 is not valid to get
-e: compile error (SyntaxError)

$ ./ruby -e 'p :$01234'
-e:1: syntax error, unexpected integer literal, expecting end-of-input
$01234
  ^~~~
-e: compile error (SyntaxError)

"Then the symbol should not be quoted"?, maybe.

Updated by nobu (Nobuyoshi Nakada) about 3 years ago Actions
Copy link
 #6

  • Status changed from Open to Closed

Applied in changeset git|89802078f9f406be411032814e1960e62dbc7ce2.

[Bug #19882] Reject tokens invalid as symbols

Actions
Copy link

Also available in: PDF Atom