DN613250766

Subject: OOP system for Tcl8.4 - DN [1]

Jeffrey Hobbs <jeffrey.hobbs@scriptics.com> - 19 Apr 2000 - comp.lang.tcl

 Just to make a few things clear where the lines seem to have blurred...

 The core team decided that it was time for an OOP system in the core
 distribution, and to put it in with Tcl8.4.  Whatever the choice is,
 it will be included in the distribution, but to get it you will have
 to do 'package require oosystem*', and it will have a separate dll.
 This is part of expanding Tcl's reach by modularization (without
 kernel bloat).  For example, the 'thread' extension will be part of
 the Tcl8.4 distribution as well.

 The reasons behind the need of an OOP system were for use in a
 megawidget system, and perhaps parts of tcllib.  That means if you
 were to use these, they would implicitly require the OOP extension.

 [incr Tcl] is recognized as the most popular, and likely most
 robust OOP system for Tcl currently.  However, some people are
 voicing their opinions against it as a choice (see the CLOS, or
 slots-based, vs C++/class-based discussions).  I invite everyone to
 take part in these discussions, as we are reading every line.  This
 is everyone's time to shape the future of Tcl.

 The core team realizes that any choice is going to make some people
 unhappy (OO argument have been around a long time, and will continue
 for longer, I'm sure).  However, we have a need for an OOP system,
 and we will be making a choice for 8.4.  This does not mean you can't
 continue to use your preferred system.  There may be some conflicts
 if you use new features (like megawidgets), but I think on the whole
 the community will greatly benefit from these changes.

 --
    Jeffrey Hobbs                          The Tcl Guy
    jeffrey.hobbs at scriptics.com         Scriptics Corp.

 * BTW, "oosystem" is just a name placeholder...