On Sat, 24 Nov 2007 09:57:42 +0900, Raul Parolari wrote:

> However, beware that this kind of information is useful and 'dangerous'
> at the same time if taken literally; eg, the example it gives of a
> Module hardcoding the class name (that is using it) is a bit.. eery
> (although I understand that he is just trying to show the mechanics of
> interaction module-class).
> 
> In Ruby, a Module of course has no preconceived notion of the classes
> using it; but, at the same time, if it needs to 'talk' to the class
> using it, it can (see the humble Enumerable module; you write a class
> including it, you define 'each', and suddenly.. you get a bounty of
> methods free; the module is in fact calling your 'each').


Thank you for the heads up, definitely something for me to come back to :)


-Thufir