ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> ruby-talk
ruby-talk
Re: class destruction (evil genius metaprogramming)
by Gregory Brown other posts by this author
Jun 17 2007 7:09AM messages near this date
Re: class destruction (evil genius metaprogramming) | Re: class destruction (evil genius metaprogramming)
On 6/16/07, dblack@[...].net <dblack@[...].net>  wrote:
>  Hi --
> 
>  On Sun, 17 Jun 2007, Devin Mullins wrote:
> 
>  > 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.
>  >
>  > You mean, like Object#become? :)
> 
>  Not exactly.  As I understand it, #become involves references changing
>  from one object to another.  I'm thinking of something more like:
> 
>     module M
>     end
> 
>     a = Object.new
>     class << a
>       ancestors.unshift(M)  # essentially same as a.extend(M)
>     end

Would you want to be able to switch ordering too?  I wonder what kind
of interesting evil could come of that...
Thread:
Giles Bowkett
Rick DeNatale
dblack
Robert Dober
dblack
Robert Dober
Giles Bowkett
dblack
Stephen Smith
Nathan Taylor-Hoover
Giles Bowkett
dblack
Giles Bowkett
Rick DeNatale
dblack
Devin Mullins
dblack
Gregory Brown
Giles Bowkett

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved