> For the complete documentation index, see [llms.txt](https://max-daunarovich.gitbook.io/flow-network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://max-daunarovich.gitbook.io/flow-network/introduction/terminology-and-syntax.md). # Terminology and Syntax ### Terminology In this document, the following terminology is used to describe syntax or behavior that is not allowed in the language: * `Invalid` means that the invalid program will not even be allowed to run. The program error is detected and reported statically by the type checker. * `Run-time error` means that the erroneous program will run, but bad behavior will result in the execution of the program being aborted. ### Syntax and Behavior Much of the language's syntax is inspired by Swift, Kotlin, and TypeScript. Much of the syntax, types, and standard library is inspired by Swift, which popularized e.g. optionals, argument labels, and provides safe handling of integers and strings. Resources are based on liner types which were popularized by Rust. Events are inspired by Solidity. **Disclaimer:** In real Cadence code, all type definitions and code must be declared and contained in contracts or transactions, but we omit these containers in examples for simplicity. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://max-daunarovich.gitbook.io/flow-network/introduction/terminology-and-syntax.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.