KAL modules & IMPORT

IMPORT pulls constants and functions out of a named module so several scripts can share one implementation.

Syntax#

IMPORT { symbol1, symbol2 } FROM "module_name";

• Exactly one line, at the top of the file, before the AUTOMATION block.
• Up to 32 imports per script.
• Module names are letters, digits, - and _.

What a module contains#

A module is KAL source whose AUTOMATION block holds only CONSTANT and FUNCTION declarations — no triggers, no actions at module level, no nested imports:

// inside module "pricing_lib"
AUTOMATION pricing_lib {
    CONSTANT TAX_RATE = 1.08;

    FUNCTION with_tax(amount AS NUMBER) AS NUMBER {
        RETURN amount * TAX_RATE;
    }
}

Using an import#

KAL VERSION 2.0;
IMPORT { with_tax, TAX_RATE } FROM "pricing_lib";
AUTOMATION checkout {
    WHEN COMMAND total (price AS NUMBER) {
        REPLY "With tax: " + ("" + with_tax(price));
    }
}

(This example is shown as a fragment because modules must exist in your server's module registry for the import to resolve — an unregistered module is a compile error, not a runtime surprise.)

How resolution works#

• Modules are registered per server. An import resolves against your server's module library only — there is no global library, no file system and no URL fetching.
• Missing module → M001_MODULE_NOT_FOUND. Missing symbol → M003_EXPORT_NOT_FOUND.
• There is currently no dashboard page for uploading modules; the library is managed by the platform. Marketplace packages that need shared code declare it in their package rather than reaching into other servers' registries.

Limits#

The M-error family#