| // IRR swift version | |
| // [email protected] | |
| // reference http://www.codeproject.com/Tips/461049/Internal-Rate-of-Return-IRR-Calculation | |
| // 2016/06/23 | |
| import UIKit | |
| func computeIRR(cashFlows:[Int],numOfFlows:Int) -> Double{ | |
| //const |
| import Darwin | |
| let handle = dlopen("/usr/lib/libc.dylib", RTLD_NOW) | |
| let sym = dlsym(handle, "random") | |
| let functionPointer = UnsafeMutablePointer<() -> CLong>(sym) | |
| let result = functionPointer.memory() | |
| println(result) |
The operators c, d, and y expect a motion, like w, e, etc. The second character in the following pairs is not a motion so it is a NOP and nothing is overridden if we use them in mappings.
cd cm co cp cq cr cs cu cx cy cz
dc dm dq dr ds du dx dy dz
This post also appears on lisper.in.
Reader macros are perhaps not as famous as ordinary macros. While macros are a great way to create your own DSL, reader macros provide even greater flexibility by allowing you to create entirely new syntax on top of Lisp.
Paul Graham explains them very well in [On Lisp][] (Chapter 17, Read-Macros):
The three big moments in a Lisp expression's life are read-time, compile-time, and runtime. Functions are in control at runtime. Macros give us a chance to perform transformations on programs at compile-time. ...read-macros... do their work at read-time.