I had this long e-mail drafted, and I deleted it.  It doesn't  
matter.  Tcl needs OO in the core, not an OO framework.  A framework  
gets us what?  The ability to make MORE OO extensions?  We already  
have a ton of those, and what good has it done us?

     XOTcl has been around for years.  Gustaf and the team have put in  
a lot of work, and I would say they have the most knowledge of OO in  
this community and especially with regards to Tcl.  So, how do we  
reward that knowledge and hard work?  Let's go off and make ANOTHER OO  
EXTENSION!  This REEKS of "not invented here."

     If you don't like XOTcl, clean it up.  It's the best we've got.   
TclOO sucks memory like a damn mind flayer (gratuitous D&D  
reference).  It uses more than Itcl, for God's sake.  Remove the cruft  
and crap and make XOTcl (a tried and tested OO extension) the core.   
Change instproc to method or whatever you've got to do.  WORK WITH  
THEIR TEAM.  They know what they're doing, and they actually WANT TO  
DO IT!

     God damn it, guys.  Grow up and work together.

D

This message has been brought to you by a member of this community who  
is sick of seeing his favorite language languish because the people in  
charge do nothing but bicker and vote.  Not that anything will save  
said member's favorite language at this point, but at least it can  
become more pleasant for himself and others.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Tcl-Core mailing list
Tcl-Core@[...].net
https://lists.sourceforge.net/lists/listinfo/tcl-core