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

xparse changed behavior after #127 (regression?) #183

Open
KristofferC opened this issue Nov 7, 2023 · 1 comment
Open

xparse changed behavior after #127 (regression?) #183

KristofferC opened this issue Nov 7, 2023 · 1 comment

Comments

@KristofferC
Copy link
Contributor

After #127 the following

using Parsers

opts = Parsers.Options(; quoted=true)

str = """
"key" "value"
"""

r = Parsers.xparse(String, str, 1, length(str), opts)

@show r.tlen

changed from showing 6 to 14. This to me suggests that the parsing no longer stops at the closing delimiter which seems like a regression, but I am not sure.

@KristofferC
Copy link
Contributor Author

KristofferC commented Nov 7, 2023

It seems adding delim=nothing to Parsers.Options gets me back to the previous behavior but not 100% sure. But that make this Option behave differently in some other contexts so it isn't ideal. For now, I worked around it by having one Option for parsing strings and a different one for parsing other stuff.

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