Stefan Sobernig wrote:
>  Well, there is TIP#279. Shouldn't there be an attempt of achieving an 
>  amalgam of these two TIPs, following a qualified evaluation of the 
>  underyling proposals?

Are you volunteering?

>  I am wondering why TIP#279 seems to be neglected entirely!

It's not my TIP, so moving it forward to being implementation-ready
would seem to me to be someone else's job[*]. There's a lot of working
code that implements #257, and it's (probably) fast and robust. OK, I
admit it's a few months since I last ran performance tests, but TclOO
0.1 beat XOTcl 1.5.5 handily by about 2x on some simple tests (see
http://wiki.tcl.tk/18152 for the evidence, extracted from my paper last
Tcl conference). If someone were to redo and rerun[**], that would be a
good deed in itself.

By comparison, I've heard and seen nothing about TIP#279 implementations
since the last time I tried to push #257 to a vote. From my perspective,
it looks like you're just trying to block me, to "teach the controversy"
and other stuff like that. That annoys me. Don't do that.

>  A reconciliation appears necessary considering that there are 
>  more than convincing implementation references in TIP#279, not to 
>  mention the expertise of TIP#279 lead authors.

I fail to see why special reconciliation is needed. I fail to see why
the onus would be upon me to do so. I note that TIP#257 is the offer
that looks possible for 8.6 in engineering terms, given that we want to
stick to a strict timetable as a matter of general policy (which I
believe has been discussed in this list a number of times and which I
will not alter).

Looked at from my perspective, if you want to be in the game, you've got
to take part. Your move.

Donal.
[* I don't have time to write everything I'm very keen on, so why should
    I write other people's code too? Be realistic! ]
[** They were conducted on a single old, slow, but quiescent machine
     that definitely did not page memory while the test was running. I
     tried very hard to make the tests measure "the same thing". Except
     that each was run in a separate script, not as one. The tests were
     run in a cycle multiple times too and the fastest reported. ]

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