From: Donal K. F. <don...@ma...> - 2010-03-29 13:46:40
|
On 29/03/2010 14:16, Donal K. Fellows wrote: > This is a Call for Votes on the following two TIPs: And now for a few comments on the TIPs... > TIP #348: Substituted 'errorstack' / 'traceback > http://tip.tcl.tk/348.html > > This TIP proposes to add an errorstack options dict entry and > associated info subcommand, giving a "substituted" traceback > similar to Python's or gdb's ones. Alex has worked hard on this one and has a specification now that is both eminently implementable and likely to be useful to code that is processing stack traces. Good one! > TIP #364: Threading Support: Configuration and Package > http://tip.tcl.tk/364.html > > This TIP changes the the default configuration for building to > threaded on all platforms where this is not already the case > (primarily Unix other than MacOS X) and adds the Thread package to > the set of packages included by default. OK. For this one, it's important to note that in terms of Tcl's configuration it is just changing a default and adding a package. It does have some impacts on things that others are doing with Tcl (in particular with Expect and TclX which reach very deeply into the murkier parts of the UNIX interface) but we can still support those packages in their classic configurations if a non-threaded build is made (which *is* and remains supported). It's also looking like this will stimulate work to make critical parts of those extensions (or things that operate in a similar area) work with threads; a very good result too. There are some issues with getting the Thread merger done. I see no reason to expect them to block us however, as the Tcl Maintainers have full commit access to the relevant repository. (Co-hosting with Tcl has its advantages.) The other threading problem I'm aware of is the poor state of thread support in OpenBSD's getaddrinfo() implementation, but that is truly a case of someone else's bug that's been allowed to fester as thread safety has been a requirement for that API for many years now. As such, if it blows up we'll fairly blame the OpenBSD guys. :-D Looking at the overall roadmap, I'd guess that we're pretty close to being able to vote on TIP#162 too. That's the last API-level new feature that we really want to introduce into 8.6, so we're very close to being able to do another beta and switch to pushing for quality so as to get to a final release... Donal. |