From: Russell Fulton Date: 2006-07-11T10:24:57+09:00 Subject: Re: problems with mixins Thanks again David! > > What it comes down to is that module inclusion is per class. A nested > class is still a completely different class from the class it's nested > in, so you need to include the module in the inner class separately. > I swear that I tried putting includes in the inner modules at one stage, sigh.. But I have been fiddling with various things and must have been holding my mouth the wrong way at the time :) After going back and adding 'include Parser' to all the inner modules I am now back in business. Originally Parser was a class and I was passing an instance of it to new for each inner class. I decided that doing it with a mixin was a better approach since I will never have more than one Parser at a time. Russell -- Posted via http://www.ruby-forum.com/.