On Mon, Feb 18, 2013 at 5:39 PM, Robert Klemme
<[email protected]> wrote:
> On Mon, Feb 18, 2013 at 5:19 PM, connor culleton <[email protected]> wrote:
>> 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.
Just an example for how much reuse there is:
$ ruby -e 'ObjectSpace.each_object(Class) {|cl| puts cl if
cl.ancestors.include? Enumerable}'
Enumerator::Generator
Enumerator
Struct::Tms
Dir
File
ARGF.class
IO
Range
Struct
Hash
Array
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.
