lc-run [OPTION ...] [--handler NAME] [--] LCMFILE [ARG ...]
lc-run [OPTION ...] --list-handlers [--] LCMFILE
lc-run runs a LiveCode Builder program from the bytecode file LCMFILE.
When running an LCB program with lc-run, some standard libraries are
unavailable (e.g. the canvas and engine libraries).
lc-run can use any public, top-level handler with no arguments as an entry
point. If the --handler option is not used to specify an entry point
NAME, then lc-run looks for a handler named main().
The --list-handlers option can be used to obtain a list of valid entry points
for a particular LCMFILE.
Any arguments ARG... specified after LCMFILE are available to the program as
the value of the command arguments.
-
-l, --load LCMLIB: In addition to loading the LCMFILE, load the bytecode file LCMLIB. Any number of
--loadoptions may be provided. LCMFILE is loaded first, followed by each LCMLIB in reverse order. -
-H, --handler NAME: Call the handler with the specified NAME as the entry point of the program. NAME must have public visibility and accept no arguments. The default value of NAME is
main. -
--list-handlers: Don't run the program. Instead, print a list of valid entry point handlers in LCMFILE to standard output.
-
-h, --help: Print some basic usage information.
-
--: Stop processing options. This is useful in case LCMFILE begins with
-or--.
lc-run has experimental support for multi-module LCB bytecode assemblies. A bytecode assembly is created by simply concatenating a set of module files generated by lc-compile(1).
When an assembly is passed as the main LCMFILE to be run by lc-run, only the handlers in the first module in the assembly are considered as valid entry points.
Copyright 2015-2016 LiveCode Ltd.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
lc-compile(1).