Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: "Mike Schilling" Newsgroups: comp.lang.java.programmer Subject: Re: Threads and statics Date: Sun, 10 Apr 2011 23:10:34 -0700 Organization: A noiseless patient Spider Lines: 5 Message-ID: References: <905p9gFpuoU1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit Injection-Date: Mon, 11 Apr 2011 06:10:41 +0000 (UTC) Injection-Info: mx03.eternal-september.org; posting-host="66VJPJAWCJKXWbwaJaRQ4g"; logging-data="15383"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18qH5pcKhRLxi+/qnaaDPo9KMYdvgOt1NU=" X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 In-Reply-To: X-Newsreader: Microsoft Windows Live Mail 14.0.8117.416 Importance: Normal Cancel-Lock: sha1:0awYYg5vJePPGC/NBi4fcXXMmMA= X-Priority: 3 X-MSMail-Priority: Normal Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3023 "Eric Sosman" wrote in message news:inqa79$3j7$1@dont-email.me... > On 4/9/2011 12:08 PM, Stefan Ram wrote: >> Eric Sosman writes: >>> manipulates). Make sure the data is always seen in a consistent >>> state, except perhaps by the *one* thread that's in the act of >>> changing it; then you'll have a correct program. >> >> It still could have potential deadlocks. [...] > > I also wrote, in the part you snipped > > >> (It might not be > >> the fastest possible program -- that's where the hard parts come > >> in -- but at least it won't have race conditions.) > > Deadlock is merely a performance problem. A really, Really, > REALLY bad performance problem. ;) There's a reason it's not call slightlyilllock.