Hi --

On Sun, 17 Jun 2007, Rick DeNatale wrote:

>  On 6/16/07, dblack@[...].net <dblack@[...].net> wrote:
> 
> > I do sometimes wonder what would happen if the ancestry array were
> > writeable.  It could be interesting.  I haven't thought through the
> > possible pitfalls.
> 
>  Actually the ancestry array only exists as the return value of the
>  ancestry method, internally it's a chain of class objects, and module
>  wrapper's.

By making it writeable I meant making it an interface to the chain
itself.  Obviously you can do:

   String.ancestors << "blah"

but that wasn't the point :-)


David

-- 
* Books:
   RAILS ROUTING (new! http://safari.awprofessional.com/9780321509246)
   RUBY FOR RAILS (http://www.manning.com/black)
* Ruby/Rails training
     & consulting:  Ruby Power and Light, LLC (http://www.rubypal.com)