Stop suffering and buy levitra without prescription, attached is a link….

As you play with a tool you progressively discover various small tidbits about it. I have a few in mind and I thought it would helpful to share them in case you encounter them and get this weird expression on your face of “huh?”.
1. The multiple ass…

Stephen Chu talked about how to beautify statements like customers.collect { |customer| customer.name…

Pretty clever stuff, nonetheless.

I tried once, it didn’t work, so I moved on Guess I should try again; its annoying that it doesn’t work the same way.

could you explain that behaviour of ‘map_by_method’ with activerecord?

Product.find(:all).collect_save — works fine

Brand.find(:first).products.collect_save — got NoMethodError

but Brand.find(:first).products.collect &:save — is ok

module MapByMethod
  def self.included(base)
    super

    base.module_eval < <-EOS
      def method_missing(method, *args, &block)
...

if I remove the included/mod_eval:

module MapByMethod
  def method_missing(method, *args, &block)
...

the tests stop working. I think its because ActiveRecord::Base defines #method_missing, so the module's version is not first in the chain.

Perhaps aliasing might be an alternative?

You embed you method_missing definition inside a module_eval. It seems to me to be sufficient to avoid the included hook and the module_eval altogether and just define method_missing directly in the module. Not only is it simpler, it plays better with the including class if it also defines a method_missing. Is there a reason for included/module_eval that I’m not seeing?

Thanks … keep those magic moments coming.