Skip to content

Critical: code after EOF is ignored #34

@mzuenni

Description

@mzuenni

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...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions