Hi everyone

This is a warning that I think we're close to the point when I'll call a
vote on TIP#257, i.e. the merger of TclOO into Tcl. While it still has
its warts, they're largely implementation issues and we can sort them
out later (indeed, some may need full core integration to get completely
knocked on the head; it's difficult to really make methods efficient)
and the rest can get their own TIPs. But are there any really critical
problems left that can't be dealt with later? Hence this message.

I'd like to remind people that TclOO strives for minimality in many
respects (I didn't want to get sucked into writing a class library!) and
it tries to leave state (i.e. variables) to conventional Tcl namespace
variables (slotted access could be built on top of this foundation, but
I'm not doing it at this stage). What it does do is provide a proper
inheritance model, mixins, filters, and mechanisms to allow things (new
method types, new data structures) to be plugged in from the C level. I
believe I've demonstrated that Self-like objects can be built on top,
and I think that something like both iTcl and XOTcl can work too (the
former wouldn't have actually worked with the proposal from 18 months
ago; the extra time allowed a number of key refinements of some internal
APIs). It's also being used already for building some of the reference
implementation of TDBC.

In short, if there's a problem with TclOO, do speak up now!

Donal.

-------------------------------------------------------------------------
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