6.7.1 Runtime Systems

Stand-alone applications containing debugged Prolog code and destined for end-users are typically packaged as runtime systems. No SICStus license is needed by a runtime system. A runtime system has the following limitations:

• No top-level. The executable will restore a saved-state and/or load code, and call user:runtime_entry(start). Alternatively, you may supply a main program and explicitly initialize the Prolog engine with SP_initialize(). break/0 and require/1 are unavailable.
• No debugger. The Prolog flags debug and debugger_print_options have no effect. Predicates annotated as [development] in the reference pages are unavailable.
• Except in extended runtime systems: no compiler; compiling is replaced by consulting. Extended runtime system contains the compiler.
• The Prolog flags discontiguous_warnings, redefine_warnings, single_var_warnings have no effect. The user is not prompted in the event of name clashes.
• The informational Prolog flag is off by default, suppressing informational messages.
• No profiler. The predicates profile_data/4 and profile_reset/1 are unavailable.
• No signal handling except as installed by SP_signal().