> For the complete documentation index, see [llms.txt](https://boxlang.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boxlang.ortusbooks.com/boxlang-language/reference/lexical-elements/semicolons.md).

# Semicolons

In BoxLang, semicolons may used to separate statements in script syntax. This is similar to their use in many other programming languages like JavaScript, Java, or C#. Statements on separate lines, however, do not require semicolons for separation.

A basic example using semicolons for termination on a single line:

```boxlang
var x = 10;
var y = 20;
var sum = x + y;
```

In this example, each line is a separate statement, and each statement is terminated with a semicolon.

Once again, semicolons are optional and may be omitted, especially when each statement is on a new line. If you want to put multiple statements on a single line, however, then semicolons become necessary to separate them:

```boxlang
var x = 10; var y = 20; var sum = x + y;
```

In this case, without the semicolons, the above code would fail to compile and would be syntactically incorrect.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://boxlang.ortusbooks.com/boxlang-language/reference/lexical-elements/semicolons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.