4. Embedding and Integration

This section explains how to embed the daslang scripting language into a host application written in C++ or C (and, by extension, any language that can call C functions). It is organized from simple to advanced:

• Quick Start — minimal host program, compilation, and evaluation

• C++ API Reference — modules, function/type/enum bindings, cast infrastructure

• C API Reference — the daslang/c_api/c_api.h header for C-only hosts and FFI

• External Modules — building and distributing modules outside the main source tree, .das_module descriptors, find_package(DAS)

• Advanced Topics — AOT compilation, standalone contexts, class adapters

For step-by-step walk-throughs with complete, compilable source code, see the C++ integration tutorials and C integration tutorials.

• 4.1. Quick Start
  • 4.1.1. Virtual machine overview
    • 4.1.1.1. Execution context
  • 4.1.2. Minimal host program
  • 4.1.3. Key types
  • 4.1.4. Calling daslang functions with arguments
  • 4.1.5. Next steps
• 4.2. C++ API Reference
  • 4.2.1. Creating a module
    • 4.2.1.1. ModuleAotType
    • 4.2.1.2. Embedding daslang source in modules
    • 4.2.1.3. Builtin module constants
  • 4.2.2. Binding C++ types
    • 4.2.2.1. ManagedStructureAnnotation
    • 4.2.2.2. DummyTypeAnnotation
    • 4.2.2.3. ManagedVectorAnnotation
    • 4.2.2.4. ManagedValueAnnotation
    • 4.2.2.5. TypeAnnotation virtual methods
  • 4.2.3. Cast infrastructure
  • 4.2.4. Binding C++ functions
    • 4.2.4.1. addExtern + DAS_BIND_FUN
    • 4.2.4.2. Binding C++ methods
    • 4.2.4.3. Binding operators
    • 4.2.4.4. addInterop — low-level binding
  • 4.2.5. Binding C++ enumerations
  • 4.2.6. Function side effects
  • 4.2.7. Callbacks — blocks, functions, lambdas
  • 4.2.8. File access
  • 4.2.9. Project file resolution
• 4.3. C API Reference
  • 4.3.1. When to use the C API
  • 4.3.2. Initialization and shutdown
  • 4.3.3. Text output
  • 4.3.4. File access
  • 4.3.5. Compilation
    • 4.3.5.1. Compilation policies
  • 4.3.6. Simulation and context
  • 4.3.7. Function evaluation
    • 4.3.7.1. Aligned (vec4f)
    • 4.3.7.2. Unaligned (vec4f_unaligned)
    • 4.3.7.3. Complex results (cmres)
  • 4.3.8. Argument helpers
  • 4.3.9. Calling lambdas and blocks
  • 4.3.10. Binding C functions
  • 4.3.11. Binding types
    • 4.3.11.1. Structures
    • 4.3.11.2. Enumerations
    • 4.3.11.3. Type aliases
  • 4.3.12. String allocation
  • 4.3.13. Context variables
  • 4.3.14. Serialization
  • 4.3.15. AOT checking
  • 4.3.16. Module groups
  • 4.3.17. Side effects
• 4.4. External Modules
  • 4.4.1. Overview
  • 4.4.2. Module types
  • 4.4.3. The .das_module descriptor
    • 4.4.3.1. Registration functions
    • 4.4.3.2. Complete examples
  • 4.4.4. Module resolution order
  • 4.4.5. Building a C++ module
    • 4.4.5.1. C++ module class
    • 4.4.5.2. C module (using the C API)
    • 4.4.5.3. CMake setup
    • 4.4.5.4. AOT for external modules
  • 4.4.6. Building a pure daslang module
  • 4.4.7. Using an external module from a host application
    • 4.4.7.1. Dynamic module discovery
  • 4.4.8. Installing external modules
  • 4.4.9. Example: dascript-demo
  • 4.4.10. In-tree modules vs external modules
• 4.5. Advanced Topics
  • 4.5.1. AOT compilation
    • 4.5.1.1. AOT pipeline overview
    • 4.5.1.2. AOT annotations
    • 4.5.1.3. AOT template functions
    • 4.5.1.4. AOT type customization
  • 4.5.2. Class adapters
    • 4.5.2.1. Pattern overview
  • 4.5.3. Coroutines (generators)
    • 4.5.3.1. Consuming a generator
  • 4.5.4. Dynamic script generation
    • 4.5.4.1. Context variables
  • 4.5.5. Standalone contexts
  • 4.5.6. Serialization
  • 4.5.7. Sandboxing
  • 4.5.8. File access customization