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

Jump to bottom

Check on variable initialization is not only done at highest statement level #84

Closed
meijeru opened this issue Jun 9, 2011 · 1 comment
Closed

Check on variable initialization is not only done at highest statement level #84

meijeru opened this issue Jun 9, 2011 · 1 comment
Labels
status.built A change in codebase has been done to address the ticket. status.tested The change in code has been manually tested and verified to fix the issue.

Comments

@meijeru
Copy link
Contributor

meijeru commented Jun 9, 2011

Compiling

if false [s: 1] print form s

one gets the result 1, and no complaint about lack of initialization. I would submit that initialization should be checked only with assignments that occur as direct (first-level) elements of a program or function body.
dockimbel added a commit that referenced this issue Jun 20, 2011
@dockimbel
FIX: issue #84 (Check on variable initialization is not only done at …
31b87b9 
…highest statement level)

FIX: byte unit test not conforming to new initialization restriction
DOCS: added variable initialization at root level restriction description
@dockimbel
Copy link
Member

Such code will now raise a compilation error.

Tested OK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status.built A change in codebase has been done to address the ticket. status.tested The change in code has been manually tested and verified to fix the issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dockimbel @meijeru