Epok Engine

EPOK RUNTIME

epok::bp::add

Function · 2 overloads

Function

Adds add as part of compiled Blueprint execution and object interaction.

Belongs to
epok::bp
Header
blueprint_runtime.hpp
Overloads
2

Declaration 1 of 2

Declaration
inline Fixed add(Fixed a, Fixed b)

Adds add as part of compiled Blueprint execution and object interaction.

ParameterTypeMeaning
aFixedValue supplied for a. Keep referenced or pointed-to data valid for the complete call.
bFixedValue supplied for b. Keep referenced or pointed-to data valid for the complete call.

Returns: Fixed. Check the value before continuing when it represents success, availability or a resource handle.

Example

C++ example
#include "blueprint_runtime.hpp"

// Assume these named values have been initialized with valid data:
// Fixed a
// Fixed b

auto result = epok::bp::add(a, b);

Why use it

It provides direct, allocation-conscious access to compiled Blueprint execution and object interaction. No exception-based error path is implied by the signature.

Trade-offs and warnings

This is classified as **Engine internal**. Prefer a higher-level Epok service unless you need this exact control.

Declared in runtime/blueprint_runtime.hpp:29

Declaration 2 of 2

template
Declaration
template<size_t Size> inline Vector<Size> add(const Vector<Size>& a, const Vector<Size>& b)

Adds add as part of compiled Blueprint execution and object interaction.

ParameterTypeMeaning
aconst Vector<Size> &Value supplied for a. Keep referenced or pointed-to data valid for the complete call.
bconst Vector<Size> &Value supplied for b. Keep referenced or pointed-to data valid for the complete call.

Returns: Vector<Size>. Check the value before continuing when it represents success, availability or a resource handle.

Example

C++ example
#include "blueprint_runtime.hpp"

// Replace these template arguments with types or values accepted by the declaration:
// Size

// Assume these named values have been initialized with valid data:
// const Vector<Size> & a
// const Vector<Size> & b

epok::bp& object = /* obtain a valid instance */;

auto result = object.add<Size>(a, b);

Why use it

Template dispatch is resolved at compile time and normally adds no runtime indirection.

Trade-offs and warnings

Every instantiated type must satisfy the header's compile-time requirements; extra instantiations can increase code size. This is classified as **Engine internal**. Prefer a higher-level Epok service unless you need this exact control. Pointer/reference arguments are borrowed unless the source contract says otherwise; keep them valid for the complete operation and never assume null is accepted.

Declared in runtime/blueprint_runtime.hpp:48

Related members