Re:Evolution of a Ruby Programmer
by csmeder on Thursday February 11, 2010 @10:05PM
(#1119616)
Honest feed back? How about this version:
def fact(max=ARGV[0].to_i, i1=1, i2=1, i=1)
i < max ? fact(max, i2, i1+i2, i+1) : (puts i1)
end
fact()
This was the 2nd program I wrote in Ruby (I know it's recursive and therefore inefficient but my goal was to see how short I could make it not how efficient)
Re:Evolution of a Ruby Programmer
by jff on Friday February 12, 2010 @12:42AM
(#1119873)
In my opinion, the "Newbie programmer" and the "Discovered ternary operators" are the clearest and simplest and can be understood by anybody who knows a C-like; the first one especially is the clearest to anyone.
I'm not a Ruby programmer, though--are there increasing performance gains as the function evolves?
Re:Evolution of a Ruby Programmer
by bschaefer on Friday February 12, 2010 @12:35AM
(#1119864)
It seems to me that programmatic evolution is often like biological evolution -- namely, it moves from "simple but works," to "Wouldn't it be cool if..." :)
I'm not a Ruby programmer, though--are there increasing performance gains as the function evolves?