Morloc Manual

• 1. Intro

  Morloc replaces the application with the function as the unit you build, publish, and compose.

• 2. Why Morloc?

  Every command line tool solves the same problems a second time.

• 3. Getting Started

  Morloc is installed and managed by mim, the Morloc installation manager.

• 4. Syntax and Features

  Everything in Morloc is built out of functions, so this is where to start.

• 5. Advanced Types

  A Morloc term may have more than one definition, and the compiler picks whichever one produces the best program.

• 6. Building CLIs

  A Morloc module compiles to a command line tool.

• 7. Building APIs

  The docstrings are used for discoverability as well.

• 8. Managing Runs

  A morloc program is an executable that can dispatch work across multiple language pools and, optionally, remote compute nodes.

• 9. Utilities

  The nexus ships two utility subcommands that operate on data files without needing a compiled morloc program: file (identifies a file) and view (loads and...

• 10. Modules and Libraries

  Every Morloc file is a module.

• 11. Language Support

  Morloc compiles each part of a program with its own language toolchain.

• 12. Installation, Versions, and Deployment

  mim is distributed as a static binary for x86 Linux, Linux ARM, and Apple Silicon macOS.

• 13. Build Architecture

  A compiled Morloc program has two kinds of components: one nexus and one or more pools.

• 14. Future Directions
• 15. Q&A

  Yes, Morloc remains useful even if you only use one programming language.

• 16. Environmental Variable List

  Every environment variable that morloc reads or sets lives in the MORLOC_ namespace.

• 17. Contact

  This is a young project and any brave early users are highly valued.