Hi Gustaf,

On 07/05/2008, at 20:06, Gustaf Neumann wrote:

>  Tip #279 goes even one step further and provides an multi-flavor
>  oo framework. I still believe that the framework aspect is important
>  since it allows continuous work in extensions for flavours,
>  while having a stable part in the core.

if it is actually intended to be possible to implement TclOO on top  
of the TIP279 engine, I don't understand why there should be any  
conflict between TIP 257 and TIP 279 at all (besides the obvious need  
for two different toplevel namespaces, say oo:: and xo::).

The vote on TIP 257 is about the TclOO API, not about the details of  
the implementation, so if TIP 257 is accepted now and integrated with  
Donal's current implementation and then in say 6 months you have the  
TIP279 xo:: framework ready with an alternative TclOO implementation  
on top that performs better, then the current 257 implementation  
could be swapped out with yours without affecting the API, no?

I don't see why the vote on something that is ready now should be  
delayed for a potential future enhancement that does not conflict  
with it? maybe I misunderstand the goals of TIP279 or the readiness  
for core integration of its implementation?

by readiness I mean (with my maintainer hat on) something that fits  
in with the rest of the tcl codebase in terms of formatting, style  
and readability so that it can be understood by a significant subset  
of the maintainers.
IMO the current TclOO implementation meets that criterion (and others  
appear to agree), does something similar exist for 279 at this point?

Cheers,

Daniel

-- 
** Daniel A. Steffen                   **
** <mailto:das@[...].net>   **



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