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

Resiliance to malformed VHDL #669

Open
imd1 opened this issue Nov 9, 2021 · 2 comments
Open

Resiliance to malformed VHDL #669

imd1 opened this issue Nov 9, 2021 · 2 comments
Assignees

Comments

@imd1
Copy link
Contributor

imd1 commented Nov 9, 2021

What is your question?
Sometimes I run VSG against code that does not compile i.e. it has VHDL syntax errors. VSG tends to fall over in a heap. Should this happen? Are there not traps somewhere so VSG can fail gracefully?

@imd1 imd1 added the question label Nov 9, 2021
@jeremiah-c-leary
Copy link
Owner

I would think that is possible, after all vcom does not stop at the first error.

Currently my parser will stop if there is a syntax error, but a syntax error is just something missing. I might be able to continue parsing and just skip the missing element.

No guarantee the rest could be parsed though.

It might give false results.

Maybe just analyze up to the syntax error?

@jeremiah-c-leary jeremiah-c-leary self-assigned this Feb 1, 2022
@imd1
Copy link
Contributor Author

imd1 commented Feb 6, 2022

When malformed VHDL is processed, I'd like VSG to report this rather than some obscure traceback error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Deferred
Development

No branches or pull requests

2 participants