| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

History Books; Iraq + The (UK) Governing Elite; Answering Some Hard Questions; Pinochet: The Dictator's Shadow; An Outsider's Guide To Julia Packages; Nobody gives a shit; Lepton Decay Irregularity; An Easier Way; Julia's BinDeps (aka How To Install Cairo); Good Example Of Good Police Work (And Anonymity Being Hard); Best Santiago Burgers; Also; Michael Emmerich (Vibrator Translator) Interview (Japanese Books); Clarice Lispector (Brazillian Writer); Books On Evolution; Looks like Ara (Modular Phone) is dead; Index - Translations From Chile; More Emotion in Chilean Wines; Week 7; Aeon Magazine (Science-ish); QM, Deutsch, Constructor Theory; Interesting Talk Transcripts; Interesting Suggestion Of Election Fraud; "Hard" Books; Articles or Papers on depolarizing the US; Textbook for "QM as complex probabilities"; SFO Get Libor Trader (14 years); Why Are There Still So Many Jobs?; Navier Stokes Incomplete; More on Benford; FBI Claimed Vandalism; Architectural Tessellation; Also: Go, Blake's 7; Delusions of Gender (book); Crypto AG DID work with NSA / GCHQ; UNUMS (Universal Number Format); MOOCs (Massive Open Online Courses); Interesting Looking Game; Euler's Theorem for Polynomials; Weeks 3-6; Reddit Comment; Differential Cryptanalysis For Dummies; Japanese Graphic Design; Books To Be Re-Read; And Today I Learned Bugs Need Clear Examples; Factoring a 67 bit prime in your head; Islamic Geometric Art; Useful Julia Backtraces from Tasks; Nothing, however, is lost with less discomfort than that which, when lost, cannot be missed; Article on Didion; Cost of Living by City; British Slavery; Derrida on Metaphor; African SciFi; Traits in Julia; Alternative Japanese Lit; Pulic Key as Address (Snow); Why Information Grows; The Blindness Of The Chilean Elite; Some Victoriagate Links; This Is Why I Left StackOverflow; New TLS Implementation; Maths for Physicists; How I Am 8; 1000 Word Philosophy; Cyberpunk Reading List; Detailed Discussion of Message Dispatch in ParserCombinator Library for Julia; FizzBuzz in Julia w Dependent Types; kokko - Design Shop in Osaka; Summary of Greece, Currently; LLVM and GPUs; See Also; Schoolgirl Groyps (Maths); Japanese Lit; Another Example - Modular Arithmetic; Music from United; Python 2 and 3 compatible alternative.; Read Agatha Christie for the Plot; A Constructive Look at TempleOS; Music Thread w Many Recommendations; Fixed Version; A Useful Julia Macro To Define Equality And Hash; k3b cdrom access, OpenSuse 13.1; Week 2; From outside, the UK looks less than stellar; Huge Fonts in VirtualBox; Keen - Complex Emergencies; The Fallen of World War II; Some Spanish Fiction; Calling C From Fortran 95; Bjork DJ Set; Z3 Example With Python; Week 1; Useful Guide To Starting With IJulia; UK Election + Media; Review: Reinventing Organizations; Inline Assembly With Julia / LLVM; Against the definition of types; Dumb Crypto Paper; The Search For Quasi-Periodicity...; Is There An Alternative To Processing?

© 2006-2015 Andrew Cooke (site) / post authors (content).

Initial Scheme code for Napito

From: "andrew cooke" <andrew@...>

Date: Mon, 13 Aug 2007 21:04:14 -0400 (CLT)

Wrote this over the weekend, with help from people on various mailing
lists and #scheme.  Finally got it running just now.  It shows the basic
structure, but the code is still a mess - I need to write functions
(possibly macros) to help simplify things.

There seems to be more emphasis on higher order functions than I believe
normal in Scheme, but really I don't have much of a clue (someone on
#scheme didn't seem to follow it, but I probably didn't explain it well,
and they may have been a student).

":";exec snow -- "$0" "$@"

(package* napito/v1.0.0

  (provide:
   (define (nap-line x1 y1 x2 y2))
   (define (nap-generate engine drawing)))

  (author: "Andrew Cooke <andrew at acooke.org>")
  (homepage: "http://www.acooke.org")
  (description: "Napito drawing description language")
  (keywords: graphics)
  (license: gpl/v3.0)

  (require: napito-base/v1)
  (require: napito-test/v1))

; napito is separated into a user api (this file), some common support
; code (napito-base), and various engines.  the engines all implement
; (extend) the same "engine api".

; the user api is used to describe a drawing.  the api looks like a
; program but, when evaluated, constructs a function that takes and
; returns an engine.

; in other words, a drawing has the type engine -> engine.

; this interface is ubiquitous, since drawings can be nested (for
; example, a single line is a drawing).

; when an engine is passed to a drawing the internal api is invoked to
; generate the image on the engine's output device (eg. by creating a
; postscript file).

; for simple actions the engine api is similar to the user api.  for
; example, the user api to draw a line is the function (nap-line x1 y1
; x2 y2).  the engine api is (engine 'line (list x1 y1 x2 y2)).

; the job of the user api is to hide the engine api (which is generic
; with late binding) behind something that looks nice and simple.

; there are two advantages to this approach:

; first, late binding allows different engines to be used with the
; same drawing.

; second, the handling of the context (for example, the current
; coordinate transformation) is made implicit to the user, without
; losing referential transparency in the implementation.

(define (nap-line x1 y1 x2 y2)
  (lambda (engine)
    (engine 'line (list x1 y1 x2 y2))))

(define (nap-generate engine drawing)
  (drawing engine))

(test*
 (expect* (equal? (let ((engine (nap-engine (nap-default-transform))))
                    ((nap-generate engine (nap-line 0 0 1 1)) 'results '()))
                  '((line 0 0 1 1)))))

(write
 (let ((engine (nap-engine (nap-default-transform))))
   ((nap-generate engine (nap-line 0 0 1 1)) 'results '())))


":";exec snow -- "$0" "$@"

(package* napito-test/v1.0.0

  (provide:
      (define (nap-engine initial-transform)))

  (author: "Andrew Cooke <andrew at acooke.org>")
  (homepage: "http://www.acooke.org")
  (description: "Napito drawing description language - test engine")
  (keywords: graphics)
  (license: gpl/v3.0)

  (require: napito-base/v1))

(define (nap-engine initial-transform)
  (let ((state (make-state '() initial-transform)))
    (new-engine state)))

(define (new-engine state)
  (lambda (action args)
    (case action
      ((line) (new-engine (line state args)))
      ((scale) (new-engine (scale state args)))
      ((results) (get-results state)) ; specific to this engine
      (else (error "unsupported action" action)))))

(define (get-results state)
  (car state))

(define (get-transform state)
  (cadr state))

(define (make-state results transform)
  (list results transform))

(define (line state args)
  (let ((results (get-results state))
        (transform (get-transform state)))
    (make-state (cons `(line ,@args) results) transform)))

  (define (scale state args)
    (display "scale"))


Andrew

Comment on this post