From: John W Higgins Date: 2013-05-01T02:12:22+09:00 Subject: Re: How does Module#include differ from #prepend? --089e0163450aa1e25404db971ae1 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Apr 30, 2013 at 9:55 AM, Love U Ruby wrote: > module Foobar > > > Now my question is - Is there any difference between module#prepend and > module#prepend_features? Looking at the output,it seems module#prepend > is set as lower priority call - why so? > prepend_features allows you to override the prepend methodology if you wish (and no, I have no idea why anyone would want to - but it's possible that you could do something like never allow a particular method call to be prepended if needed (and that's just a guess)) prepended is a callback that tells you a prepend has occured - it is not "lower priority" - it simply occurs after the fact as opposed to before as prepend_features does --089e0163450aa1e25404db971ae1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Apr 30, 2013 at 9:55 AM, Love U Ruby <= lists@ruby-forum.= com> wrote:

module Foobar

Now my question is - Is there any difference between module#prepend and
module#prepend_features? Looking at the output,it seems module#prepend
is set as lower priority call - why so?

=A0=

prepend_features allows you to override the prepend methodology if = you wish (and no, I have no idea why anyone would want to - but it's po= ssible that you could do something like never allow a particular method cal= l to be prepended if needed (and that's just a guess))

prepended is a callback that tells you a prepend has occured - it is not=20 "lower priority" - it simply occurs after the fact as opposed to = before as=20 prepend_features does

--089e0163450aa1e25404db971ae1--