Eric Wong wrote:
> ko1 brought up a good point:  this may interact badly with
> 3rd-party libraries which use thread-local storage via
> pthread_getspecific/pthread_setspecific (or compiler
> extensions).

> So, we might need to disable this before 2.6 release :<

ko1 and I agreed this is a low-risk and will keep thread cache
enabled for 2.6.  pthread_{get,set}specific isn't very popular
in 3rd-party libraries, or they use it in ways which does
not conflict with thread-caching.

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>