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

Strings with an escaped backslash at the end are not decoded correctly #102

Open
ArthNevaris opened this issue Oct 9, 2024 · 0 comments

Comments

@ArthNevaris
Copy link

Hi,

I ran into the following bug.

When I use the function ParserSTEP.Decode to decode a string like Test \\, the result is Test \\ and not the expected string Test \. On the other hand, \\ Test will result in the correct \ Test. I suspect the error lies in the difference on how the last 4 characters of the string are handled in the decode function.

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

No branches or pull requests

1 participant