Skip to content

exit codes #71

Description

@pazz

It'd be convenient to encourage different outcomes, especially failures, into exit codes.

For example,

  • 0: all good and the given instance is positive.
  • -1: all good but the given instance is negative
  • 1: input could not be read
  • 2: input could not be parsed into an automaton

This way, one could fit instance use the new output argument -o that writes winning strategies to a file, say as tex, and then only compile this in case the output was written, using the shell's && operator.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions