It just looks nicer–it’s syntactic sugar; it ends up being the same thing. When mixing keys (ew, why would you do that?) I use the old hash-rocket syntax for the entire hash. With symbol values I also use the old hash-rocket syntax for the entire hash–this looks icky: { ohai: :kthxbye } I don’t like … Read more
Instead of adding # coding: UTF-8 try to add # encoding: UTF-8 on the first line of the file. It worked for me. I found the information here : http://groups.google.com/group/sinatrarb/browse_thread/thread/f92529bf0cf62015
You can either: set your RUBYOPT environment variable to “-E utf-8” or use https://github.com/m-ryan/magic_encoding
Yes, you’re calling to_s on an array of strings. In 1.8 that is equivalent to calling join, in 1.9 it is equivalent to calling inspect. To get the behavior you want in both 1.8 and 1.9, call join instead of to_s.
Here is the way I fix the “invalid date format in specification” error: 1.) Go to the specifications folder located at: /usr/local/lib/ruby/gems/1.8/specifications/ 2.) Find the spec that is causing the problem. 3.) Change s.date = %q{2011-05-21 00:00:00.000000000Z} to s.date = %q{2011-05-21} That’s a WIN for me! Good Luck
A workaround for this was just added to the ‘aws’ gem so thought I’d share as it was inspired by this post. https://github.com/appoxy/aws/blob/master/lib/awsbase/require_relative.rb unless Kernel.respond_to?(:require_relative) module Kernel def require_relative(path) require File.join(File.dirname(caller[0]), path.to_str) end end end This allows you to use require_relative as you would in ruby 1.9.2 in ruby 1.8 and 1.9.1.
Sam Ruby has a cool slideshow that outline the differences. In the interest of bringing this information inline for easier reference, and in case the link goes dead in the abstract future, here’s an overview of Sam’s slides. The slideshow is less overwhelming to review, but having it all laid out in a list like … Read more
Have you tried adding a magic comment in the script where you use non-ASCII chars? It should go on top of the script. #!/bin/env ruby # encoding: utf-8 It worked for me like a charm.
The author of that blog post is being overly dramatic and foolish, the => is still quite necessary. In particular: You must use the rocket for symbols that are not valid labels: :$set => x is valid but $set: x is not. In Ruby 2.2+ you can get around this problem with quotes: ‘$set’: x … Read more
Yes, there is a difference. These are legal: h = { :$in => array } h = { :’a.b’ => ‘c’ } h[:s] = 42 but these are not: h = { $in: array } h = { ‘a.b’: ‘c’ } # but this is okay in Ruby2.2+ h[s:] = 42 You can also use … Read more