RFC6901 JSON pointers.

Sourceexception Jsonptr_illegal_pointer_notation of string * int * string
Sourceexception Jsonptr_unsupported_path_item of Json_query.path_item * string
Sourceval pp_rfc6901_token : Restapis_o.Open__.Format.formatter -> string -> unit

Print a RFC6901 token. Conforms to RFC6901 Syntax.

Sourceval pp : ?wildcards:bool -> Restapis_o.Open__.Format.formatter -> [< `Field of string | `Index of int | `Next | `Star ] list -> unit
Sourceval show : ?wildcards:bool -> [< `Field of string | `Index of int | `Next | `Star ] list -> string
Sourceval compare : ?wildcards:bool -> [< `Field of string | `Index of int | `Next | `Star ] list -> [< `Field of string | `Index of int | `Next | `Star ] list -> int
Sourceval path_of_json_pointer : ?wildcards:bool -> string -> [> `Field of string | `Index of int | `Next ] list
Sourceval of_fragment_identifier : ?wildcards:bool -> string -> [> `Field of string | `Index of int | `Next ] list
Sourceval path_of_fragment : string -> [> `Field of string | `Index of int | `Next ] list
include DkCoder_Std.SCRIPT
Sourceval __init : DkCoder_Std.Context.t -> unit

__init context is the entry point for running a script module. The DkCoder compiler will inject this function at the top and bottom of the script module. The top __init does nothing, while the bottom __init calls the prior __init.

That means:

  1. calling the __init function guarantees that the script module is initialized; that is, all of the script module's side-effects (ex. let () = Format.printf "Hello world@.") are executed before the __init returns to the caller.
  2. you can override the __init function by simply defining the __init idempotently. That will shadow the top __init and when the bottom __init is executed your __init will be called instead of the do-nothing top __init.

Future versions of DkCoder will call __init in dependency order for all `You script modules. Your __init function may be called several times.

Sourceval __repl : DkCoder_Std.Context.t -> unit

__repl context is the entry point for debugging a script module in a REPL. The DkCoder compiler will inject this function at the top and bottom of the script module. The top __repl does nothing, while the bottom __repl calls the prior __repl.

That means:

  1. you can override the __repl function by simply defining the __repl idempotently. That will shadow the top __repl and when the bottom __repl is executed your __repl will be called instead of the do-nothing top __repl.
Sourceval __module_info : unit -> DkCoder_Std.ModuleInfo.t

The run-time module information for the script module.