Infant Lang Errors

note

Some errors are likely to be changed in the future versions of Infant Lang.

Tokenization Error

Tokenization error gets thrown when the tokenizer encounters an unexpected character.

The Interpreter will also show the line number and the character which caused the error.

Let's see why this error is thrown:

token.infant

moce pointer right 15

In the above code, instead of the move keyword, we misspelled the move keyword as moce. Infant Lang sees that the moce keyword is not a valid keyword and throws a Tokenization Error.

💀 Tokenization Error:
Unknown token: "c" at line 1
moce pointer right 15
  👆

Defined in the errors.go as

func printError(line string, lineNumber int, i int) 

Expected Token Error

Expected Token error gets thrown when the parser expects a token to execute but it couldn't find it.

The Interpreter will also show the line number and the character which caused the error.

Let's see why this error is thrown:

expected.infant

memory = 

In the above code, we did not assign a value to the memory. Infant Lang sees that we did not assign a value to the memory and throws an Expected Token Error. It expects a number or a pointer.

💀 Token was Expected
Expected 'pointer or memory or number' at line number '1'
👉 memory =

It is defined in the errors.go file

func printExpectedTokenError(line string, lineNumber int, expectedToken string)

Unexpected String Error

UnExpected String error gets thrown when the parser finds a legal token but it expects a different token.

The Interpreter will also show the line number and the character which caused the error.

Let's see why this error is thrown:

unexpected.infant

memory pointer pointer

In the above code, we have two pointers. Infant Lang sees that we have two pointers and throws an Unexpected String Error. It expects an assignment operator.

💀 Unexpected String Literal
Unexpected String Literal 'pointer' at line number '1'
👉 memory pointer pointer

It is defined in the errors.go file.

func printParseError(line string, lineNumber int, token string)

Runtime Error

Runtime error gets thrown when the interpreter encounters an error during the execution of the program. It's usually thrown if the interpreter finds a logical error in the program.

Let's look at an example:

runtime.infant

memory = 1 / 0

In the above code, we divide the memory by zero. Infant Lang sees that we are trying to divide the memory by zero and throws a Runtime Error.

💀 Runtime Error
Cannot Divide Entity by Zero at line number '1'
👉 memory = 1 / 0

Other Runtime Errors:

There are other runtime errors that can be thrown by the interpreter. These errors often stop the execution of the program.

• Pointer can't point to a negative box

  When the interpreter tries to point to a negative box, it throws a Pointer can't point to a negative box error.

• Negative number. Memory Cannot Hold Negative Numbers

  When the interpreter tries to store a negative number in the memory, it throws this error. It is often thrown when the memory is initialized with a negative number or initialized by an arithmetic operation that results in a negative number.

• Memory Cannot Have Decimal Values

  When the interpreter tries to store a decimal number in the memory, it throws a Memory Cannot Have Decimal Values error. Often thrown when the memory is initialized with a decimal value or initialized by an arithmetic operation that results in a decimal value.

Defined in the errors.go file as

func runtimeError(line string, lineNumber int, errorMessage string)

File Access Error

File Access Error gets thrown when the interpreter tries to access a file that does not exist. Possible Solutions:

• Check if the file exists.
• Check if the file is a valid file. (It's not a directory or a binary file)

Example:

infant no.infant

💀 Unable to Access File: no.infant
Error: open no.infant: The system cannot find the file specified.

Defined in the errors.go file as:

func printFileAccessError(errorMessage string, err string)

No Arguments Error

No Arguments Error gets thrown when the interpreter tries to execute a command without any arguments. Possible Solutions:

• Check if the command has a file name as an argument.
• Check if the command has a valid flag. For eg. infant -v

Example:

infant
💀 No file name provided. Please provide a file name.
Usage: infant <filename>.infant

💀 Exiting...

Defined in the errors.go file.

func noArguments() {
    fmt.Println("\n💀 No file name provided. Please provide a file name.")
    fmt.Println("Usage: infant <filename>.infant")
    fmt.Println("\n💀 Exiting...")
    os.Exit(1)
}

info

The No Arguments Error will be removed in the future builds, for Infant Lang has plans for implementing an Interpreter Mode.