Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add a single node for DOUBLE PRECISION and similar multi-token keywords #36

Closed
pjh40 opened this issue Oct 3, 2019 · 1 comment
Closed

Add a single node for DOUBLE PRECISION and similar multi-token keywords #36

pjh40 opened this issue Oct 3, 2019 · 1 comment
Assignees
@pjh40
Labels
enhancement New feature or request

Comments

@pjh40
Copy link
Collaborator

pjh40 commented Oct 3, 2019

Currently, DOUBLE PRECISION is recognized by FLPR::Stmt::intrinsic_type_spec() as two keywords. This makes it difficult for users to identify the meaning of this sequence. Suggest adding a "smashed" keyword for all non-END* entries in Smash_Hash.gperf.
@pjh40 pjh40 self-assigned this Oct 3, 2019
@pjh40 pjh40 added the enhancement New feature or request label Oct 3, 2019
@pjh40
Copy link
Collaborator Author

pjh40 commented Oct 3, 2019

Turns out that the rest of the "smashed" keywords are all structural, in that they are either complete statements, or complete prefixes of statements (GOTO). Limiting the change to DOUBLEPRECISION.

@pjh40 pjh40 mentioned this issue Oct 3, 2019
Merged
@pjh40 pjh40 closed this as completed Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pjh40 pjh40

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pjh40