It's too bad that keyword arguments are semantically opposite between CRuby and RubyMotion in Ruby 2.0+. It'll cause a divergence and makes it a little more dif

It's too bad that keyword arguments are semantically opposite between CRuby and RubyMotion in Ruby 2.0+. It'll cause a divergence and makes it a little more difficult for Rails+RubyMotion engineers like me to switch. I understand the reasoning behind both decisions (RubyMotion is following Objective-C's semantics, CRuby is following Python et al). For those who aren't familiar with RubyMotion's syntax: def my_method(arg1, keyword: arg2) puts arg1 puts arg2 end my_method("test", keyword: "test2") # output test test2