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.

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

Whitespace in SLEIGH token names #576

Open
bdarmofal opened this issue May 6, 2019 · 3 comments
Open

Whitespace in SLEIGH token names #576

bdarmofal opened this issue May 6, 2019 · 3 comments
Labels

Comments

@bdarmofal
Copy link

I would like to be able to use leading spaces in my SLEIGH token definitions.

I have several string fields I concatenate using the "^" operator to form a mnemonic name.
If any of these fields are defined using leading spaces, they are automatically trimmed off.

Is there some way to escape out the leading spaces so they are preserved when the processor definition is compiled and used?

I hate to resort to patching code or using another delimiter like a period or underscore where a space is called for.

@bdarmofal bdarmofal added the Type: Enhancement New feature or request label May 6, 2019
@achan1989
Copy link
Contributor

Have you tried quoting the whitespace?

@mumbel
Copy link
Contributor

mumbel commented May 9, 2019

Looks similar to #315

@bdarmofal
Copy link
Author

Yes, the leading spaces are contained in quotes.
They are being dropped by the SLEIGH compiler / parser?

Example:
prefix_text: " PC" is pc1=0 { }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants