p7g

0   .................+.....................................................................
1   ................ooo....................................................................
2   ...............ooooo...................................................................
3   ..............ooooooo..................................................................
4   .............ooooooooo.................................................................
5   ............ooooooooooo................................................................
6   ...........ooooooooooooo...............................................................
7   ..........ooooooooooooooo..............................................................
8   .........ooooooooooooooooo.............................................................
9   ........ooooooooooooooooooo............................................................

p7g

how to use

You are the signalling server

1. turn on camera on both (dunno if required)
2. create a peer on both
3. create offer on one, paste into "add remote session description form" and submit
4. copy answer from previous step and paste into "add remote session description form" in other client, submit
5. copy ice candidates array from each client and paste into "add ice candidate" on other, submit both

p7g

#lang racket

(define (tape-new)
  (cons 0 (make-vector 1 0)))

(define (tape-inc tape amount)
  (let ([pos (car tape)]
        [vec (cdr tape)])
    (vector*-set! vec pos (+ (vector-ref vec pos) amount))))

p7g

"""
This is a really basic and dumb regexp engine to play with composable regular
expressions.

A Re object is basically just a pointer to some initial state and to some
accepting state. These states can each point to other states, forming an NFA-ε,
which can then be evaluated directly.

The cool thing is that you can just combine Re objects like this:

p7g

import textwrap
from csnake import (
    AddressOf,
    CodeWriter,
    Function,
    TextModifier,
    Variable,
)

p7g

// vim: ft=java

import joe.collections.ArrayList;
import joe.fs.File;
import joe.io.StdOut;
import joe.io.StdErr;

class Tape {
    final ArrayList<uint> data;
    uint pos;

p7g

import operator

nil = ()

def nilp(l):
	return l == nil

def cons(a, b):
	return a, b

p7g

#include <stdlib.h>
#include <stdio.h>

struct tape {
	unsigned pos, capacity;
	unsigned char *data;
};

void tape_init(struct tape *t)
{

p7g

"""Ask clang what a struct looks like

Structs like stat don't necessarily have the same fields in the same order on
different platforms. This makes writing a language with C FFI sound pretty
awful... since all the different platforms would need to be handled by the FFI
library of that language. Maybe with something like this, the C compiler could
be queried to find out what these structs look like?
"""

import io

p7g

use std::collections::BTreeSet;

type Point = [i64; 3];
type Rotation = [u8; 3];

#[derive(Debug)]
struct Orientation {
    signs: [i8; 3],
    rotation: Rotation,
}