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

Don't make all syntax errors fatal #33

Open
nmoroze opened this issue Apr 24, 2024 · 0 comments
Open

Don't make all syntax errors fatal #33

nmoroze opened this issue Apr 24, 2024 · 0 comments

Comments

@nmoroze
Copy link
Owner

nmoroze commented Apr 24, 2024

Syntax errors in parsed command arguments don't need to kill parsing of the entire script, but they currently do. E.g., linting this input:

set foo 1
if {foo > 0} {
    puts this is an error
}

gives:

test.tcl:2:5: syntax error: invalid bareword in expression: foo

But i'd expect it to give

test.tcl:2:5: syntax error: invalid bareword in expression: foo
test.tcl:3:5: too many args to puts: got 4, expected no more than 3 [command-args]
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