all releases |
oilshell.org
Oil 0.7.pre5
2019-10-04
This is the home page for version 0.7.pre5 of Oil, a Unix shell. To use it,
- Download a source tarball.
- Build and install it, as described in INSTALL.
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
|
File / SHA256 checksum |
Size |
|
|
oil-0.7.pre5.tar.xz |
1,065,312 |
|
6c472c8bf2b35e7feadde54e89c3824709e56be4ea6aeed18cfc5c8a7c25f3ee |
|
oil-0.7.pre5.tar.gz |
1,457,567 |
|
6f5871975c73366a9a908af4eb648cd04c5504bee2f3ea3eecbf353bb7e4f77e |
What's New
Documentation
Metrics
- Lines of source, counted in differented ways:
- osh-cloc. OSH and common
libraries, as measured by the cloc tool.
- src. The whole Oil repo organized by
type of source file.
- 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
- Native Code Metrics
- 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.
Tests
More tests:
OPy Tests
The OPy compiler is used to compile Oil to bytecode, but isn't itself part of
the release.
Tree-shaking:
Manual Tests
- [ ] Test build and install on OS X
Benchmarks
Source Code
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.
Generated on Thu Oct 3 21:53:41 PDT 2019