Re:Ruby is not a callable orientated language
by blubb on Sunday February 21, 2010 @01:22PM
(#1140968)
>> lambda {} == proc {}
=> true
Can you shed some light on the difference? I always thought that lambda is simply a synonym for proc - has this changed in more recent versions?
Re:Ruby is not a callable orientated language
by carbon8 on Sunday February 21, 2010 @01:58PM
(#1141030)
See here: http://www.robertsosinski.com/2008/12/21/understanding-ruby-...
Proc objects created with lambda check arguments and have "diminutive return" so they behave as anonymous methods.
Also, Kernel#proc is an alias to Kernel#lambda, so the only way you get the bare Proc behavior is by calling Proc.new directly.
Re:Ruby is not a callable orientated language
by blubb on Sunday February 21, 2010 @02:20PM
(#1141071)
Ah, I didn't know that Proc.new != proc/lambda :)
They both return Proc objects though, so I wonder if it is possible to "convert" them.
Re:Ruby is not a callable orientated language
by carbon8 on Sunday February 21, 2010 @07:13PM
(#1141530)
One small note, as pointed out in http://innig.net/software/ruby/closures-in-ruby.rb posted by arohner above: although in 1.8 proc is an alias for lambda, in 1.9 it's now an alias for Proc.new.
Re:Ruby is not a callable orientated language
by FooBarWidget on Sunday February 21, 2010 @03:11PM
(#1141154)
The empty lambda or empty proc is a special object that always points to the same instance. Probably some kind of optimization.
Procs and Lambdas exist because they exhibit different scoping rules. If you want local scoping only, use a lamdba. If you want access to information outside the block, use a proc.
Of course, your rant sure sounds like you didn't actually read Katz's blog post, or you wouldn't be using terms like "callable types." The post explains exactly WHY Ruby doesn't have an equivalent __call__ structure...