-
Notifications
You must be signed in to change notification settings - Fork 28
Open
Description
reading the spec I would say that EOF should be identical to ASSERT(ISEOF). However, it seems like the actual implementation stops after encountering EOF. The following checker accepts an empty:
EOF
ASSERT(1!=1)
I would say that is a (critical) error. The ASSERT should be executed and therefore the validator should reject everything.
I have also found at least one checker that assumed that code /asserts are still executed after the EOf...
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels