pmwhite

hw1WriteData: hw1WriteData.c
	gcc -o hw1WriteData hw1WriteData.c

hw1ReadData: hw1ReadData.c
	gcc -o hw1ReadData hw1ReadData.c

pmwhite

shopt -s nullglob globstar

# settings
typeDelay=30
user=0

while [ -n "$1" ]; do
  case "$1" in
    --user) user=1; shift;;
    *) break;;

pmwhite

/home/philip λ>readlink -f $(which vim)
/nix/store/qi7n9xamd2gw2hzq5z3izj7mxskqylyy-vim-8.0.1150/bin/vim
/home/philip λ>readlink -f $(which test-vim)
/nix/store/sdzmghl3rjl51kc2vc2a7jw0n0kafqd0-test-vim/bin/test-vim
/home/philip λ>nix-env -e vim
/home/philip λ>readlink -f $(which vim)
/nix/store/qi7n9xamd2gw2hzq5z3izj7mxskqylyy-vim-8.0.1150/bin/vim
/home/philip λ>

pmwhite

{ config, pkgs, ... }:

{
  imports = [ ./hardware-configuration.nix ];

  boot.loader.systemd-boot.enable = true;
  boot.loader.efi.canTouchEfiVariables = true;

  networking.hostName = "mordor"; # Define your hostname.

pmwhite

function plus(x) {
  return function(y) {
    return x + y;
  };
}

addFive = plus(5);

addFive(4); // 9
addFive(3); // 8

pmwhite

How F# functions work.

Functions in functional programming take some time to get used to, but I want to try to simplify it a little.

Expressions

In functional programming, nearly everything is an expression. Although you must eventually do something, generally you should try to isolate those parts by themselves.

In a language like Java, if is a statement:

pmwhite

#include <iostream>
using namespace std;

class Pascal {
  public:
    int row;
    int column;
    int value;

    Pascal(int v, int r, int c) : value(v), row(r), column(c) { }

pmwhite

#include <vector>

struct SensorRange {
  int first;
  int last;
}

// Find the first and the last sensors that see something
SensorRange activeSensorRange(vector<bool> sensorData) {

pmwhite

using System;
using System.Diagnostics;
using System.Collections.Generic;
using System.Text.RegularExpressions;
using System.IO;
using System.Threading;

namespace Air1SongTracker
{
  struct Item

pmwhite

module Main
import Data.Vect

-- I'm modelling this after Edwin Brady's extensible records snippet - http://lpaste.net/104020


-- I tried to make a corresponding extensible union type.
-- It ended up morphing into a type that has a parameter that specifies how many
-- fields can be filled.  In my head, this type should consume (subsume?) both
-- types.