http://www.globalnerdy.com/2009/03/12/default-and-named-parameters-in-c-40-sith-lord-in-training/ Tech Evangelist Joey deVilla on software development, tech news and other nerdy stuff Thu, 19 Nov 2009 18:44:37 -0400 http://wordpress.org/?v=2.8.6 hourly 1 http://www.globalnerdy.com/2009/03/12/default-and-named-parameters-in-c-40-sith-lord-in-training/comment-page-1/#comment-3990 Named Parameters in Method Calls: Python Si, Ruby No — Global Nerdy Mon, 16 Mar 2009 04:00:11 +0000 http://www.globalnerdy.com/2009/03/12/default-and-named-parameters-in-c-40-sith-lord-in-training/#comment-3990 [...] an earlier article, Default and Named Parameters in C# 4.0 / Sith Lord in Training, I wrote about how C# 4.0 – that’s the version coming out with the next release of Visual [...] [...] an earlier article, Default and Named Parameters in C# 4.0 / Sith Lord in Training, I wrote about how C# 4.0 – that’s the version coming out with the next release of Visual [...]

]]> http://www.globalnerdy.com/2009/03/12/default-and-named-parameters-in-c-40-sith-lord-in-training/comment-page-1/#comment-3989 Joey deVilla Sun, 15 Mar 2009 10:49:02 +0000 http://www.globalnerdy.com/2009/03/12/default-and-named-parameters-in-c-40-sith-lord-in-training/#comment-3989 <strong>Jörg W Mittag:</strong> You're right. I got my Python mixed up with my Ruby! Jörg W Mittag: You’re right. I got my Python mixed up with my Ruby!

]]> http://www.globalnerdy.com/2009/03/12/default-and-named-parameters-in-c-40-sith-lord-in-training/comment-page-1/#comment-3982 Jörg W Mittag Fri, 13 Mar 2009 17:56:56 +0000 http://www.globalnerdy.com/2009/03/12/default-and-named-parameters-in-c-40-sith-lord-in-training/#comment-3982 Ruby <em>does not</em> support named parameters. What you are simply doing is passing the expression <code>radius = 100</code> as the first <em>positional</em> argument, and since in Ruby assignment expressions always evaluate to the assigned value, this is exactly the same as passing <code>glorp = 100</code> or even <code>foo.bar = 100</code> or just <code>100</code>. In fact, it is even the same as passing <code>x = 100</code>, which is definitely <em>not</em> what you want from your named parameters! Ruby does not support named parameters. What you are simply doing is passing the expression radius = 100 as the first positional argument, and since in Ruby assignment expressions always evaluate to the assigned value, this is exactly the same as passing glorp = 100 or even foo.bar = 100 or just 100. In fact, it is even the same as passing x = 100, which is definitely not what you want from your named parameters!

]]>