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

Internal error caused by signals declared and initialized together inside a block #210

Closed
veripoolbot opened this issue Jan 20, 2010 · 2 comments
Assignees

Comments

@veripoolbot
Copy link
Contributor

@veripoolbot veripoolbot commented Jan 20, 2010


Author Name: Byron Bradley (@bbradley)
Original Redmine Issue: 210 from https://www.veripool.org
Original Date: 2010-01-20
Original Assignee: Wilson Snyder (@wsnyder)


If a signal is declared and initialized in the same statement in a block (initial, always, etc.), V3Life will fail with "Scope lost on variable". The patch attached shows this in t/t_var_local and fixes a ->fatalSrc() being called on the wrong node in V3Life.

@veripoolbot
Copy link
Contributor Author

@veripoolbot veripoolbot commented Jan 22, 2010


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2010-01-22T01:10:34Z


Fixed in git for next release.

This was a much larger fix then I would have suspected, as "var x= value" has at lest 3 different contextual meanings. Regress well :)

@veripoolbot
Copy link
Contributor Author

@veripoolbot veripoolbot commented Feb 7, 2010


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2010-02-07T12:42:32Z


In 3.800.

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.