AkitaCode Compiler Errors

In this page you can found all return codes of AkitaCode make() function. The following list contains the return code, the type of error occurred before/during/after compile ATD files and a short orientating explanation and causes for each error may occur.

Code	Type	Explanation
0	Success	The build completed successfully. You should see the resulting file in the specified directory.
1	Success	The structural analysis of the ATD document is successfully completed.
2	Success	The ATD document data analysis is successfully completed.
3	MakeError	Error generating the AKITA file. Some of the causes may be that there is not enough space on the hard drive or that the output directory is read-only or that you do not have sufficient privileges to write to said directory.
4	PathError	Indicates that the ATD file is not located in the specified path or that you do not have sufficient privileges to open the file.
5	DatabaseError	The specified database does not exist, is currently in use, or you do not have sufficient privileges to open it. In case it is in use, you must close all previously established connections with the database.
6	SyntaxError	Syntax error in ATD code. Review the line indicated by the error displayed by the queue.
7	Success	Indicates that the syntax of a document line is correct. This return code should never appear to you because it is managed by an internal module.
8	StructureError	An existing protocol is required before performing any other operations.
9	StructureError	An attempt was made to declare a virtualized situation outside of an environment. You must first declare an environment and then declare the virtualized situation.
10	StructureError	An instance of this type was not expected on the indicated line.
11	StructureError	An instance of this type was not expected on the indicated line.
12	StructureError	An instance of this type was not expected on the indicated line.
13	StructureError	An instance of this type was not expected on the indicated line.
14	StructureError	A time instance has already been declared. The error occurs because another time instance has been declared without having added variables or functions in the previous time instance.
15	StructureError	The error occurs because you are trying to terminate an instance before defining variables or functions after an instance of time.
16	StructureError	An instance of this type was not expected on the indicated line.
17	UnexpectedError	Unexpected error upon completion of structural check. Check the structure of the ATD file.
18	ProtocolError	The declared protocol does not exist in the database.
19	VariableError	The declared variable does not exist in the specified protocol.
20	ValueError	The value assigned to the variable exceeds the minimum and maximum limit allowed. Check that the assigned value meets the requirements of the variable.
21	ValueError	The value assigned to the variable exceeds the maximum limit allowed. Check that the assigned value meets the requirements of the variable.
22	ValueError	The value assigned to the variable exceeds the maximum limit allowed. Check that the assigned value meets the requirements of the variable.
23	ValueError	It was not possible to calculate the length in bits of the value assigned to the variable.
24	ValueError	The reserved constants "True" and "False" can only be used in variables and arguments that have the property of being boolean.
25	ValueError	This error occurs when you are trying to assign an expected value to another expected value. In AkitaCode it is allowed to assign a value of a set variable to an expected variable or argument, but it is not possible to use an expected variable or argument as the value of another expected variable or argument.
26	ValueError	This error occurs when a value is assigned to an expected variable or argument that does not match its length in bits.
27	ValueError	This error occurs when a value is assigned to an expected variable or argument that does not match its type. You cannot assign an unsigned value to a signed variable or argument and vice versa.
28	AssignmentError	This error indicates that the variable has not been previously declared.
29	ValueError	The value assigned to the variable or argument is not a valid value. The AkitaCode compiler allows you to assign values in decimal (16), octal (0o20), hexadecimal (0x10), and binary (0b10000).
30	FunctionError	The declared function does not exist in the specified protocol.
31	FunctionError	The number of arguments of the declared function does not match the number of arguments defined in the database. Check that all arguments are defined.
32	ArgumentError	The declared argument does not exist. The error queue itself tells you all the arguments defined for the instantiated function.
33	ArgumentError	The declared argument does not exist. The error queue itself tells you all the arguments defined for the instantiated function.
34	ValueError	The value assigned to the argument exceeds the minimum and maximum limit allowed. Check that the assigned value meets the requirements of the variable.
35	ValueError	The value assigned to the argument exceeds the maximum allowable limit. Verify that the assigned value meets the requirements of the argument.
36	ValueError	The value assigned to the argument exceeds the maximum allowable limit. Verify that the assigned value meets the requirements of the argument.
37	ValueError	It was not possible to calculate the length in bits of the value assigned to the argument.
38	ValueError	This error occurs when you try to assign an expected value to another expected value. AkitaCode allows you to assign a value of a set variable to an expected variable or argument, but you cannot use an expected variable or argument as the value of another expected variable or argument.
39	ValueError	This error occurs when a value is assigned to an expected variable or argument that does not match its length in bits.
40	ValueError	This error occurs when a value is assigned to an expected variable or argument that does not match its type. You cannot assign an unsigned value to a signed variable or argument and vice versa.
41	AssignmentError	This error indicates that the variable has not been previously declared.
42	ValueError	The value assigned to the variable or argument is not a valid value. The AkitaCode compiler allows you to assign values in decimal (16), octal (0o20), hexadecimal (0x10), and binary (0b10000).
43	ValueError	The declared variable does not exist in the specified protocol.
44	ForValueError	This error indicates that the generation of an expected variable is being declared within a "For" instance. This operation is not allowed in AkitaCode, since expected variables cannot generate situational environment conditions.
45	TypeError	This error appears when there is an internal compiler error and an instance type is accepted that is not yet allowed in AkitaCode.
46	MakeError	An unexpected error occurred during the compilation of the ATD file.