Kevin Kenny wrote:
>  I like the [string foreach] idea, particularly now that we have
>  extensible ensembles. (I'm not sure without source-diving whether
>  [string] is broken into an ensemble yet, but that's in the plan.)

All ensembles that produce bytecode are done, since I used the
opportunity of writing an ensemble compiler to simplify the code
generators in tclCompCmds.c. Well, I think splitting the big compiler
functions up into smaller ones that do one thing only is better. :-)

It's the other ensemble-like things that need doing. (It's not difficult
coding, but it takes time.)

>  An extensible [string] ensemble would mean that [string foreach]
>  could be piloted as an extension and then tracked into the Core.

Or, if the benefit isn't large enough, left as an extension.

FWIW, the main cost with a [string foreach] is actually the allocation
of a large number of character objects. We learned *that* when we
optimized [split] in 8.4. :-)

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