Chapter 6.1: Errors

At some point, your program will fail. Whether it’s a missing a closing bracket, a typo, or trying to add a number to a string, errors happen.

But don’t worry, GLang won’t set your computer on fire when something goes wrong. Instead, it safely reports the issue right in your terminal.

1 / 0; # dividing by zero causes an error

And the output:

Error: division by zero
| in > example.glang:1:5
|
| 1 / 0; # dividing by zero causes an error
|     ^

What The Error Says

GLang highlights exactly where things went wrong, showing you the offending line and character.

• Error: tells you what error occured.
• in > indicates where and what file caused the issue.
• ^ shows what code stopped the program's execution

Sometimes, you’ll also get a helpful hint to steer you in the right direction:

Error: variable name 'example' is undefined
| in > <stdin>:1:1
|
| example
| ^^^^^^^ help: define a variable with the syntax 'obj <variable name> = <value>;'

Tracebacks

Sometimes, multiple errors appear at once. This is called a traceback. A traceback happens when an error is propagated upward through the code, from where it occurs to wherever the function was called.

For example, consider the push function:

push("", "");

Here, both arguments are strings, but push expects the first argument to be a list. GLang first detects the problem inside its library code, then reports it again at the point where you called the function.

That’s why you’ll see two errors:

Error: argument 'list' must be type list
| in > library/fundamental/list.glang:7:9
|
|         uhoh("argument 'list' must be type list");
|         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Error: argument 'list' must be type list
| in > example.glang:1:1
|
| push("", "");
| ^^^^^^^^^^^^

The first error shows where the problem started (inside the GLang library). The second shows where it reached the code.