Almost impossible to do static analysis.
If you want to figure out where a method call is going to go to
(without running it through ruby-debug), good luck, especially if
there's much use of alias_method_chain.
On Apr 25, 11:01 am, Andrew Grimm <andrew.j.gr...@gmail.com> wrote:
> I suspect the ability to call private methods is something that'd be
> very hard to change in ruby. I can't see how you could change that
> without forbidding open classes, which would mean an end to duck
> punching (though to be honest I don't punch ducks much myself)
>
> One minor glitch that annoys me is that you can't declare a method
> private in the method definition itself. You can't do something like
>
> private def change_balance(amount)
> ...
> end
>
> instead, you have to do
>
> def change_balance(amount)
> ...
> end
>
> private_method :change_balance
>
> which isn't very DRY to me.
>
> For what it's worth, some people regard private methods as a code
> smell - something that ought to be refactored out into another object.
>
> Andrew
>
>
>
>
>
> On Sun, Apr 25, 2010 at 10:30 AM, liam <liam.mclen...@gmail.com> wrote:
> > I don't know ruby very well so my likes / dislikes are evolving, but
> > the moment the things I don't like are:
>
> > Ruby has complicated and overloaded anonymous method syntax:
> > - do ... end, proc.new, lambda, & parameter syntax, blocks are method
> > parameters but not exactly
>
> > Compare this to the javascript equivalent: function() {}
>
> > Linking scripts is a pain with require, load, require_relative.
>
> > The ability to call private methods.
>
> > On Apr 24, 9:24 pm, Andrew Grimm <andrew.j.gr...@gmail.com> wrote:
> >> Opposite of the previous question. Unlike the previous, it should be
> >> able to fit in 140 characters or less.
>
> >> For me:
> >> * ruby (MRI and YARV) is an imperfect implementation of ruby (the
> >> language).
> >> * ruby's appeal isn't small, just selective, ala Spinal Tap.
>
> >> Andrew
>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Ruby or Rails Oceania" group.
> >> To post to this group, send email to rails-ocea...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> rails-oceania+unsubscr...@googlegroups.com.
> >> For more options, visit this group
> >> athttp://groups.google.com/group/rails-oceania?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Ruby or Rails Oceania" group.
> > To post to this group, send email to rails-ocea...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > rails-oceania+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/rails-oceania?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To post to this group, send email to rails-ocea...@googlegroups.com.
> To unsubscribe from this group, send email to
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group
> athttp://groups.google.com/group/rails-oceania?hl=en.
--
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To post to this group, send email to rails-ocea...@googlegroups.com.
To unsubscribe from this group, send email to
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en.
