On Mon, Feb 18, 2013 at 5:19 PM, connor culleton <[email protected]> wrote: > Hey Robert! > > Yes you are correct. That was confusing terminology on my part, I am > just using 'include' keyword. I'll edit the op now. > > "It will just insert the module in the inheritance chain (see > MyController.ancestors) for > method lookup." > > Ok that is helpful! > > To be more precise about what is happening in my case. Our framework is > using cucumber and the large module is being included like this > > World(Stuff) > > Then I am later including it in a controller class to get access to the > same methods. Including the whole thing again into another class feels > wrong some how...
Why? That's the whole point in placing code in a module vs. in a class. Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- [email protected] | https://groups.google.com/d/forum/ruby-talk-google?hl=en --- You received this message because you are subscribed to the Google Groups "ruby-talk-google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
