R
Robert Klemme
2007/11/24 said:Thank you for the heads up, definitely something for me to come back to![]()
Although I am a bit late into the discussion here are some points
where more discussion of topics like this can be found. This is really
about design patterns (as has been mentioned already).
First of all there is - of course - the famous book:
http://www.aw-bc.com/catalog/academic/product/0,1144,0201633612,00.html
Then there is the "Portland Pattern Repository"
http://c2.com/cgi/wiki?PatternIndex
Wikipedia also has some useful bits
http://en.wikipedia.org/wiki/Design_pattern_(computer_science)
A personal remark: sometimes I see it as a danger that delegation is
so easy in Ruby. The downside is that if you delegate *all* the
methods of a contained object you will completely clutter the outer
class's interface and you overly increase the dependency between the
two. Sometimes this is just what you want (because for example you
hide the contained object completely from the outside) but at other
times you just create unnecessary complexity.
Kind regards
robert