From: Lionel Bouton <lionel-subscription@...>
Date: 2007-09-06T08:41:45+09:00
Subject: Re: before, after and around Ruby 1.9

Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Re: before, after and around Ruby 1.9"
>     on Thu, 6 Sep 2007 03:07:14 +0900, Trans <transfire@gmail.com> writes:
>
> |Any chance Ruby 1.9 will have before, after and around method
> |composition support?
>
> No.  Wait for 2.0 for built-in method combination.  The vague plan is
> making open-class to stack methods on the current ones, unless
> explicitly removed, i.e.
>
>   class Foo < Object
>     def foo
>       puts "Foo#foo (1)"
>     end
>   end
>   class Foo # re-open
>     def foo
>       super  # calls the first foo
>       puts "Foo#foo (2)"
>     end
>   end
>
> will print
>
>       Foo#foo (1)
>       Foo#foo (2)
>
> No alias required.
>   

Does it mean that we won't be able to call the ancestor's implementation
when monkey-patching a method?

I'm asking because I do this very (ugly?) thing for the Rails 1.1
PostgreSQL ActiveRecord driver: add_column is buggy with my PostgreSQL
version and it happens that the AbstractDriver implementation works out
of the box :-)

Lionel