Codex

macOSLinuxWindowswasm

#import "Codex";

USAGE_MODE says what an importer does with the module: record a build (.WRITE, the default) or read a recorded one back (.READ), or both. Every declaration is available in every mode.

Procedures#

Codex inspection#

get_file_and_module

(node: *Code_Node) -> (file: *Message_File, import: *Message_Import)

is_global_ident

(ident: *Code_Ident) -> bool

Codex lifetime#

deinit

(help: *Codex_Help)

Codex wire values#

put2 overloads

(builder: *String_Builder, x: $T)

get2 overloads

(s: *string, x: *$T)

put_short_string

(builder: *String_Builder, s: string, $count_type: Type, $zero_terminated := false)

get_short_string

(input: *string, $count_type: Type, error: *bool, $allocate := true, $zero_terminated := false) -> string

Codex wire reader#

make_help

(memory: [] u8) -> (success: bool, help: Codex_Help, error_string: string)

dump_file

(name: string) -> bool

Codex plugin#

get_plugin

() -> *Metaprogram_Plugin

init

(p: *Metaprogram_Plugin, options: [] string) -> bool

communication_proc

(_p: *Metaprogram_Plugin, key: string, value: string) -> bool

message

(p: *Metaprogram_Plugin, message: *Message)

log_help

(p: *Metaprogram_Plugin)

finish

(p: *Metaprogram_Plugin)

shutdown

(p: *Metaprogram_Plugin)

Codex metrics#

collect_metrics

(tc: Typechecked(Code_Procedure_Body)) -> metrics: Metrics

Types#

Metricsstruct

:: struct

Revision_Control_Typeenum

:: enum

Canonical public records; declaration order follows their dependency graph.

Module_Recordstruct

:: struct

File_Recordstruct

:: struct

Procedure_Recordstruct

:: struct

Header_Recordstruct

:: struct

Codex_Helpstruct

:: struct

Constants#

Math

:: Math_Module

HELP_STRING

:: "Codex: -export_file <path> (default exported.codex)\n"