![Twitter Follow][twitter]
A shady game master approaches...
Hey there! You look like you would enjoy a good game of chance.
| ///! This package provides a skeleton for read-only access to FlatBuffer encoded binary data. | |
| const std = @import("std"); | |
| const assert = std.debug.assert; | |
| const t = std.testing; | |
| /// Header represents the data at offset 0 | |
| /// it consists of an unsigned offset to the root table | |
| /// and optionally a 4-byte file identifier | |
| const Header = packed struct { | |
| offset: u32, // root table offset |
This is an updated fork of this gist.
Logging functionality that supports:
I wanted to be really able to explain to a fair amount of detail how does the program :command:`ls` actually work right from the moment you type the command name and hit ENTER. What goes on in user space and and in kernel space? This is my attempt and what I have learned so far on Linux (Fedora 19, 3.x kernel).
How does the shell find the location of 'ls' ?

Author: Josef Jezek
sudo apt-get install python-setuptools