Class Ek9ExitCodes
java.lang.Object
org.ek9lang.compiler.common.Ek9ExitCodes
Defines all exit codes used by the EK9 compiler and generated code.
These exit codes form an internal protocol between the compiler and the
ek9 wrapper, which maps some codes to follow Unix conventions.
The ek9 wrapper (ek9.c) translates these internal codes: - Exit code 0: Wrapper executes command from stdout, returns program's exit code - Exit code 1: Wrapper maps to 0 (Unix success for operations with no program to run) - Exit codes 2-10: Wrapper returns same code (various error conditions)
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final int
Exit code 4: Invalid combination of parameters.static final int
Exit code 2: Invalid command line parameters.static final int
Exit code 8: Compilation failed with errors.static final int
Exit code 3: File processing error.static final int
Exit code 7: Language Server failed to start.static final int
Exit code 5: No programs found.static final int
Exit code 9: Wrong number of program arguments.static final int
Exit code 10: Cannot convert argument to required type.static final int
Exit code 6: Program not specified.static final int
Exit code 0: Compiler prints command to run.static final int
Exit code 1: Operation successful, nothing to run. -
Method Summary
-
Field Details
-
RUN_COMMAND_EXIT_CODE
public static final int RUN_COMMAND_EXIT_CODEExit code 0: Compiler prints command to run. The wrapper executes that command and returns the program's exit code.- See Also:
-
SUCCESS_EXIT_CODE
public static final int SUCCESS_EXIT_CODEExit code 1: Operation successful, nothing to run. Examples: -C compile only, -V version, -Gk generate keys, -PV print version. The wrapper maps this to 0 (Unix success).- See Also:
-
BAD_COMMANDLINE_EXIT_CODE
public static final int BAD_COMMANDLINE_EXIT_CODEExit code 2: Invalid command line parameters. The command line parameters provided were not valid or could not be parsed.- See Also:
-
FILE_ISSUE_EXIT_CODE
public static final int FILE_ISSUE_EXIT_CODEExit code 3: File processing error. The specified file was not found, could not be read, or had missing content.- See Also:
-
BAD_COMMAND_COMBINATION_EXIT_CODE
public static final int BAD_COMMAND_COMBINATION_EXIT_CODEExit code 4: Invalid combination of parameters. The parameters provided were individually valid but incompatible when used together.- See Also:
-
NO_PROGRAMS_EXIT_CODE
public static final int NO_PROGRAMS_EXIT_CODEExit code 5: No programs found. The EK9 file does not contain any programs that can be executed.- See Also:
-
PROGRAM_NOT_SPECIFIED_EXIT_CODE
public static final int PROGRAM_NOT_SPECIFIED_EXIT_CODEExit code 6: Program not specified. The EK9 file contains more than one program, and you must specify which to run.- See Also:
-
LANGUAGE_SERVER_NOT_STARTED_EXIT_CODE
public static final int LANGUAGE_SERVER_NOT_STARTED_EXIT_CODEExit code 7: Language Server failed to start. The EK9 compiler could not start in Language Server Protocol mode.- See Also:
-
COMPILATION_FAILED_EXIT_CODE
public static final int COMPILATION_FAILED_EXIT_CODEExit code 8: Compilation failed with errors. The EK9 source code contains syntax errors, type errors, or other compilation issues.- See Also:
-
PROGRAM_ARGUMENT_COUNT_MISMATCH_EXIT_CODE
public static final int PROGRAM_ARGUMENT_COUNT_MISMATCH_EXIT_CODEExit code 9: Wrong number of program arguments. The program requires a specific number of arguments, but a different number was provided. This is detected during the generated code's argument validation.- See Also:
-
PROGRAM_ARGUMENT_TYPE_MISMATCH_EXIT_CODE
public static final int PROGRAM_ARGUMENT_TYPE_MISMATCH_EXIT_CODEExit code 10: Cannot convert argument to required type. A program argument could not be converted to the type required by the program's parameter. This is detected during the generated code's argument conversion.- See Also:
-