> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/9.0/developer-guide/idc/core-concepts/functions.md).

# Functions

An IDC function always returns a value. There are 2 kinds of functions:

* [built-in](/9.0/developer-guide/idc/idc-api-reference/alphabetical-list-of-idc-functions.md) functions
* user-defined functions A user-defined function is declared this way: static func(arg1,arg2,arg3) { [statements](/9.0/developer-guide/idc/core-concepts/statements.md) ... } It is not necessary to specify the parameter types because all necessary type conversions are performed automatically.

By default all function arguments are passed by value, except:

```
  - objects are always passed by reference
  - functions are always passed by reference
  - it is possible to pass a variable by reference using the & operator
```

If the function to call does not exist, IDA tries to resolve the name using the debugged program labels. If it succeeds, an [dbg\_appcall](/9.0/developer-guide/idc/idc-api-reference/alphabetical-list-of-idc-functions/1572.md) is performed.


---

# 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://docs.hex-rays.com/9.0/developer-guide/idc/core-concepts/functions.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.