Oil 0.8.pre11

2020-09-03

This is the home page for version 0.8.pre11 of Oil, a Unix shell. To use it,

These steps take 30 to 60 seconds on most machines. After that, you can assemble an oshrc file, which is described in the manual.

Test results, metrics, and benchmarks are shown below.

Download

Note: oil-native is a preview release, not a working shell.

Details are in the raw git change log. Not all changes affect the release tarball.
I sometimes write a release announcement with a high-level description of changes.

The Doc Overview links to all docs. It's work in progress, but these docs are ready:

Help topics for OSH and Oil. These documents underlies the help builtin.

Github Wiki for oilshell/oil. The Oil Deployments wiki page has other ways of getting Oil. These versions may not be up-to-date.

Spec Tests
- Oil Language Features
- OSH Survey. Test OSH with existing shells, and compare their behavior.
  - OSH in C++. Measuring the progress of Oil's C++ translation.
Wild Tests. Parse and translate thousands of shell scripts with OSH.
Unit Tests. Python unit test results.

Gold Tests. Compare OSH against bash (using implicit assertions, no golden output.)
osh2oil Tests. Test the conversion of OSH to Oil.
parse-errors. A list of all parse errors.
- parse-errors-oil-native. With the native binary.
runtime-errors. A list of shell runtime errors.
oil-runtime-errors. Oil language runtime errors.
arena. Testing an invariant for the parser.
osh-usage. Misc tests of the osh binary.
oshc-deps. Tests for a subcommand in progress.
opyc. Tests for the opyc tool.
Smoosh test suite (from mgree/smoosh):
- smoosh
- smoosh-hang
How many processes does Oil start compared to other shells?
- syscall/by-code
- syscall/by-input

Parser. How fast does OSH parse compared to other shells?
Runtime. How fast does OSH run shell scripts?
Compute. How fast does OSH run small programs without I/O?
Build. How long does it take for end users to build Oil? How big is the resulting binary?
Virtual Memory Baseline. How much memory do shells use at startup?

Lines of source, counted in different ways:
- osh-cloc. OSH and common libraries, as measured by the cloc tool.
- src. The whole Oil repo organized by type of source file.
- oil-cpp. The C++ code in the oil-native tarball.
- OPy. How much code is in the OPy toolchain?
Lines of dependencies:
- pydeps. Oil code plus the Python standard library.
- nativedeps. Oil code plus a slice of CPython.
Bytecode Metrics
- overview - Compare OPy vs. CPython.
- oil-with-opy - Oil compiled with OPy.
- oil-with-cpython - Oil compiled with CPython (for comparison).
- src-bin-ratio-with-opy - How big is the compiled output?
OVM / CPython
- overview - An analysis of GCC's compilation of OVM (a subset of CPython). Bloaty provides the underlying data.
- cpython-defs/overview - We try to ship as little of CPython as possible, and this is what's left.
oil-native. The future of Oil is pure native code.
- overview - Binary code size reported by Bloaty.

These files may help you understand how Oil is implemented, i.e. with domain-specific languages and code generation.

_devbuild/gen/id.h. A list of language elements, used in the lexer and in multiple parsers and evaluators.
The regex-based lexer uses two stages of code generation:
frontend/syntax.asdl. The syntax tree for OSH and Oil.
oil_lang/grammar.pgen2. The expression grammar for Oil. In contrast, the OSH parsers are hand-written.

Also see the oilshell/oil repository.

The OPy compiler is used to compile Oil to bytecode, but isn't itself part of the release.

Tree-shaking:

Generated on Wed Sep 2 18:12:45 PDT 2020