$$$$$$$$$$$$**$$$$$$$$$**$$$$$$$$$$$$$$$
$$$$$$$$$$" ^$$$$$$F *$$$$$$$$$$$$$
$$$$$$$$$ z$$$$$$L ^$$$$$$$$$$$$$
$$$$$$$$$ e$$$$$$$$$e J$$$$$$$$$$$$$
$$$$$$$$$eee$$$$$$$$$$$$$e$$$$$$$$$$$$$$
$$$$$$$$b$$$$$$$BARE$$$$$$$*$$$$$$$$$$$$
$$$$$$$)$$$$P"e^$$$F$r*$$$$F"$$$$$$$$$$$
$$$$$$$d$$$$ "z$$$$" $$$$% $3$$$$$$$$
$$$$*"""*$$$ .$$$$$$ z$$$* ^$e*$$$$$$
$$$" *$$ee$$$$$$$$$$*" $$$C$$$$$
$$$. "***$$"*"$$"" $$$$e*$$$
$$$b "$b.$$" $$$$$b"$$
$$$$$c. """ $$$$$$$^$
The first implementation of bare (called Lean as a word play for Lín, western representation of the chinese 林 - forest) was done resembling the Java runtime, where an intermediate representation is produced from the source code (Lean Code) and it is then executed in a compatible machine (such as the Lean Maschine). You can check out more details covering from the rationale to a deep analysis of how bare came to be right here (Pt-BR only).
python3 bare.py <path_to_source>
Garren Souza
Pedro L. Mondadori
