The end goal is to evolve these into Tcl 9.
The table below is for tracking the list of ideas. Portions of it, maybe even all, should also be added to our Project Ideas for Google Summer of Code.
For ease of exchange please follow the same format for ideas and idea pages as for the GSoC page.
|Sort out 64-bit Tcl API issues||Very disruptive; approach taken might be too extreme||DKF||novem-64bit-sizes||Not much happening right now|
AMG: When I see "novem-64bit-sizes" above, am I to take it that there is a plan (even a vague plan) to support strings/lists longer than 2,147,483,647 bytes/elements? I'm curious how much interest there is in this. Is it an unmotivated wishlist item, or has anyone actually found an application for it? The only thing I can think of is that a Tcl web server might someday want to send or receive a "file" larger than two gigabytes, even if the "file" was generated or processed in memory and not on disk. An example would be data going to and from an SQLite incrblob since the incrblob implementation is buggy w.r.t. channel events.