diff options
author | Sean MacLennan <seanm@seanm.ca> | 2019-01-20 13:24:25 +0700 |
---|---|---|
committer | Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2019-01-20 13:28:32 +0700 |
commit | a5e93e7222c55b2cf1ccc5e251de26e71a361e84 (patch) | |
tree | f441c4a2285cb5d52aad4f02e5ef1fe10d5dfac0 /system/execline/README | |
parent | 92a0d1f01a0949e54d711530f400c9ae7b8f0e96 (diff) |
system/execline: Added (non-interactive scripting language).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'system/execline/README')
-rw-r--r-- | system/execline/README | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/system/execline/README b/system/execline/README new file mode 100644 index 0000000000000..567b32fdb902e --- /dev/null +++ b/system/execline/README @@ -0,0 +1,14 @@ +execline is a (non-interactive) scripting language, like sh ; but its +syntax is quite different from a traditional shell syntax. The +execlineb program is meant to be used as an interpreter for a text +file; the other commands are essentially useful inside an execlineb +script. + +execline is as powerful as a shell: it features conditional loops, +getopt-style option handling, filename globbing, and more. Meanwhile, +its syntax is far more logic and predictable than the shell's syntax, +and has no security issues. + +execline requires skalibs at build time but not at run time. + +execline installs into /command to match the skarnet.org examples. |