Skip to content

Leading 0x for hex cannot be written as 0X #508

Closed

Description

@MauricioFauth

Summary

A leading 0x is case-sensitive and cannot be written as 0X.

Current behavior

$ bin/tokenize-query --query '0X0F'
[TOKEN 0]
Type = 6
Flags = 1
Value = 15
Token = '0X0F'

[TOKEN 1]
Type = 9
Flags = 0
Value = NULL
Token = NULL

Expected behavior

$ bin/tokenize-query --query '0X0F'
[TOKEN 0]
Type = 0
Flags = 0
Value = '0X0F'
Token = '0X0F'

[TOKEN 1]
Type = 9
Flags = 0
Value = NULL
Token = NULL

Activity

  1. added a commit that references this issue on Sep 15, 2023
    796b135
  2. linked a pull request that will close this issueFix invalid hexadecimal prefix 0X #509on Sep 15, 2023
  3. added this to the 5.8.1 milestone on Sep 15, 2023
  4. added a commit that references this issue on Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions