The Tcl Core Team is pleased to announce the 8.5.2 releases of the Tcl
dynamic language and the Tk toolkit. This is the second patch release
of Tcl/Tk 8.5. More details can be found below. We would like to
express our gratitude to all those who submit bug reports and patches.
This information is invaluable in enabling us to identify and eliminate
problems in the core.
Where to get the new releases:
------------------------------
Tcl/Tk 8.5.2 sources are freely available as open source from the
Tcl Developer Xchange web site at:
http://www.tcl.tk/software/tcltk/8.5.html
This web page also contains additional information about the releases,
including new features and notes about installing and compiling the
releases. Sources are always available from the Tcl SourceForge
project's file distribution area:
http://sourceforge.net/project/showfiles.php?group_id=10894
Binaries for most major platforms are available from:
http://www.activestate.com/Tcl
For additional information:
---------------------------
Please visit the Tcl Developer Xchange web site:
This site contains a variety of information about Tcl/Tk in general, the
core Tcl and Tk distributions, Tcl development tools, and much more.
Summary of Changes since Tcl/Tk 8.5.1:
--------------------------------------
The following were the main changes in Tcl/Tk 8.5.2. A complete list
can be found in the changes file at the root of the source tree. The
more complete ChangeLog is also included with each source release. This
is a patch release, so it primarily included bug fixes and corrections
to erratic behavior. Below are only the most notable changes.
* New version 2.7 of http package:
- [http::meta] command
- [http::geturl] options: -myaddr -keepalive -protocol -strict -method
- chunked transfer encoding support
* Tcl Modules defined to use the utf-8 encoding *only*.
*** POTENTIAL INCOMPATIBILITY for any existing Tcl Modules written
in encodings not compatible with utf-8 ***
* Improved refcount usability for Tcl_SetReturnOptions() and
Tcl_AddObjToErrorInfo().
*** POTENTIAL INCOMPATIBILITY for existing callers ***
* Corrections to the Ttk_* interfaces to support stub-enabled callers.
* Exposed Tcl_GetMemoryInfo() for AOLserver.
* Fixed regexps ending in \*.
* Made [::safe::loadTk] work again.
* Fixed confusion in caching bytecode for scripts vs. expressions.
* Fixed hang in [namespace delete] with variable unset traces.
* Fixed crash following font failures (X11 --enable-xft).
* Fixed crash in [. configure -cursor] (X11).
* Fixed crash in [binary format x0s].
* Fixed crash in Tcl_GetReturnOptions() during finalization.
* Fixed memory leak in QD drawing (Aqua).
* Fixed memory leaks in [return -level 0] and [format %llx $big].
* Fixed memory leak in expr parser error message generation.
* Fixed memory leak in enter execution trace.
* Improved [clock format] performance.
* Better support for 64bit Solaris builds.
* New Tk demo: Knight's tour
--
Tcl Core Team and Maintainers
Don Porter, Tcl Core Release Manager
--
| Don Porter Mathematical and Computational Sciences Division |
| donald...@nist.gov Information Technology Laboratory |
| http://math.nist.gov/~DPorter/ NIST |
|______________________________________________________________________|
Question for everyone involved or whoever cares to answer:
Is it possible/desirable to extend TCL core to add more functionality
to make the environment more transparent?
Example:
----------------------------------------------------
I have these namespaces: x::y1::z,x::y2::z, x::y3::x
If I want to see all commands in namespaces x::y1::z, x::y2::z,
x::y3::z
info commands x::*::z
In namespace x::y1::z
info commands x::*1::z
Find all namespaces below x::
namespace children x::*
Find all namespaces below x::y1 and x::y2
namespace children x::y*
----------------------------------------------------
Basically, add glob expansion to namespace and it's associated
commands (where it makes sense). IMHO, that would make programming
with TCL much easier for a lot of people (including the humble
me) :) .
Since there is not much activity here, I reposted my question here:
http://groups.google.com/group/comp.lang.tcl/browse_thread/thread/a37c95242b20549f/9e86b7dc99ca7d4d#9e86b7dc99ca7d4d
Please go there to post your reply.
It is certainly possible to implement these things right now in pure Tcl
script. No need to extend the core.
>
> Example:
> ----------------------------------------------------
> I have these namespaces: x::y1::z,x::y2::z, x::y3::x
>
> If I want to see all commands in namespaces x::y1::z, x::y2::z,
> x::y3::z
> info commands x::*::z
set cmds [list]
foreach sub [namespace children x] {
lappend cmds {*}[info commands $sub\::z::*]
}
>
> In namespace x::y1::z
> info commands x::*1::z
Similar to the above.
>
> Find all namespaces below x::
> namespace children x::*
This is just [namespace children x].
>
> Find all namespaces below x::y1 and x::y2
> namespace children x::y*
...and x::y3.
>
> ----------------------------------------------------
>
> Basically, add glob expansion to namespace and it's associated
> commands (where it makes sense). IMHO, that would make programming
> with TCL much easier for a lot of people (including the humble
> me) :) .
I don't understand in what way this would make programming in Tcl
easier. It seems slightly odd to be wanting to glob match against
namespaces and commands in this way. What is it that you are trying to
accomplish? Is this for debugging or for building some sort of IDE? If
that is the case, then it seems that the solution is fairly simple already.
-- Neil
Is it me, or are these releases coming unusually closely spaced?
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Yes, for 8.6. For the best chance to achieve this, supply a patch. :-)
> Basically, add glob expansion to namespace and it's associated
> commands (where it makes sense). IMHO, that would make programming
> with TCL much easier for a lot of people (including the humble
> me) :) .
Adding glob-in-namespace-path support to various commands is possible,
but not quite as simple as you seem to think (as it internally needs
changes so that the "parse apart a qualified name" function can return
multiple namespaces). I suggest you try to make it work and report on
your experiences.
Don't forget to log a Feature Request at http://tcl.sourceforge.net/
Donal.
We're trying to stop them being so disgustingly far apart... :-)
Donal.
That reference is no use whatsoever to the many of us who do not use
Google Groups as an interface to the Usenet newsgroup!
E
Unfortunately, I don't speak C. :)
> Don't forget to log a Feature Request at http://tcl.sourceforge.net/
Done
Thanks for pointing it out.
---Victor
Looks like the tk_getOpenFile -multiple bug is still present. (On Linux,
64 bit, built from sources - don't know about Windows, AS binary
doesn't seem to be available yet...)
Ian
*********** To reply by e-mail, make w single in address **************
> project's file distribution area:
>
> http://sourceforge.net/project/showfiles.php?group_id=10894
Why not on ftp.tcl.tk ? I thought, it's s.c. "primary FTP" for TCL/Tk...
--
ZB
I would have expected it with a shiny new 8.5 series release. Bugs,
tweaks, etc.
Robert
That reference is a URL. Unless one has no web browsing ability, one
should be able to visit that web address to see the context of the
message.
It is up to the reader whether s/he wishes to locate that message in
one's own method of reading comp.lang.tcl. I mean, if someone only
reads clt in hardcopy, should everyone be expected to provide page
numbers?