jakarta-regexp-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 3877] - {n} and {n,m} not thread safe
Date Fri, 28 Sep 2001 23:05:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3877>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3877

{n} and {n,m} not thread safe





------- Additional Comments From dougpardee@yahoo.com  2001-09-28 16:05 -------
External synchronization works great in the usual case where an *instance* 
cannot safely be shared between threads. In this case, however, the *class* 
cannot safely be shared between threads. This presents an unexpected and much 
messier proposition. In general, we do expect to be able to create more than 
one instance of a class at a time.

Mime
View raw message