I guess it can get quite noisy, so joining that can be a pain. I'll give it a bit[over-night] to see if any of the Collections developers involved respond and then forward the message over to the Dev list.
Hen On Thu, 16 Jan 2003, Durham David Cntr 805CSS/SCBE wrote: > why not ask this on the developer list? > > > -----Original Message----- > > From: Tony Chao [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 16, 2003 2:20 PM > > To: Jakarta Commons Users List > > Subject: RE: Collections: Double-Checked Locking > > > > > > I already understand the problem with DCL > > > > I'm not asking what DCL is. > > I'm asking why collections uses DCL even though DCL is broken. > > Is it the case that the DCL situation doesnt ever actually occur on > > most real-world archectures (e.g. most real-world arch's follow > > a certain ordering such that the bug never appears) ? > > > > If not, then how does collections justify using DCL? > > > > -Tony > > > > > > > > -----Original Message----- > > From: Robert Egan [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 16, 2003 3:14 PM > > To: 'Jakarta Commons Users List' > > Subject: RE: Collections: Double-Checked Locking > > > > > > Try these java world articles for more info > > > > http://www.javaworld.com/javaworld/jw-02-2001/jw-0209-double.html > > http://www.javaworld.com/javaworld/jw-05-2001/jw-0525-double.html > > > > > > -----Original Message----- > > From: Tony Chao [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 16, 2003 2:59 PM > > To: [EMAIL PROTECTED] > > Subject: Collections: Double-Checked Locking > > > > > > Hi, > > > > I just started using commons-collections package. > > I noticed in the API there's a lot of warnings about > > doubled-checked locking > > idiom > > being broken. > > > > If it's broken? Why does commons-collections still use it? > > > > Is is theoretically broken, but works in most architectures > > in practice? > > > > What are some architectures that it actually breaks on? > > > > Thanks! > > > > -Tony > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > ************************************************************** > > *********** > > PRIVILEGED AND CONFIDENTIAL: This communication, including > > attachments, is > > for the exclusive use of addressee and may contain > > proprietary, confidential > > and/or privileged information. If you are not the intended > > recipient, any > > use, copying, disclosure, dissemination or distribution is strictly > > prohibited. If you are not the intended recipient, please > > notify the sender > > immediately by return e-mail, delete this communication and > > destroy all > > copies. > > ************************************************************** > > *********** > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
