Am Dienstag, 6. Mai 2008 17:38:27 schrieb Vasiljevic Zoran:
>  On 06.05.2008, at 16:53, Gerald W. Lester wrote:
>  > I agree that TIP 257 should go up for a vote and not (again) be
>  > stalled by 279, particularly since we've not seen any work on 279
>  > come out and since several people have been beating on 257 and found
>  > it very useful.
> 
>  I do not think that TIP 257, as-is now, should be voted for inclusion in
>  mainstream Tcl codebase, as neither the code nor the interface stability
>  is sufficient enough for professional-grade applications.
> 
>  It could exist as an extension to Tcl for people that find it useful.
>  Technically, a separate branch outside the main Tcl distribution tree
>  should be sufficient for that purpose, IMO.
> 
>  One should use the knowledge gathered by its develoment (AND by the 10+
>  years of XOTcl development) to create (better) hooks in core Tcl for
>  other (OO) extensions to have better interfacing capabilities,
>  as in the spirit of the Tcl language.

As somebody who has looked deeper (for several weeks) in both code bases 
(TclOO and XOTcl) in finding a suitable base for itcl-ng, I can only 
recommend TclOO code for inclusion into Tcl core. 

It is much better structured and as it was developped as an extension first it 
has well defined interfaces to the Tcl core, which helps modifying Tcl core 
later on without having always to look for TclOO. 

XOTcl C-code on the other side was very hard to read for me and as there is a 
very deep nesting level of functions for example in the dispatcher with the 
interfaces not very obvious. It uses very low level interfaces and structures 
and modifies them, which makes it very hard for Tcl core developpers to make 
changes. 

Also the TclOO coding style in my opinion fits much better to the rest of the 
core. I am assuming here that the XOTcl code would be used as a base for 
implementing TIP#279, as there is already a reference implementation for that 
with XOTcl.

My experience using TclOO for a new implementation of Itcl was very good and 
the TclOO side did a lot of interfaces needed for Itcl implementation. I had 
no success building an Itcl implementation on top of a prototype 
implementation (done by myself) of TIP#279 based on modified code of the 
reference implementation using XOTcl see: http://wiki.tcl.tk/18440 and 
http://wiki.tcl.tk/19873.

So if I had a vote I would vote with YES for TIP#257 (TclOO) and I suggest it 
to the voters.

Just my 2 cents (as a person which is a none voter for the tips)
Arnulf 
> 
>  Zoran Vasiljevic
>  Archiware GmbH, Munich
>  www.archiware.com
> 
> 
> 
> 
>  -------------------------------------------------------------------------
>  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/java
> one _______________________________________________
>  Tcl-Core mailing list
>  Tcl-Core@[...].net
>  https://lists.sourceforge.net/lists/listinfo/tcl-core



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