| class Numeric | |
| def prime? | |
| basics = (2..10).to_a | |
| return false if basics.detect { |n| self % n == 0 } | |
| factors == [1, self] | |
| end | |
| def factors | |
| @factors ||= (1..self).to_a.select { |n| self % n == 0 } | |
| end |
| #!/usr/bin/ruby | |
| require 'rubygems' | |
| require 'net/http' | |
| require 'yaml' | |
| require 'cgi' | |
| require 'bossman' | |
| include BOSSMan | |
| require 'igraph' |
cribbed from http://pastebin.com/xgzeAmBn
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
| full_data = { | |
| response: {body: StyledYAML.literal(DATA.read), status: 200}, | |
| person: StyledYAML.inline('name' => 'Steve', 'age' => 24), | |
| array: StyledYAML.inline(%w[ apples bananas oranges ]) | |
| } | |
| StyledYAML.dump full_data, $stdout | |
| __END__ | |
| { |
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
WARNING
This gist is outdated! For the most up-to-date information, please see http://emberjs.com/guides/routing/!
An Ember application starts with its main template. Put your header, footer, and any other decorative content in application.handlebars.
<header>
| # ROUTER | |
| GWS.Router.map (match) -> | |
| #match("/").to("home") # home.handlebars gets rendered automatically and mapped to / | |
| # according to guide the previous logic shouldn't be needed. but it won't work without it | |
| # you can either use model: () -> or | |
| # setupController: (controller, model) -> | |
| # controller.set 'content', model |
There are two JSON API styles:
The ID style is the easiest to get started with, but requires that your clients be able to guess the URLs for related documents. It also locks your API into a particular URL structure, which may become a problem as your API grows.
The URL style requires less guessing on the client side, and makes clients more resilient to API changes, but is trickier to use with relationships and compound documents.
| <?xml version="1.0" encoding="UTF-8" ?> | |
| <!DOCTYPE plist PUBLIC "-//Apple Computer/DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
| <plist version="1.0"> | |
| <dict> | |
| <key>Label</key> | |
| <string>org.scottlowe.pf.plist</string> | |
| <key>Program</key> | |
| <string>/sbin/pfctl</string> | |
| <key>ProgramArguments</key> | |
| <array> |
