| #!/usr/bin/env ruby | |
| Dir.glob('poly/*.poly').each_slice(50) do |group| | |
| bp_wx = '' | |
| group.each do |poly_file| | |
| file = File.basename(poly_file, '.poly') | |
| city, region = file.split('_') | |
| bp_wx << "--buffer bufferCapacity=50000"\ | |
| " --bp file='poly/#{city}_#{region}.poly'"\ |
Note that for blocks, {} and do ... end are interchangeable. For brevity, only the former will be listed here.
Pre-1.9, lambda and proc are synonyms. Essentially the difference is between proc and block.
def method(&block) p block.class; p block.inspect; end
l = lambda { 5 }
parentheses: ( )
braces: { }
brackets: < >
square-brackets: [ ]
| # Related blog post: https://iprog.com/posting/2017/10/benchmarking-geoip-gems | |
| require 'benchmark' | |
| PASS = 1 # 1 or 2 | |
| ### libraries for C extensions | |
| # brew install geoip | |
| # brew install libmaxminddb |
Teh Social Netswork!
CREATE TABLE users (
id SERIAL PRIMARY KEY,
name VARCHAR(10) NOT NULL
);
INSERT into users VALUES
| # Usage: | |
| # | |
| # class Mail | |
| # include SimpleStateMachine | |
| # | |
| # self.initial_state = 'unread' | |
| # self.transitions_map = { | |
| # read: {from: 'unread', to: 'read'}, | |
| # unread: {from: 'any', to: 'unread'}, | |
| # delete: {from: 'any', to: 'deleted'}, |
| module SimpleRailway | |
| class Result | |
| attr_accessor :success, :data | |
| def initialize(success, data) | |
| @success = success | |
| @data = data | |
| end | |
| def success?; !!success; end | |
| def failure?; !success?; end |
| Go to Bitbucket and create a new repository (its better to have an empty repo) | |
| git clone git@bitbucket.org:abc/myforkedrepo.git | |
| cd myforkedrepo | |
| Now add Github repo as a new remote in Bitbucket called "sync" | |
| git remote add sync git@github.com:def/originalrepo.git | |
| Verify what are the remotes currently being setup for "myforkedrepo". This following command should show "fetch" and "push" for two remotes i.e. "origin" and "sync" | |
| git remote -v |
| /** | |
| * GlobalsDebugger | |
| * | |
| * Inspect the stack when a global variable is being set on the window object. | |
| * Given a global variable name, it proxies the variable name in the window | |
| * object adding some custom code that will be invoked whenever the variable | |
| * is set. The custom code will log the current stack trace and halt the code | |
| * execution to allow inspecting the stack and context in your browser DevTools. | |
| * You can use the "globalsToInspect" query-parameter to set a comma-separated | |
| * list of names of the variables you want to inspect. |