Max Bernstein tekknolagi

## github.css
body {
  font-family: Helvetica, arial, sans-serif;
  font-size: 14px;
  line-height: 1.6;
  padding-top: 10px;
  padding-bottom: 10px;
  background-color: white;
  padding: 30px; }

body > *:first-child {

## ferengi-plan.txt
# The blog post that started it all: https://neocities.org/blog/the-fcc-is-now-rate-limited
#
# Current known FCC address ranges:
# https://news.ycombinator.com/item?id=7716915
#
# Confirm/locate FCC IP ranges with this: http://whois.arin.net/rest/net/NET-165-135-0-0-1/pft
#
# In your nginx.conf:

location / {

## why_spool.sh
#!/bin/sh

# Read _why's SPOOL in real time.
# Requires `lp` and a printer.

BASEURL=http://whytheluckystiff.net
if [ ! -d SPOOL ]; then
    mkdir SPOOL
fi

## lisp.c
#include <assert.h>
#include <stdarg.h>
#include <stdbool.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>

enum type {
    NIL,

## specification.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                tekknolagi
                / specification.md
            
            
              Created
              October 24, 2018 16:59
                — forked from rain-1/dcs.rkt
            
              
                Dotted Canonical S-expressions - DCSexps
              
          
    Dotted Canonical S-expressions - DCSexps

This is a specification for an s-expression interchange format that attempts to improve upon [2]rivest's canonical s-expressions.
It is an output format for a subset of s-expressions. Those containing only pairs and atoms.
It was designed with the following desirable properties in mind:

It has the canonicity property that (EQUAL? A B) implies the DCS output of A is byte equal to the DCS output of B.
It has the non-escaping property that arbitrary binary blobs can be contained as atoms without any processing. A consequence of this is that dcsexps can be nested easily.


## stack_machine.cpp
//
// Simple stack-based virtual machine tests.
//
// I use two slightly different strategies to manage the
// interpreter stack: First is using the "naive" approach
// of keeping a stack pointer that is bumped/decremented
// for every instruction that has stack operands. The second
// approach uses a "stack cache" register to cache the
// Top-of-Stack (TOS) value.
//

## enum_bitmask.hpp
/*
Type-safe enum class bitmasks.
Based on work by Andre Haupt from his blog at
http://blog.bitwigglers.org/using-enum-classes-as-type-safe-bitmasks/
To enable enum classes to be used as bitmasks, use the ENABLE_BITMASK_OPERATORS
macro:
  enum class MyBitmask {
     None = 0b0000,
     One = 0b0001,
     Two = 0b0010,

## strace-deps
#!/bin/bash

if [[ $# -lt 2 ]]; then
  echo "Usage: $0 <depfile> <command...>" >&2
  exit 1
fi

# The .d file we're going to write.
DEPSFILE=$1
shift

## sym_test.cc
#include <stdio.h>
#include <stdlib.h>
#include <cxxabi.h>
#include <link.h>

#include <string>
#include <vector>
#include <iostream>

using namespace std;

## python_make_github_issues.py
import json
import requests
import csv

# Authentication for user filing issue (must have read/write access to
# repository to add issue to)
USERNAME = 'username'
PASSWORD = 'password'

# The repository to add this issue to
	body {
	font-family: Helvetica, arial, sans-serif;
	font-size: 14px;
	line-height: 1.6;
	padding-top: 10px;
	padding-bottom: 10px;
	background-color: white;
	padding: 30px; }

	body > *:first-child {
	# The blog post that started it all: https://neocities.org/blog/the-fcc-is-now-rate-limited
	#
	# Current known FCC address ranges:
	# https://news.ycombinator.com/item?id=7716915
	#
	# Confirm/locate FCC IP ranges with this: http://whois.arin.net/rest/net/NET-165-135-0-0-1/pft
	#
	# In your nginx.conf:

	location / {
	#!/bin/sh

	# Read _why's SPOOL in real time.
	# Requires `lp` and a printer.

	BASEURL=http://whytheluckystiff.net
	if [ ! -d SPOOL ]; then
	mkdir SPOOL
	fi
	#include <assert.h>
	#include <stdarg.h>
	#include <stdbool.h>
	#include <stdio.h>
	#include <stdlib.h>
	#include <string.h>
	#include <unistd.h>

	enum type {
	NIL,
	//
	// Simple stack-based virtual machine tests.
	//
	// I use two slightly different strategies to manage the
	// interpreter stack: First is using the "naive" approach
	// of keeping a stack pointer that is bumped/decremented
	// for every instruction that has stack operands. The second
	// approach uses a "stack cache" register to cache the
	// Top-of-Stack (TOS) value.
	//
	/*
	Type-safe enum class bitmasks.
	Based on work by Andre Haupt from his blog at
	http://blog.bitwigglers.org/using-enum-classes-as-type-safe-bitmasks/
	To enable enum classes to be used as bitmasks, use the ENABLE_BITMASK_OPERATORS
	macro:
	enum class MyBitmask {
	None = 0b0000,
	One = 0b0001,
	Two = 0b0010,
	#!/bin/bash

	if [[ $# -lt 2 ]]; then
	echo "Usage: $0 <depfile> <command...>" >&2
	exit 1
	fi

	# The .d file we're going to write.
	DEPSFILE=$1
	shift
	#include <stdio.h>
	#include <stdlib.h>
	#include <cxxabi.h>
	#include <link.h>

	#include <string>
	#include <vector>
	#include <iostream>

	using namespace std;
	import json
	import requests
	import csv

	# Authentication for user filing issue (must have read/write access to
	# repository to add issue to)
	USERNAME = 'username'
	PASSWORD = 'password'

	# The repository to add this issue to